Setting Up MCP in Zed: Complete Configuration Guide

What is Zed?

Zed is a next-generation code editor built from the ground up in Rust for maximum performance. Created by the team behind Atom and Tree-sitter, Zed offers native speed, real-time collaboration, and integrated AI assistance.

With MCP support (via “context servers”), Zed's AI assistant can access external tools, databases, and APIs—extending its capabilities beyond the codebase.

Context Servers Overview

Zed uses the term “context servers” for MCP servers. There are three ways to add them:

Configuration Location

Context servers are configured in Zed's settings.json file:

# Open settings with:# Cmd+, (macOS) or Ctrl+, (Linux)# Or via Command Palette: "zed: open settings"# Settings location:# macOS: ~/Library/Application Support/Zed/settings.json# Linux: ~/.config/zed/settings.jsons.json

Installing via Extensions

The easiest way to add MCP servers is through Zed's extension gallery:

1. Open the Extensions panel (Cmd+Shift+X)
2. Search for the MCP server you want (e.g., “postgres”, “puppeteer”)
3. Click “Install” on the extension
4. Configure any required settings in settings.json
5. The context server will be available in the AI panel

Popular MCP Extensions

Custom Server Configuration

For custom MCP servers not available as extensions, configure them directly in settings.json:

Basic Structure

{
  "context_servers": {
    "server-name": {
      "command": "executable",
      "args": ["arg1", "arg2"],
      "env": {
        "ENV_VAR": "value"
      }
    }
  }
}

Configuration Fields

Configuration Examples

Filesystem Server

Allow the AI to read and write files in specific directories:

{
  "context_servers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/username/projects",
        "/Users/username/documents"
      ]
    }
  }
}

GitHub Integration

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

Remote HTTP Server

Connect to a remote MCP server:

{
  "context_servers": {
    "remote-api": {
      "url": "https://api.example.com/mcp",
      "headers": {
        "Authorization": "Bearer your-api-token"
      }
    }
  }
}

Multiple Servers

{
  "context_servers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/home/user/projects"]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxx"
      }
    },
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres"],
      "env": {
        "POSTGRES_CONNECTION_STRING": "postgresql://user:pass@localhost:5432/db"
      }
    }
  }
}

Agent Profiles

Zed allows you to create custom agent profiles to control which tools are available in different contexts. This is useful for creating specialised AI assistants.

Creating Agent Profiles

Define profiles in your settings.json:

{
  "agent": {
    "profiles": {
      "default": {
        "tools": {
          "filesystem": true,
          "github": true,
          "postgres": false
        }
      },
      "database-admin": {
        "tools": {
          "filesystem": false,
          "github": false,
          "postgres": true
        }
      },
      "full-access": {
        "tools": {
          "filesystem": true,
          "github": true,
          "postgres": true
        }
      }
    }
  }
}

Tool Approval Settings

By default, Zed asks for approval before executing MCP tools. You can configure this behaviour in settings:

Always Allow Tools

To skip approval prompts for all tool actions:

{
  "agent": {
    "always_allow_tool_actions": true
  }
}

Per-Tool Approval

When approval is required (default), Zed will prompt you before each tool execution. You can:

• ●Approve: Execute the tool this time
• ●Deny: Skip the tool execution
• ●View Details: See the parameters before deciding

Troubleshooting

References & Further Reading