Connect Cursor to your MCP server
Cursor reaches your MCP server through one Flowplane address. You add your MCP server once in Flowplane, add that address to Cursor, and sign in. Put any remote MCP server, your own or a vendor’s, behind Flowplane: one address for your AI, sign-in per person, rules per tool and a log.
- Tools
- Whatever your server lists
- Sign-in
- Own account or shared key
- Approval, by default
- Changes wait for you
- MCP server
- Yours, behind Flowplane
- 1
Add your MCP server in Flowplane
In the Flowplane console, add a custom app (MCP), paste the server’s https address and sign in if it asks. Then tick the tools you want and add it.
Flowplane finds out how the server signs in: no sign-in at all, a pasted access token, or OAuth on the server’s own sign-in page, where Flowplane registers itself when the server allows it. The workspace signs in once for everyone, or each person signs in with their own account so the assistant acts as them and sees only the tools their account has. Flowplane keeps the login sealed; the assistant never sees it.
- 2
Add Flowplane to Cursor
Your address is shown in the Flowplane console; it looks like
https://mcp.flowplane.eu/<your-label>- Add the block below to
~/.cursor/mcp.json(all projects) or.cursor/mcp.json(one project). - Open Cursor’s MCP settings and turn
flowplaneon. - When Cursor asks, sign in to Flowplane and allow it.
{ "mcpServers": { "flowplane": { "url": "https://mcp.flowplane.eu/<your-label>" } } }Steps checked against the vendor’s documentation (Anysphere)
- Add the block below to
- 3
Ask Cursor
- “List the open tickets in our internal helpdesk server.”
- “Use our pricing server to quote 40 licences for Acme.”
- “Search our product documentation server for how to reset a device.”
- “Create a deployment ticket for release 2.4 in our ops tool.”
What Cursor can do in your MCP server
Paste the address of any remote MCP server, your own or a vendor’s, and its tools join your other apps at the one Flowplane address your assistants already use. You look at every tool before it is used and decide what each kind may do; Flowplane keeps watch when the server adds or changes tools, and every call is in the log. A server in your own network is reached through a Flowplane tunnel.
The tools are the ones your server lists, and you tick the ones you want when you add it. By default reads are allowed, changes wait for the person’s approval and deletes are blocked; your workspace’s rules decide.
Questions
- What may the assistant do with the server’s tools by default?
- Each tool is a read, a change or a delete, taken from the server’s own hints, and a tool without hints counts as a delete. By default reads are allowed, changes wait for approval and deletes are blocked. An admin can change the rule for each kind, and set an exception for one tool.
- What happens when the server adds or changes a tool?
- A new tool stays off until someone reviews it, unless the setting to use tools the server adds later is on: then it follows its kind’s rule. A tool whose name, description, inputs or hints change is suspended at once until someone looks at the difference and approves it again.
- Does it work with a local MCP server?
- It takes a remote server at an https address. One that runs in your own network is reached through a Flowplane tunnel; one that only runs on a laptop is not reachable.
- Does Cursor see the password or key for your MCP server?
- No. You sign in to your MCP server through Flowplane, which keeps that sign-in sealed. Cursor only gets a Flowplane sign-in for you, which you can revoke in the console.
- Can Cursor change things in your MCP server without asking?
- Not by default: reads are allowed and anything that changes something in your MCP server waits for your approval. Your workspace’s rules can make that stricter or looser.
Let your AI work with your data. Safely, from today.
Free for yourself, set up in a minute. For your team or company, we’re happy to help you get started.