Skip to main content
Windsurf became Devin Desktop in June 2026. New agent tabs use Devin Local; the older Cascade agent reads a separate MCP list. Devin Local and the Devin CLI share one configuration (checked 2026-10-10).

​
Devin Local and Devin CLI

The quickest way is the CLI:
login opens AdLoop’s consent page; choose Allow access. Leave out -s user to add AdLoop to the current project only. Or edit ~/.config/devin/mcp_config.json (Windows: %APPDATA%\devin\mcp_config.json; per project: .devin/mcp_config.json):
If AdLoop shows Needs auth in the MCP list, click Authenticate.
Check with devin mcp list, then ask: “Run the AdLoop health check.”

​
Legacy Cascade agent

Cascade reads ~/.config/devin/mcp_config.json too, but expects serverUrl (Windsurf versions before the rename used ~/.codeium/windsurf/mcp_config.json):
Open the file from the Cascade panel: ⋯ → MCPs → Open MCP config file. The MCPs section then lists AdLoop with its tools and an on/off switch.

​
Notes

  • Cascade can see at most 100 tools across all servers. If you run several, use an AdLoop key limited to a few toolsets.
  • On team plans, once an admin allowlists any MCP server, all others are blocked. The allowlist entry must be named exactly adloop, like the config key.
  • MCP tools ask for your approval by default, and every AdLoop write goes through its own preview and confirm flow on top.
Your AI can read these docs too. Add https://docs.getadloop.com/mcp as an additional MCP server and your assistant can search this documentation while it works: setup answers, troubleshooting, and tool guidance on demand.