Devin
Devin has separate cloud and local CLI connection settings. Configure the environment where the agent actually runs, and reuse an existing Simplified connection if one is present.
Cloud Devin
In Devin, open Customize → MCPs → Add MCP → Add custom MCP. Name the server Simplified, choose HTTP, and enter:
Save it, complete the sign-in flow, and use Test tools to confirm Devin can list the Simplified tools. Adding a custom server requires the Manage MCP Servers permission; ask an organization admin if the control is unavailable.
Devin CLI and Devin Local
For a local connection, run:
The add command uses Devin’s local scope by default. Select user or project scope only when you intend to share the configuration more broadly. Devin Local in Devin Desktop uses the same agent harness as Devin CLI.
Verify access
Ask Devin to identify your Simplified workspace and list its teamspaces without changing data. Confirm it called the Simplified tools, then follow the verification checklist. For workflow instructions, see the Simplified skills repository.
See Devin’s official cloud MCP guide and CLI MCP guide for current controls and authentication.
