Skip to main content
Devin’s web app and the Devin CLI each keep their own Spiral connection. Set up the one you use; signing in on one does not sign in the other.

Devin (web app)

1

Add a custom MCP

Open Customize › MCPs. Click + and choose New MCP. Fill in:
  • Server Name: Spiral
  • Transport: HTTP
  • Server URL: https://api.spiral.ai/mcp
  • Authentication method: OAuth
  • Access: Personal, so each member signs in to their own Spiral account
Leave OAuth credentials empty: Devin registers itself with Spiral. Click Add.
2

Sign in to Spiral and approve

In Customize › MCPs, open Spiral and choose Connect. Spiral opens: sign in, pick the organization and click Authorize. No API key.
3

Check it

On Spiral’s configuration page, click Test tools. Devin lists Spiral’s tools.
4

Try a starter prompt

Start a new session and send:
Any member can add a server for themselves. To add Spiral for the whole organization, an admin switches Myself to the organization and chooses Add custom MCP.
Create a key under API keys in the console. In the New MCP form, set Authentication method to Auth Header, keep the header key Authorization and set the value to Bearer <your key>.

Devin CLI

The CLI’s settings also apply to Devin Local, the default agent in new Devin Desktop tabs.
1

Add the server

-s user makes Spiral available in all your projects. Without it, the server goes to this project’s .devin/mcp_config.local.json.
2

Sign in

Sign in to Spiral in the browser and click Authorize. No API key. devin mcp logout spiral signs out.
3

Try a starter prompt

Start devin and send:
Devin asks before it uses each MCP tool. Approve the prompt, or add mcp__spiral__* to permissions.allow.
Create a key under API keys in the console and add Spiral to ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows) with the key as a header:
Keep the key out of .devin/mcp_config.json: that file is shared through version control.
If something does not work, see Troubleshooting.