CommunityHire an ExpertSign Up
Softr MCP serverOverview
Softr MCP server

Softr MCP Server

Connect an AI assistant to your Softr workspace to work with data, build apps, and create workflows.

Model Context Protocol (MCP) is an open standard that lets AI assistants securely connect to external tools and data. Softr’s MCP server gives an assistant like Claude, ChatGPT, or Cursor direct access to your Softr workspace — so you can query and edit your data, read and build apps, write custom code blocks, and create workflows, all in plain language.

It is the same workspace you see in Softr Studio, reached a different way. Anything the assistant does happens as you, with your permissions, and shows up in the builder like any other change.

What you can do

AreaWhat the assistant can do
DatabasesQuery, filter, and aggregate your data; create records and attach files; build and change tables, fields, and views
ApplicationsCreate and rename apps; add pages; build navigation menus; read apps, pages, blocks, and permissions; list, search, add, remove, activate, and deactivate app users; manage user groups and data restrictions; configure login, sign-in methods, sign-up, sessions, the email sender, and the app’s subdomain and custom domain; preview an app; publish it
Vibe coding blocksCreate and edit custom code blocks on an app’s pages, and manage their settings, visibility, and version history
IntegrationsBrowse the external data sources connected to a workspace
WorkflowsBuild workflows step by step, test them, publish them, and read their runs

How Softr is organized

Almost every tool asks for a workspace, so it helps to know how the pieces fit together. A workspace is the top-level container, and everything else belongs to one:

Workspace
├── Applications ── pages ── blocks (including vibe coding blocks)
├── Databases ───── tables ── fields, views, records
├── Workflows ───── steps
└── Integrations ── the external data sources apps and blocks read from

workspace_list returns the workspaces you can reach, with their IDs. It is how the assistant turns “my Sales workspace” into the ID that every other tool needs, so it is often the first call in a conversation.

Sending feedback to Softr

When you ask for something no tool can do, or a tool behaves differently from its description, the assistant can pass it on to the Softr team with send_feedback. It sends a short note in the assistant’s own words, leaving out personal data and record contents. For anything other than a missing capability, a bug, or an unclear tool description, the assistant shows you the text and sends it only once you agree. Feedback changes nothing in your workspace.

MCP server URL

https://mcp.softr.io/mcp

Use this URL when adding Softr as an MCP server in your AI tool.

Authentication

Softr’s MCP server supports two ways to sign in. Both let you choose exactly what the AI tool can reach.

OAuth is the normal route, and what Claude, Claude Code, ChatGPT, Codex, Cursor and most other clients use. You give the client the MCP server URL, and Softr shows you an authorization screen where you pick what to grant. Most clients negotiate the OAuth details themselves — a Client ID only has to be entered by hand in clients that cannot register with Softr on their own, such as Cursor.

A personal access token covers custom clients, your own MCP build, and any tool with no OAuth support. Create one under API tokens in your account menu.

Connect your AI assistant has the exact steps for every tool, the Client IDs for the clients that ask for one, and what the authorization screen is granting.

Permissions

Whether you connect with OAuth or a personal access token, you choose permissions the same way: pick which workspaces are covered, then set an access level for each of three areas.

AreaAccess levels
Applications & FormsFull access · Read only · None
DatabasesFull access · Edit data · View only · None
WorkflowsFull access · Read only · None

What each level allows:

AreaLevelWhat it allows
Applications & FormsRead onlyRead apps, pages, blocks, user groups, permissions, and the fields of the table that authenticates end users; browse integrations and read a sample of an external table’s records
Full accessThe above, plus adding pages, creating and editing vibe coding blocks, creating, changing, and deleting user groups, previewing, and publishing
DatabasesView onlyRead databases, tables, fields, views, and records; search and aggregate
Edit dataThe above, plus creating, updating, and deleting records
Full accessThe above, plus creating, changing, and deleting databases, tables, and fields
WorkflowsRead onlyRead workflows and their steps, and the outputs of steps already tested
Full accessThe above, plus building, editing, testing, and publishing workflows

Managing access

Go to API tokens in your account menu to see and remove access at any time.

  • Personal access tokens can be edited, regenerated, or deleted.
  • Authorized apps lists the AI tools you connected with OAuth, with a Revoke button for each. Revoking one immediately invalidates the tokens it was issued.

Example prompts

Once connected, you can work with your workspace in plain language:

  • “Create a new blank app in my workspace.”
  • “Add a user named Jane Doe with email jane@example.com to my app.”
  • “Deactivate the user jane@example.com in my app.”
  • “Change my app’s subdomain to my-crm.softr.app.”
  • “Connect app.acme.com to my app.”
  • “List my app’s users — who hasn’t signed in yet?”
  • “Disable login for my app.”
  • “Only let people with an example.com email sign up for my app.”
  • “Let my app’s users sign in with a one-time email code instead of a password.”
  • “Send my app’s emails from support@acme.com as Acme Support.”
  • “What email sender is configured on my app?”
  • “List all databases in my workspace.”
  • “Search the Orders table for everything still pending and sort by date.”
  • “Add a Priority field to Tasks with options Low, Medium, and High.”
  • “Build me a chart block on the dashboard page showing revenue by month.”
  • “What user groups can edit the Clients page?”
  • “Create a workflow that sends me a Slack message whenever a new order comes in.”
  • “Show me what the app looks like right now.”
  • “Add a sidebar menu with links to Dashboard, Clients, and Invoices.”
  • “Why did my order workflow fail last night?”

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Documentation documentation and read it in full, instead of answering from memory.

https://docs.softr.io/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://docs.softr.io/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.