How to add an MCP server to Windsurf and Zed (2026 guide)

How Plugsky MCP works in practice

Everything in this guide runs on Plugsky’s live MCP endpoint (https://plugsky.com/mcp) or the npm bridge (npx -y @plugsky/mcp). A client request flows: JSON-RPC over Streamable-HTTP → auth (API key or OAuth 2.1 + Dynamic Client Registration with fine-grained scopes) → tool router → the service you asked for. Model calls run behind a 7-tier provider failover chain; browsing renders with headless Chromium; transcripts come from real captions and Groq Whisper; images generate on FLUX; code runs in a sandbox with no network; memory persists in your account (Postgres-backed); and every tool call is metered per user on your dashboard.

Relevant live tools for this article: plugsky_browser_session — persistent Chromium profiles from Cascade/Zed.

How to add an MCP server to Windsurf and Zed (2026 guide)

Direct answer

To add an MCP server to Windsurf: edit ~/.codeium/windsurf/mcp_config.json and add your server under mcpServers with a command (stdio) or serverUrl (remote). To add an MCP server to Zed: open Zed settings, add an entry under context_servers with command and env, or use the built-in zed: add mcp server command. Both hot-reload on save. Windsurf ships MCP inside its Cascade agent; Zed exposes MCP inside its Assistant panel.

Key facts

Config file	~/.codeium/windsurf/mcp_config.json	~/.config/zed/settings.json
Config key	mcpServers	context_servers
Auth	Bearer, stdio env	OAuth 2.1, Bearer, stdio env
Primitives	Tools, Resources	Tools
Reload	Hot on save	Hot on save
Interface	Cascade agent panel	Assistant panel
Free tier for MCP	✅	✅

TL;DR

• Windsurf: ~/.codeium/windsurf/mcp_config.json with the same schema as Claude — top-level mcpServers.
• Zed: context_servers inside Zed's settings.json.
• Both are hot-reload — no restart.
• Both support Plugsky's remote MCP via Bearer today; Zed also supports OAuth 2.1.

How it works

Windsurf — step-by-step

1. Open ~/.codeium/windsurf/mcp_config.json (create if missing).
2. Add:

```json

{

"mcpServers": {

"plugsky": {

"serverUrl": "https://plugsky.com/mcp",

"headers": { "Authorization": "Bearer sk-live-YOUR_KEY" }

}

}

}

```

1. Save. Windsurf's Cascade panel picks up the tools immediately.
2. Try: "Cascade, use plugsky_route to pick the cheapest model that handles Arabic RTL correctly, then refactor this string."

Zed — step-by-step

1. Cmd+, opens ~/.config/zed/settings.json.
2. Add:

```json

{

"context_servers": {

"plugsky": {

"command": "npx",

"args": ["-y", "@plugsky/mcp"],

"env": { "PLUGSKY_API_KEY": "sk-live-YOUR_KEY" }

}

}

}

```

1. Save. Zed hot-reloads. Open the Assistant panel and pick the Plugsky tools you want available.

Why some devs prefer Windsurf's Cascade for MCP

Cascade is Windsurf's autonomous agent — closer in style to Cursor Composer than to Copilot Chat. MCP tools appear as available capabilities and Cascade decides when to invoke them across multi-file edits. This shines when you want the agent to browse Plugsky's models, pick one, and use it to refactor code across the workspace in one continuous plan.

Why Zed is winning with Rust/Go devs

Zed is written in Rust, uses GPU-accelerated rendering, and stays snappy at massive project sizes. Its MCP support is minimal on purpose — tools only, no Prompts UI — but the speed makes it a great match for high-throughput coding sessions where MCP calls should feel instant.

Common errors and fixes

Windsurf: tools don't appear	JSON invalid — validate with jq
Windsurf: OAuth server won't connect	Windsurf prefers Bearer; if OAuth-only, run a local proxy
Zed: context_servers unknown	Update Zed — MCP support requires 0.170+
Both: 401	Wrong Bearer scope; regenerate with tool-execution scope

Comparison — Windsurf vs Zed for MCP

Config style	JSON, mcpServers	JSON, context_servers
OAuth 2.1	⚠️ (Bearer preferred)	✅
Autonomous agent	✅ Cascade	⚠️ Simpler assistant
Speed	Standard	Blazing (GPU-native)
Best for	Large multi-file agent flows	Rust/Go, huge repos

FAQ

Q: Does Windsurf Codeium support OAuth 2.1 MCP?

A: Officially Bearer-preferred as of Sept 2026. OAuth support is on the roadmap but not fully shipped.

Q: Which version of Zed added MCP support?

A: Zed 0.170 introduced context_servers. Update to the latest for the full spec.

Q: Can I run the same Plugsky config on Windsurf and Zed?

A: The server URL and Bearer key are the same, but the JSON schema differs (mcpServers/serverUrl in Windsurf, context_servers/command in Zed).

Q: Is MCP in Windsurf a paid feature?

A: No — MCP works on Windsurf's free tier.

Q: Are Prompts (slash-commands) supported in Zed?

A: Not yet as of Sept 2026 — Tools only.

Trust & sources

• Author: Mustafa Hasan.
• Last updated: {DATE}.
• References: Windsurf MCP docs, Zed context servers docs.
• Related: [Add MCP to Cursor](/blog/add-mcp-to-cursor) · [Add MCP to VS Code](/blog/add-mcp-to-vscode).