Skip to main content
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

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.
Working with your Softr workspace over MCP does not consume Softr AI credits. The AI tool you connect uses its own model and its own quota.

​
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.

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.

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

​
Claude

Works in Claude on the web, in the desktop app and in Cowork.
1

Open the connector settings

In Claude, go to Customize → Connectors, click +, then Add custom connector.On a Team or Enterprise plan only an Owner can add a custom connector. If you don’t see the +, ask an Owner to add Softr once — after that every member connects to it themselves from the same screen.
2

Enter the name and the server URL

Name it Softr, paste https://mcp.softr.io/mcp as the remote MCP server URL, and click Continue.

Claude's Add custom connector dialog with the Softr server URL filled in.

3

Click Add

Claude detects Softr’s authentication and OAuth client settings for you. Leave them as they are and click Add.
4

Authorize your Softr account

Click Connect, choose what Claude can reach, and click Allow. See What you are approving.
5

Try it

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

​
Claude Code

Claude Code adds MCP servers from the command line.
1

Add the server

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

Authenticate

Run /mcp inside Claude Code, select softr and choose Authenticate. Softr’s authorization screen opens in your browser — see What you are approving.Until you do, claude mcp list reports the server as Needs authentication.
3

Try it

Ask Claude Code to list your Softr apps.

​
ChatGPT

Custom MCP servers in ChatGPT arrive as plugins, which requires developer mode.
1

Enable developer mode

Open ChatGPT Settings → Security and login → Developer mode and switch it on.

Developer mode in ChatGPT's security settings. It has to be on before you can add a custom MCP server.

2

Add Softr as a plugin

Open Plugins, click +, then fill in the details: name it Softr, keep Connection set to Server URL and paste https://mcp.softr.io/mcp, and leave Authentication on OAuth.Tick I understand and want to continue to accept the custom MCP server notice, then click Create.

ChatGPT's New Plugin dialog. Name, server URL and OAuth are the only fields Softr needs.

3

Authorize your Softr account

Click Connect, choose what ChatGPT can reach, and click Allow. See What you are approving.
4

Try it

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

​
Codex

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

Add the server

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

Sign in

Softr’s authorization screen opens in your browser — see What you are approving. Run codex mcp list to confirm the server is there, or /mcp in the Codex TUI.
3

Try it

Ask Codex to list your Softr apps.
Softr does not support OAuth Dynamic Client Registration. Codex negotiates a Client ID Metadata Document instead, which needs no configuration from you. If a login fails, fall back to a personal access token.

​
Cursor

1

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.
2

Add Softr as a server

Paste the following into mcp.json and save:
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.
3

Authorize your Softr account

Softr appears under Needs Attention. Click Authenticate, choose what Cursor can reach, and click Allow. See What you are approving.

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

4

Try it

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

​
Other MCP clients

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

Find the MCP settings

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

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.
3

Authorize your Softr account

Follow the client’s sign-in flow, choose what it can reach, and click Allow. See What you are approving.

​
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: 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'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.
Full access on Databases lets an assistant delete records, fields, tables and whole databases. If you want a connection that can never delete anything, set Databases to View only. See Deleting data.

​
Personal access tokens

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

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.
2

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.
3

Send it as a bearer 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.
Authorized apps only appears once you have authorized at least one tool, so it is missing if you have only ever used personal access tokens.

​
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.

Softr MCP server

What the assistant can do once it is connected, and how permissions work.

Databases

Query, edit and structure your Softr databases through an AI assistant.

Applications

Create apps, add pages, manage app users, preview and publish.

App MCP server

Let the users of your app work with it through their own AI assistant.