MCP

Devin Desktop (formerly Windsurf)

Last verified: 2026-07-21

Windsurf became Devin Desktop on June 2, 2026 — existing installs updated automatically, carrying settings and MCP connections over. The agent formerly called Cascade is now Devin Local, though the panel and its settings section still say Cascade. Remote servers like ours sign in through your browser, and that flow now works out of the box.

Prerequisites

  • A Manyreach account + your API key (Manyreach web app → API & Integrations)
  • Devin Desktop installed, on any plan (org/enterprise users: an admin may need to enable MCP access first)

Steps

  1. Click the MCPs icon in the top-right of the Cascade panel (or Devin Settings → Cascade → MCP Servers — some builds still label the menu Windsurf Settings).

  2. Manyreach isn't in the MCP Marketplace, so click View Raw Config to edit the config file directly — it lives at ~/.codeium/windsurf/mcp_config.json (Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json), still under the pre-rebrand folder name. The Command Palette entry Windsurf: Configure MCP Servers opens the same file.

  3. Add:

    {
  "mcpServers": {
    "manyreach": {
      "serverUrl": "https://mcp.manyreach.com/mcp"
    }
  }
}

  4. Save, then click Refresh in the MCP panel — adding an HTTP server triggers the browser sign-in automatically. If the new server doesn't appear, fully quit and reopen the app.

What the authorization looks like

Your browser opens a Manyreach authorization page. Paste your API key there and click Authorize. The key is checked once and never shown to the AI — afterwards the connection stays signed in on its own.

Verify

Ask the agent in the Cascade panel to "describe the Manyreach catalog". It should call the describe tool and list resources like campaign, prospect, and sender.

Troubleshooting

  • New server doesn't show up — click Refresh in the MCP panel first; if that doesn't work, fully quit and reopen the app (closing just the window isn't always enough). Several MCP fixes landed through 2026, so updating helps too.
  • Connects, but tool calls fail with 401 — a long-reported issue where the authorization header is left off individual tool calls. Re-authorize the server; for an OAuth server like this one don't hand-add a headers block, and remove any stray empty one left in the config.
  • Our tools don't seem to load with several other MCP servers installed — there's a cap of about 100 total tools across all connected servers (and 20 tool calls per prompt); disable servers you're not using.
  • MCP options greyed out on a team/enterprise account — an admin may have MCP access disabled for the organization; ask them to enable it.