Windsurf MCP server: there isn't one, and why

Windsurf sits on the client side of the protocol, and the servers its owner does publish belong to a different product. What to connect instead.

Last verified 25 August 2026 · from Windsurf's Cascade MCP documentation, Devin documentation and the MCP registry

This page is one of 90 in a directory of monitoring and developer tools. Each page checks what an AI coding agent can get out of the tool through its MCP server, the connector that lets the agent query the tool directly.

What is the Windsurf MCP server, and is it usable?

Windsurf is an AI code editor whose agent is called Cascade. Its role in the Model Context Protocol is to be the client: you configure servers, and Cascade makes their tools available to the model.

Cognition acquired Windsurf and does publish MCP servers. Devin MCP exposes Devin, its autonomous engineer product, and DeepWiki MCP exposes repository documentation. Neither exposes anything Windsurf holds.

The distinction matters because a search for Windsurf MCP surfaces Cognition's servers. Connecting one gives an agent Devin data while the user believes they connected their editor.

Every one of the 90 vendors in this directory gets the same four checks. Windsurf passes 0 of them.

Windsurf operates in code, tests and review through Cascade, which consumes servers other vendors publish.

The takeaway is a correction rather than a verdict. Windsurf has no server to connect, and the servers its owner publishes belong to Devin. If you came looking for a Windsurf connector, go to the page for the product that holds your data. Its client setup block is what you need.

What can an AI agent do with Windsurf?

The failure here is a naming collision rather than a broken server.

How to configure Windsurf MCP for agents

1. 1

   Check which agent you are configuring

   Windsurf documents that the MCP configuration applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, configures servers in the Devin CLI config files instead.

2. 2

   Enterprise accounts must turn it on

   The documentation notes that enterprise users must enable MCP manually through settings before any of this is reachable.

3. 3

   Budget against a hard ceiling

   Cascade has a limit of 100 tools available at any one time, so the servers you connect compete for one fixed allowance.

4. 4

   Turn tools off per server, not per connection

   Each server has a settings page where individual tools can be toggled, which is the lever for staying under that ceiling.

5. 5

   Decide the allowlist before the first server

   Once an admin allowlists any server, every other server is automatically blocked for the team.

Paste this into your agent’s instructions

Cascade caps the number of tools, not the token cost. A connector can be attached and still be invisible to the model. An agent that cannot see a tool should say so rather than conclude the data does not exist.

When you answer inside Windsurf, state:
- Which server answered, and which of its tools you called.
- That Cascade allows 100 tools at a time, so a tool may be
  present in a server and not enabled in this session.
Never state that data does not exist. State which server you
queried and whether its tool was enabled.
Write your answer in ASD-STE100 Simplified Technical
English. Use short sentences with one idea in each.

Do you need the MCP server at all?

There is no Windsurf server to replace, so the useful move is choosing what Cascade connects to. Windsurf's own documentation covers adding servers to Cascade.

For code and pipelines, GitHub and CircleCI. For what happens after a deploy, Grafana, Datadog or Dynatrace. For your own agents, Langfuse or Arize Phoenix.

Devin MCP is worth connecting on its own terms if you use Devin. It is simply a different product from the editor.

Connect servers for the data you query. If you use Devin, connect Devin MCP knowingly rather than as a Windsurf substitute.

Windsurf MCP server setup

Nothing here installs a Windsurf server, because there is none. This is how servers are added to Cascade, which is the question a reader on this page actually has.

Windsurf's documentation gives one important caveat first: the configuration below applies to the legacy Cascade agent. The Devin Local agent, which is the default for new tabs, reads the Devin CLI config files instead.

No credentials appear in the file shapes themselves. Each server supplies its own, either in env for a local process or in headers for a remote endpoint.

{"mcpServers":{"github":{
  "command":"npx",
  "args":["-y","@modelcontextprotocol/server-github"],
  "env":{
    "GITHUB_PERSONAL_ACCESS_TOKEN":"<your-token>"}}}}

{"mcpServers":{"remote-http-mcp":{
  "serverUrl":"<your-server-url>/mcp",
  "headers":{"API_KEY":"value"}}}}

Cascade panel  ->  MCPs icon  ->  choose a server  ->  Install

windsurf://windsurf-mcp-registry?serverName=<server-name>

Every other client

Each block below is the configuration for one client, with the file path and the key that client expects.

stdio  ·  Streamable HTTP  ·  SSE      OAuth on all three

Admin allowlist: allow one server  ->  all others blocked

Read-only access, permissions and security

• Windsurf disclaims liability for tool calls

  Its documentation states that because MCP tool calls can invoke code written by arbitrary server implementers, it does not assume liability for MCP tool call failures.

• The allowlist is the team-level control

  Once an admin allowlists any server, all other servers are automatically blocked for team members, which makes the first allowlist entry a decision about everything else.

• Enterprise accounts start closed

  The documentation states enterprise users must turn MCP on manually through settings.

• Credentials sit in your own files

  A local server carries its token in env inside ~/.codeium/windsurf/mcp_config.json; a remote one carries it in headers, unless the server supports OAuth.

• Cascade supports tools, resources and prompts

  All three surfaces of a server are exposed, so a review of a server should cover more than its tool list.

Troubleshooting

You cannot find a Windsurf MCP server to install

There is not one. Cascade is the client. The servers Cognition publishes, Devin MCP and DeepWiki MCP, serve Devin and repository documentation rather than Windsurf.

The configuration file has no effect

Check which agent is running. Windsurf documents that mcp_config.json applies to the legacy Cascade agent, while the Devin Local agent, the default for new tabs, uses the Devin CLI config files.

A tool exists in the server but the model never calls it

Cascade allows 100 tools at a time. Open that server's settings page from the MCPs icon and toggle the tools you need within the limit.

MCP is missing entirely on an enterprise account

It is off until enabled. The documentation states enterprise users must turn it on manually through settings.

A server your team used has stopped appearing

Check the admin allowlist. Allowlisting any server automatically blocks every other server for that team.

An allowlist pattern does not match

Server matching uses regex. The documentation notes that $, ., [, ], ( and ) carry regex meaning and must be escaped for literal matching.

Windsurf MCP server: Reference

What engineers report

There is no Windsurf server to have opinions about, so this section records what the search actually finds.

Windsurf and Devin documentation read on 25 August 2026, alongside a search of Cognition's published servers and the official MCP registry.

Should you connect an agent to Windsurf?

There is nothing to connect: this is the agent side of MCP. Best for connecting vendor servers to Cascade, with Devin MCP added only if you actually use Devin.

Strongest fit

Teams who want an editor whose agent can call other vendors' MCP servers.

Main advantage

Cascade is a capable client, and Cognition publishes real servers for its other products.

Main weakness

Nothing exposes Windsurf itself, and the servers that do exist are easy to mistake for it.

Operational risk

Connecting Devin MCP believing it is a Windsurf connector gives an agent the wrong data confidently.

Frequently asked questions