A Softr account with a workspace you can edit, and an MCP-capable AI client (Claude, ChatGPT, Cursor or Claude Code).
Softr's MCP server lets an AI assistant work directly with your Softr workspace. You can ask it to query a database, add a page to a portal, create a custom block or build a workflow, all from a chat. This guide walks through connecting safely and testing it with low-risk requests first.
Softr updates its interface often. If a label below doesn't match what you see, check the official Softr MCP documentation.
What you need
- A Softr account with a workspace you can edit.
- An MCP-capable AI client. Softr lists Claude, ChatGPT, Cursor and Claude Code as supported, and says most other MCP clients work too.
- Five minutes to plan permissions. This is the step most people skip.
Step 1: Decide what the assistant can touch
Softr splits MCP access into three areas, and each gets its own level:
| Area | Levels available |
|---|---|
| Applications & forms | None · Read-only · Full access |
| Databases | None · View-only · Edit data · Full access |
| Workflows | None · Read-only · Full access |
Softr describes each level as a bundle: a higher level includes everything below it.
Recommended starting point:
- Applications & forms: Read-only
- Databases: View-only
- Workflows: None
You can raise the levels once you've seen how the assistant behaves.
Step 2: Choose how to authenticate
Softr supports two methods:
- OAuth (recommended). You sign in to Softr and approve access in the browser, with no secret to copy or store.
- Personal access token. Useful for developer tools and scripts. Treat it like a password: don't paste it into shared documents or commit it to a code repository.
Step 3: Add the Softr server to your AI client
In your AI client's settings, add a new MCP server / connector with this address:
https://mcp.softr.io/mcp
Then complete the OAuth sign-in, or paste your token if your client asks for one. In Claude, remote servers are added from the connectors settings. In code editors such as Cursor or Claude Code, they're added in the MCP configuration.
Step 4: Start with read-only requests
Check that the connection works with requests that can't change anything:
- "List the apps in my Softr workspace."
- "How many records are in the Clients table? Group them by status."
- "Which pages in my Client Portal app are visible to logged-out users?"
If the answers match what you see in Softr, the connection is working.
Step 5: Let it make small changes
Raise the permission for one area, for example Databases → Edit data. Then try a contained change:
- "Add a record to the Projects table: name 'Website refresh', status 'Planned'."
- "In my Client Portal, add a page called 'Invoices' that lists invoices for the logged-in client."
Check each change in the Softr editor before moving on.
Step 6: Try vibe coding and workflows
Once you're comfortable, try the features that shipped in Softr's MCP Launch Week:
- Vibe code blocks. "Create a block that shows a bar chart of projects by status, using the Projects table." Softr keeps a version history for these blocks, so you can roll back.
- Workflows. "Build a workflow that emails the account manager when a project's status changes to 'Blocked'." Test it before you publish.
Safety checklist
- Start every new connection at read-only / view-only.
- Give full access only to the area you're actively working on.
- Test changes in a copy of the app before touching a live client portal.
- Review what the assistant changed before you publish.
- Remove access (or revoke the token) when you're done.
Troubleshooting
- The assistant can't see an app or table. Check the permission level for that area. "None" hides it completely.
- Changes are refused. You're probably on a read-only or view-only level. Raise it for that area only.
- The token stopped working. Create a new personal access token in Softr, or switch to OAuth.
Next steps
- Read the news: Softr opens its platform to AI assistants with MCP.
- Why this matters: MCP is turning no-code builders into back ends for AI.