Windsurf, Zed and others · Connect your AI

Windsurf, Zed, Perplexity, Microsoft 365 Copilot, and any client that speaks MCP over HTTP.

The brain speaks standard MCP over HTTP with OAuth 2.1, so any client that supports remote MCP servers can connect. This page covers the ones people ask about, and the general recipe for anything else.

What every client needs

Transport	Streamable HTTP. The endpoint is `https://YOUR-BRAIN.brain.lanbrain.ai/mcp`
Auth	OAuth 2.1 with automatic client registration and PKCE. The brain publishes its discovery documents, so a client that supports OAuth needs no client ID
Not supported	SSE-only clients, and clients that can only send a static API key (see the last section)

Your MCP URL is in the dashboard under Your brain, then Connect AI client.

Windsurf

Windsurf's docs now live with Devin (Cognition); the product still ships the same config.

Open Settings, then Cascade, then MCP Servers, or click the MCP icon in the Cascade panel, and open the raw config. The file is ~/.codeium/windsurf/mcp_config.json.
Add the brain. Note the field is serverUrl, not url:

json

{
  "mcpServers": {
    "lan-brain": {
      "serverUrl": "https://YOUR-BRAIN.brain.lanbrain.ai/mcp"
    }
  }
}

Save, refresh the MCP list, and complete the OAuth sign-in when Windsurf prompts for it.
Paste the instructions block into your global rules (Settings, then Cascade, then Rules) or a .windsurfrules file in the repo.

Zed

Open Settings, then AI, then MCP Servers, and choose Add Remote Server.
Or edit settings.json directly:

json

{
  "context_servers": {
    "lan-brain": {
      "url": "https://YOUR-BRAIN.brain.lanbrain.ai/mcp"
    }
  }
}

Complete the sign-in when Zed prompts, then enable the server in the agent panel's tools.
Paste the instructions block into a .rules file at the repo root, or the agent's default profile instructions.

Perplexity

Custom remote connectors are an Enterprise feature. In Account settings, then Connectors, choose Custom connector, then Remote, paste the MCP URL, choose OAuth 2.0 and Streamable HTTP, and add. Members of an Enterprise org can only add their own connectors if an admin allows it. On personal Pro plans remote connectors were still rolling out as of September 2026.

Microsoft 365 Copilot and Copilot Studio

There is no self-serve path for end users. A tenant admin can register the brain as a custom connector from the Microsoft 365 admin center (Copilot, then Connectors, then Create a new connector, then Connect to MCP server) and deploy it to users. Makers in Copilot Studio can add it to an agent under Tools, then Add a tool, then Model Context Protocol, choosing OAuth 2.0 with dynamic discovery. Send your admin this page and your MCP URL.

Any other MCP client

If a client accepts a remote HTTP MCP URL and supports OAuth, follow its "add remote server" flow with your MCP URL and sign in when prompted. Then put the instructions block wherever that client keeps system or custom instructions. If the client cannot do OAuth and only accepts a static key, it cannot connect on its own today; write to info@lanbrain.ai with the client name and the use case, and we can issue a scoped token for automation, revocable per brain.

Try it

"Search the brain for how we name environments, then follow it."
"List the decisions tagged with security and open the most recent one."

If something is off

Most failures on this page are one of three things: the URL does not end in /mcp, the client field name is different (serverUrl, url, httpUrl), or the client needs a restart to re-read its config. After that, see Troubleshooting.