Creativity · MCP — client

Zed Editor as an MCP Client

Zed is a GPU-accelerated code editor written in Rust, and it is a full Model Context Protocol client. MCP servers (called 'context servers' in Zed's UI) are configured in settings.json; once loaded they become tools the Zed Assistant Agent can call while editing code. It is the fastest native-desktop experience for MCP-enabled coding.

MCP facts

Kind: client
Ecosystem: anthropic-mcp
Language: native (Rust / GPUI)
Transports: stdio, http, sse

Capabilities

Loads MCP servers via settings.json context_servers block
Assistant Agent auto-discovers tools and reasons about when to call them
Extensions marketplace — install common MCP servers with one click
Per-project .zed/settings.json for shared team configuration

Install

Install Zed from https://zed.dev, then edit settings.json

Configuration

{
  "context_servers": {
    "github": {
      "command": {
        "path": "npx",
        "args": ["-y", "@modelcontextprotocol/server-github"],
        "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxx" }
      }
    }
  }
}

Frequently asked questions

Why does Zed call them 'context servers' instead of MCP servers?

Zed's context_servers entry in settings is their name for the MCP integration point. The wire protocol is standard MCP, so any server that works in Claude Desktop or Cursor works in Zed with a slightly different config shape.

Does Zed support remote HTTP MCP servers?

Yes — you can configure URL-based servers, and the extensions marketplace has one-click installers for popular hosted servers (GitHub, Notion, Linear). Stdio servers are the default for local work.

How does Zed's Assistant compare to Cursor's Agent?

Zed's Assistant emphasises native-Rust performance and tight collaborative editing; Cursor's Agent leans into code-generation breadth and has larger model defaults. Both speak MCP, so the server ecosystem is shared.

Sources

Zed — Model Context Protocol — accessed 2026-04-20
Zed documentation — accessed 2026-04-20