From the video

Every prompt from the Softr MCP video.

Six prompts that took Claude Code from an empty Softr workspace to a published project tracker: a real database, a live dashboard built with the Vibe coding block, user login, and a workflow that emails you the moment a project is blocked. Paste them in order, or grab the one you need.

Get started with Softr free Watch the video

Sponsored by Softr · works with Claude, ChatGPT, Codex, Cursor and any MCP client

Data

Database

A Projects table with a proper schema and eight fictional client projects.

App

Live dashboard

A read-only Vibe coding block that reads the live records, counts included.

Security

Login + users

App users, a login wall on the page, and user groups with edit rights.

Automation

Workflow + App MCP

An email the moment a project is Blocked, and the app's own MCP for your team.

Connect

Connect Softr to Claude Code

One URL, one login, one restart. Same route for ChatGPT, Codex and Cursor — every tool just buries the setting somewhere different.

Copy the setup docs

In Softr, open the MCP page and click Connect your agent. Pick your tool, open the docs and hit Copy page. The only value that matters is the server URL:

https://mcp.softr.io/mcp

Paste it into Claude Code

Start a fresh project so everything lives in one place, paste the docs in, and add two words. Claude adds the MCP server and opens the browser so you can log in and approve the workspace access.

Say[paste the copied docs page] Set this up.

Restart Claude Code after the login. MCP tools are picked up on start-up, so the first session won't see them. Quit, reopen, then check.

Check it's connected

If Claude lists your workspaces, you're in. If it guesses the wrong workspace later, tell it in plain English — make a new workspace is what I used.

SayList my Softr workspaces

Prompts

The prompts, in order

Exactly what I pasted on camera. Swap the highlighted placeholders for your own workspace, date and emails.

Create the database and records

Everything else hangs on the data, so this comes first. The due dates are relative to today so the overdue and due-soon states show up properly. All eight projects are fictional.

1Database + 8 fictional projects

In my [workspace name] workspace, create a database called Agency Projects. Add a Projects table with these fields: project_name, client_name, owner_name, due_date, status, priority, next_action. Status options: Not started, In progress, Blocked, Done. Priority options: Low, Medium, High. Pick sensible field types and show me the schema before you add any records. Then add these eight projects. Today is [today's date] — set due dates relative to that as noted: - Northstar website, Northstar Studio, Maya, Blocked, High, due in 2 days - Atlas onboarding, Atlas Works, Theo, Blocked, Medium, due 2 days ago - Cedar launch, Cedar Labs, Priya, In progress, High, due tomorrow - Lumen brand refresh, Lumen Co, Maya, In progress, Medium, due in 5 days - Harbor client portal, Harbor Studio, Theo, In progress, Low, due in 12 days - Willow campaign, Willow House, Priya, Not started, Medium, due in exactly 7 days - Orbit landing page, Orbit Collective, Theo, Done, High, due in 3 days - Beacon research, Beacon Works, Maya, Done, Low, due 4 days ago Give each one a realistic next_action. All fictional — no real contact details. Show me all eight records when you're done.

Use your own projects instead Optional

Following along with real work? Use this instead of prompt 1 and point Claude at wherever your project list lives today — a CSV, a spreadsheet export, a notes file, or just paste it in.

1bImport your own data

In my [workspace name] workspace, create a database called Agency Projects with a Projects table. My real project list is here: [paste it, or give the path to your CSV / spreadsheet / notes file]. Read it and work out sensible fields — at minimum project_name, client_name, owner_name, due_date, status, priority and next_action. Map whatever statuses and priorities I already use onto Not started / In progress / Blocked / Done and Low / Medium / High. Pick sensible field types and show me the schema before you add anything. Then import every row. Don't invent data: if a value is missing, leave it blank and list the gaps at the end. Show me the record count and the first ten records when you're done.

Real client data: read the schema Claude shows you before it imports, and strip anything you wouldn't want on a shared dashboard.

Build the live dashboard

This is the Vibe coding block. The important lines are read the live table records and do not hardcode any project data — otherwise you get a pretty screenshot of your data instead of a dashboard.

2Read-only dashboard (Vibe coding block)

In my [workspace name] workspace, create a new blank Softr app called Agency Project Desk with a Dashboard page. On that page, create a Vibe coding block connected to the Projects table in the Agency Projects database. Build a read-only internal dashboard: - Counts at the top: total projects, and how many are Blocked - A project list showing name, client, owner, due date, status and next action - Filters for status and owner Read the live table records — do not hardcode any project data into the component. Handle pagination so the counts cover every record, not just the first page. Make clear whether a count is global or filtered. Keep it readable on mobile. Show me the data connection and a preview when it's done. Don't publish the app.

Want a tweak? Say it: change the list to a kanban view, add a due-soon filter. Update a record from the same chat with change Northstar to 20 Sept due and refresh.

Add login and app users

The dashboard should only be visible to people you invite. This creates the users table, turns login on and locks the page behind it.

3Users + login

Create a demo users table for app users, connect it to the app as the user source, and explicitly turn login on. Then restrict the Dashboard page and its Vibe coding block to logged-in users only. Create one for [admin email] and one for [your email]

Once the app is published, select the users in Softr and hit Send invite. Give someone edit rights later with: update [email] to be in a user group with edit rights please

Chase blocked work automatically

A Softr workflow with one trigger and two actions: log a follow-up and email you. Build it unpublished first so you can click through the trigger and actions in Softr.

4Follow-up workflow

In the [workspace name] workspace, create a workflow called "Follow up blocked projects" on the Agency Projects database. Trigger: a record in Projects meets the conditions status = Blocked AND priority = High. Then two actions: 1. Add a row to a new Follow-ups table with the project name, the owner, the next action, a status of Open, and a due date three days from creation 2. Send an email using Softr's native send-email action, to me, saying which project is blocked, who owns it and what the next action is Build it but do not publish it yet. Show me the trigger and both actions so I can walk through them.

Softr flags untested steps as requires attention. That's what these two are for:

Say2 steps require attention, why?

Sayrun it for real

Only Blocked and High fires this one. Want overdue projects chased too? Ask for a second workflow with the condition due_date is before today AND status is not Done.

Publish, then run it from Claude

Publish the app and the workflow, invite yourself, and then the payoff — open a brand-new chat and change the data. The dashboard reads the table, so it updates on refresh.

Saypublish this site

Sayworkflow publish

Saymove Atlas to 23 Sept

Give your team the app's own MCP

The bit people sleep on. You built everything as the Softr builder, but your team shouldn't need your account. In the published app's settings, switch on App as MCP and enable MCP for users. Each person then connects the app URL to their own Claude, ChatGPT, Codex or Cursor — read and write access to the app's records, scoped to what their user group allows.

6Connect the app MCP (each teammate runs this)

Saywhich projects in that app are blocked then?

Publish first. The app MCP only works on the published app — if the connection fails, you skipped the publish step (I did on camera).

Outcome

What you end up with

✓A real database with a proper schema — not a CSV on one laptop

✓A live dashboard your team and clients can log into at a real domain

✓Automations that email you when work is Blocked and needs you

✓Everyone updating the same app from the AI they already work in, via MCP

Build it with the agent you already use.

Softr MCP is on every plan, including Free, and it doesn't use Softr AI credits — your AI tool runs on its own quota.