Back to magertron.com

Devin

Magertron™ for Devin

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

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

Add your servers

One setting, and the extension does the rest.

  1. Mint a service-account token in the developer portal at /portal
  2. In Devin, open Settings and search magertron
  3. Paste the token into Magertron: Token
  4. Restart Devin
Devin Settings showing the Magertron Token field, with a warning that the value is a bearer credential stored in plain text
One setting. The warning is ours — a token on disk is a token on disk, and the extension says so rather than letting you find out later.

There is no command to run. On startup the extension asks the gateway what your roles can reach and writes every one of them — across every namespace you are entitled to — into Devin’s MCP config. Servers you cannot reach are not in the file, because they were never in the answer.

The generated MCP config open in Devin, listing several servers across two namespaces, each pointing at the gateway with an Authorization header referencing an environment variable
Written for you: every entitled server, each pointed at the gateway.
It reconciles, it does not just seed. The file is rewritten on every start, so a grant your platform team revokes on Monday is gone from your editor on Tuesday — without anyone asking you to edit a file.
No credential is in the file. It references ${MCP_TOKEN}, so it is safe to commit to a repository or paste into a chat. Export the token in your shell profile and start Devin from that shell.

Submit a server you built

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

Download v0.1.0 (.vsix) User guide (PDF)

From a terminal

devin-desktop --install-extension magertron-submit-<version>.vsix
Devin's command palette showing Magertron: Submit MCP Server for Review alongside Devin's own MCP config migration command
The command, once the extension is installed. Devin’s own Migrate MCP Config sits beside it — it moves a config from Windsurf’s path, and has nothing to do with the gateway.

One extension, every editor. Devin Desktop is a VS Code fork and runs it unchanged — the same file installs in Cursor, VS Code and Windsurf. There is no separate build and no Devin-specific version to keep current.

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.

Your platform team can see this laptop

Worth knowing, rather than discovering.

If your organization runs Magertron's endpoint inventory, the MCP config on this machine is read on a schedule and matched against what has been approved — whether it points at the gateway, straight at a vendor, or at a route that no longer exists. Nothing resident is installed; it rides the endpoint management your IT team already runs.

No Magertron installed yet?

Run the orchestrator in your own sandbox and point Devin 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 Cursor, VS Code and Claude Code.