CommunityHire an ExpertSign Up
Softr MCP serverConnect
Softr MCP server

Connect your AI assistant

Step-by-step setup for Claude, Claude Code, ChatGPT, Codex, Cursor and any other MCP client.

Softr’s MCP server works with any client that speaks the Model Context Protocol. The setup is the same everywhere — point the client at one URL, then approve what it can reach in your workspace — but every tool buries that setting in a different place. This page has the exact route for each.

If you are not sure what the assistant will be able to do once it is connected, start with the Softr MCP server overview.

MCP server URL

https://mcp.softr.io/mcp

This is the only value you need for Claude, ChatGPT, Codex, Cursor and most other clients. There is nothing to install and no API key to paste.

Get the setup guide inside Softr

Softr Studio has the same instructions built in, with the server URL ready to copy. Click your workspace name at the top of the left sidebar, then API tokens or Use Softr.

Softr Studio account menu with API tokens and Use Softr highlighted

The account menu in Softr Studio. Both API tokens and Use Softr lead to the MCP setup guide.

Pick your tool and Softr walks you through it, screen by screen.

Connect your AI tools to Softr MCP dialog showing four tool tabs and the MCP server URL

The in-product setup guide, with a tab for Claude, ChatGPT, Cursor and everything else.

Set up your client

Pick your tool below. Every route ends on the same Softr authorization screen — see What you are approving.

Works in Claude on the web, in the desktop app and in Cowork. Softr is in Claude’s connector directory, so there is no server URL to paste.

Add the Softr connector

Open Softr in Claude’s connector directory and click Connect to Claude.

Softr's connector page in Claude with the Connect to Claude button

Softr's page in Claude's connector directory. Connect to Claude starts the authorization.

Authorize your Softr account

Choose what Claude can reach, and click Allow.

Try it

Start a new chat and ask “List my Softr apps.”

Claude Code adds MCP servers from the command line.

Add the server

Terminal
claude mcp add --transport http softr https://mcp.softr.io/mcp

Add --scope user to make Softr available in every project rather than only the current one.

Authenticate

Run /mcp inside Claude Code, select softr and choose Authenticate. Softr’s authorization screen opens in your browser.

Until you do, claude mcp list reports the server as Needs authentication.

Try it

Ask Claude Code to list your Softr apps.

Softr is in ChatGPT’s plugin directory, so there is no server URL to paste and no developer mode to switch on.

Add the Softr plugin

Open Softr in ChatGPT’s plugin directory and click Connect.

Softr's plugin page in ChatGPT with the Connect button

Softr's page in ChatGPT's plugin directory. Connect starts the authorization.

Authorize your Softr account

Choose what ChatGPT can reach, and click Allow.

Try it

Start a new chat and ask “List my Softr apps.”

The Codex CLI, the Codex IDE extension and the ChatGPT desktop app share one MCP configuration, so you only set this up once.

Add the server

Terminal
codex mcp add softr --url https://mcp.softr.io/mcp

Or add it to ~/.codex/config.toml by hand:

TOML
[mcp_servers.softr]
url = "https://mcp.softr.io/mcp"

Sign in

Terminal
codex mcp login softr

Softr’s authorization screen opens in your browser. Run codex mcp list to confirm the server is there, or /mcp in the Codex TUI.

Try it

Ask Codex to list your Softr apps.

Open the MCP settings

In Cursor, go to Customize → MCPs and click New MCP Server.

Softr’s in-product setup guide also has an Add to Cursor button that opens Cursor with these details pre-filled.

Add Softr as a server

Paste the following into mcp.json and save:

JSON
{
  "mcpServers": {
    "Softr": {
      "url": "https://mcp.softr.io/mcp",
      "auth": {
        "CLIENT_ID": "4d2556b2-cfc8-4608-bd76-8dbe7e605f68"
      }
    }
  }
}

Cursor doesn’t register OAuth clients dynamically, so it needs Softr’s Cursor client ID. It goes in ~/.cursor/mcp.json to use Softr in every project, or .cursor/mcp.json for one project — see Cursor’s MCP documentation.

Authorize your Softr account

Softr appears under Needs Attention. Click Authenticate, choose what Cursor can reach, and click Allow.

Cursor Customize MCPs tab with New MCP Server marked 1 and the Softr entry's Authenticate link marked 2

Cursor's MCPs tab: New MCP Server adds the server, Authenticate signs it in to Softr.

Try it

Start a new chat and ask “List my Softr apps.”

Softr works with any client that supports remote MCP servers over streamable HTTP — Mistral, Windsurf, n8n, Zapier, your own build.

Find the MCP settings

Look for MCP, Connector, Integration, App or Tool in the client’s settings.

Add Softr as a remote server

Add a custom or remote MCP server and enter https://mcp.softr.io/mcp. Choose OAuth if the client asks for an authentication method.

Authorize your Softr account

Follow the client’s sign-in flow, choose what it can reach, and click Allow.

If the client asks for a Client ID

Some clients can’t register themselves with Softr and ask you for OAuth credentials. Softr has pre-registered clients for the tools below:

AI toolOAuth Client ID
Claude (claude.ai)db31b760-e758-4f52-b15b-93b0262a1290
Cursor (cursor.com)4d2556b2-cfc8-4608-bd76-8dbe7e605f68
ChatGPT (chatgpt.com)aa73bf7b-c5b6-4031-b771-25108bf6c132
Mistral AI (mistral.ai)522bfc02-e64f-43cd-87ef-552507ecb967

Leave the Client Secret blank — Softr’s OAuth clients are public and don’t use one. For any other client, use a personal access token instead.

What you are approving

However you connect, the last step is the same Softr screen. You choose which projects the tool can reach and how much it can do in each of three areas, then click Allow.

Softr authorization screen showing Access set to Everything and Full access on Applications & Forms, Databases and Workflows

Softr's authorization screen. Access sets which projects are covered; Permissions sets what the tool can do in each area.

The AI tool cannot request particular permissions in advance — you always pick them here, and you can change or revoke them later. For what each level allows, see Permissions.

Personal access tokens

Use a token when you are building your own MCP client, or connecting a tool that has no OAuth support.

Create the token

Go to API tokens in your account menu and click Create. Give it a name and an expiry — never, 1 year, 90 days or 30 days.

Choose what it can access

On the Define scopes step, pick the workspaces the token covers and the permissions it carries, exactly as on the authorization screen above.

Send it as a bearer token

JSON
{
  "mcpServers": {
    "softr": {
      "url": "https://mcp.softr.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Managing and removing access

API tokens in your account menu is also where you take access away.

  • Personal access tokens can be edited, regenerated or deleted.
  • Authorized apps lists every tool you connected with OAuth, with a Revoke button for each. Revoking one invalidates its tokens immediately.

Connecting an app instead of a workspace

This page is for builders connecting their Softr workspace. If you want the users of one of your apps to work with it through their own AI assistant, with their own app permissions, that is a different server — see App MCP server.

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.