Back to magertron.com

Cursor

Magertron for Cursor

Use the MCP servers your platform has already approved — and hand it the ones you build. Both directions, from inside the editor.

1 · Entitled The portal lists the servers your roles can reach. Nothing else.
2 · Configured One file, dropped where Cursor looks. No credential in it.
3 · Governed Every call is authorized and recorded at the gateway, not in your editor.

Add your servers

Open the developer portal at /portal on your platform's address.

  1. Choose Add to your IDE in the toolbar
  2. Download mcp.json, or Copy to merge if you already have one
  3. Save it to ~/.cursor/mcp.json, or .cursor/mcp.json in a project
  4. Restart Cursor

The file lists every server your roles can reach and nothing they cannot. It works in Cursor, VS Code, Claude Desktop and Windsurf alike — the format is shared, so this is not a Cursor feature that happens to work elsewhere.

No credential is in the file. It references ${env:MCP_TOKEN}, so it is safe to commit to a repository or paste into a chat. Mint a token in the portal and export it in your shell profile.

Tokens expire

On purpose. That is the point of a governed platform.

A token that lasts a year keeps working long after somebody's access has been revoked, and outlives every role change in between. Yours does not. When calls start failing, mint a new one and restart your editor.

Organisations issuing agent credentials through their own identity provider can exchange those for short-lived platform tokens automatically. Ask your platform team.

Submit a server you built

The other direction, and it uses the extension rather than a config file.

From a terminal

cursor --install-extension magertron-submit-<version>.vsix

One extension, both editors. Cursor is a VS Code fork and runs it unchanged — there is no separate build.

Open your project as a folder first. The submit command lives on the file explorer's right-click menu, so it appears on a manifest in the tree. Opening a file on its own leaves nothing to right-click, and it looks as though the extension is not installed.
Settings live under VS Code's pane, not Cursor's own. If a search for magertron finds nothing, look under Settings → Extensions → Magertron. Editing ~/.config/Cursor/User/settings.json directly is quicker.

Anything credential-shaped is removed before the manifest leaves your machine. Environment variable names are sent; values are not, including defaults written into the file. Your platform team can see that a server needs a secret without ever seeing the secret.

No platform yet?

Run the orchestrator in your own sandbox and point Cursor at it.

# add the chart repository
helm repo add magertron https://magertron.com/charts
helm repo update

# install into a new namespace
helm install mcp magertron/mcp-orchestrator \
  --namespace mcp-system --create-namespace

Starts in Free Tier. No license required. More at magertron.com/charts.

Also available for VS Code.