Where do you configure MCP servers in Zed, and where do their tools appear?

Flashcard·Easy·4.0 · 0·~30s·Asked atCursor·Relevant atAnthropic Microsoft Zed

Attempt it

Zed (the GPU-accelerated collaborative editor written in Rust by the original Atom team) supports MCP through what it calls context_servers. You declare them in ~/.config/zed/settings.json under the context_servers key, not in a separate file. Each entry takes command + args + env for a local stdio server or url for a remote streamable HTTP endpoint. Once loaded, the Assistant panel (the AI chat surface on the right side of the editor) can call any tool the server exposes, mixing MCP tool calls with Zed's built-in slash commands. Zed was one of the first non-Anthropic hosts to ship MCP support (early 2025) and remains a common reference host that server authors test against to confirm cross-vendor portability.

Your answer

Quick reference

TL;DR

Zed loads MCP servers from `~/.config/zed/settings.json` under `context_servers`; their tools become callable inside Zed's Assistant panel.

Memory aid

Easy to grasp

Imagine an editor that already has a built-in writing helper in a side panel. The helper can answer questions and edit your file, but it has no idea about your database, your tickets, or your team's documentation. MCP is how you teach the helper new tricks. In Zed you do that by opening the editor's main settings file and adding an entry under `context_servers` for each external helper you want loaded. Save, and the helper in the side panel can now talk to the new server and use whatever tools it offers, all without leaving Zed.

Key concepts

Zed editor MCP host IDE integration

Detailed answer & concept explanation

~5 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.

Quick scan · 2–4 min

Everything important, quickly.

3 min: Zed as a Rust-based editor from the Atom team, early 2025 MCP adoption, `context_servers` terminology and reasoning, settings.json location, Assistant panel as the consumer, reference host status for portability testing.

Real-world examples

Real products, models, and research that use this idea.

A Rust developer using Zed adds a cargo MCP server under `context_servers` so the Assistant panel can run targeted builds and read compiler errors as structured tool output.
A team uses Zed's collaborative sessions to pair-program, with a shared Postgres MCP server loaded so both participants' Assistant panels can query the dev database in the same conversation.
Server authors testing cross-vendor portability run their server against Zed (alongside Claude Desktop and Cursor) to confirm `tools/list` and `tools/call` responses parse correctly in a non-Anthropic host.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QWhy did Zed choose `context_servers` instead of `mcpServers`?

QWhat did Zed's early MCP adoption demonstrate about the protocol's portability?

QHow would you debug a `context_servers` entry that fails to start in Zed?

Don't say this

Red flags and common mistakes that signal junior thinking. Click to expand.

Most common mistake

Looking for an `mcpServers` key in Zed's settings. Zed calls them `context_servers`, reflecting that an MCP server provides context (tools, resources, prompts), not just callable tools.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

References

Primary sources. Skim if you want the original framing.