How to add an MCP server to Zed

Checked against Zed's documentation on Oct 26, 2026. Commands and config blocks are generated from the same install data as each listing page.

1. 1. Choose a server and see what it needs

   Zed keeps a server in your user settings file, and you can also add one from the settings screen named in the notes. The notes also say what each example server needs.

   • Playwright MCP: runs locally, no key needed.
   • Figma MCP Server: hosted, connect by URL, no key needed.
   • Firecrawl MCP Server: runs locally, can take FIRECRAWL_API_KEY.
   • Where Zed can keep a server: user (settings.json). You can also add a server from Settings > AI > MCP Servers > Add Server.

2. 2. Add a local server (Playwright MCP)

   The entry goes under a context_servers key and holds a command, its arguments and an empty env.

   {
     "context_servers": {
       "playwright-mcp": {
         "command": "npx",
         "args": [
           "-y",
           "@playwright/mcp@0.0.82"
         ],
         "env": {}
       }
     }
   }

   Copy

3. 3. Add a remote server (Figma MCP Server)

   Figma MCP Server is hosted, so its entry in the block holds only a URL.

   {
     "context_servers": {
       "figma": {
         "url": "https://mcp.figma.com/mcp"
       }
     }
   }

   Copy

   • A remote entry with no Authorization header makes Zed start the standard MCP OAuth sign-in.

4. 4. Keep API keys out of the file (Firecrawl MCP Server)

   Firecrawl MCP Server can take FIRECRAWL_API_KEY. The notes say only literal env values and an Authorization header are documented, so the example entry holds the placeholder YOUR_FIRECRAWL_API_KEY for your own value.

   {
     "context_servers": {
       "firecrawl-mcp-server": {
         "command": "npx",
         "args": [
           "-y",
           "firecrawl-mcp@3.34.1"
         ],
         "env": {
           "FIRECRAWL_API_KEY": "YOUR_FIRECRAWL_API_KEY"
         }
       }
     }
   }

   Copy

   • Only literal env values and an Authorization header are documented. The docs describe no variable interpolation, so the token sits in settings.json.
   • This puts the value in settings.json in plain text; keep that file out of version control.
   • FIRECRAWL_API_KEY (optional): Your API key for Firecrawl.

5. 5. Restart or reload if the server does not appear

   Use this step if the server does not appear. The notes say what the docs state about restarts, trusted worktrees and tool-call confirmation.

   • The docs do not say a restart is needed after a settings change.
   • Project settings and MCP servers start only in trusted worktrees. Tool calls ask for confirmation unless agent.tool_permissions says otherwise.