Zed Setup

Learn how to connect your deployed ToolBoost MCPs to Zed, the high-performance collaborative code editor.

Overview

Zed is a next-generation code editor built for performance and collaboration. With MCP support, you can extend Zed's AI assistant with external tools and data sources from ToolBoost.

Prerequisites

• Zed installed (Download here)
• A ToolBoost account with at least one deployed MCP
• Your project's API key from ToolBoost dashboard

Finding Your Connection URL

1. Go to your MCP's detail page on ToolBoost
2. Ensure the MCP is deployed to your project
3. In the "Use" section, copy the connection URL:

https://toolboost.dev/server/author/mcp-name/mcp?api_key=YOUR_API_KEY

Configuration Steps

1. Open Zed Settings

macOS:

• Press Cmd + , (or Zed → Settings)
• Click "Open ~/.config/zed/settings.json"

Linux:

• Press Ctrl + ,
• Click "Open ~/.config/zed/settings.json"

Windows:

• Press Ctrl + ,
• Click "Open settings.json"

2. Add MCP Configuration

In your settings.json, add the MCP server configuration:

{
  "mcp": {
    "servers": {
      "your-mcp-name": {
        "url": "https://toolboost.dev/server/author/mcp-name/mcp?api_key=YOUR_API_KEY",
        "transport": "http"
      }
    }
  }
}

Replace:

• your-mcp-name - A friendly identifier (lowercase, no spaces)
• YOUR_API_KEY - Your ToolBoost project API key
• author/mcp-name - Your actual MCP path from ToolBoost

3. Multiple MCPs

To configure multiple MCP servers:

{
  "mcp": {
    "servers": {
      "github": {
        "url": "https://toolboost.dev/server/github/github-mcp-server/mcp?api_key=YOUR_API_KEY",
        "transport": "http"
      },
      "postgres": {
        "url": "https://toolboost.dev/server/modelcontextprotocol/servers-postgres/mcp?api_key=YOUR_API_KEY",
        "transport": "http"
      },
      "filesystem": {
        "url": "https://toolboost.dev/server/modelcontextprotocol/servers-filesystem/mcp?api_key=YOUR_API_KEY",
        "transport": "http"
      }
    }
  }
}

4. Save and Reload

1. Save the settings.json file
2. Reload Zed: Cmd/Ctrl + Q (quit) then reopen
3. Or use the command palette: Cmd/Ctrl + Shift + P → "zed: reload"

Project-Specific Configuration

For project-specific MCPs, create a .zed/settings.json file in your project root:

my-project/
├── .zed/
│   └── settings.json
├── src/
└── package.json

.zed/settings.json:

{
  "mcp": {
    "servers": {
      "project-db": {
        "url": "https://toolboost.dev/server/modelcontextprotocol/servers-postgres/mcp?api_key=YOUR_API_KEY",
        "transport": "http"
      }
    }
  }
}

This configuration only applies when working in this specific project.

Using Environment Variables

For better security, reference environment variables:

1. Set Environment Variables

macOS/Linux - Add to ~/.zshrc or ~/.bashrc:

export TOOLBOOST_API_KEY="tb_your_actual_key"

Windows - Set in System Environment Variables

2. Reference in Configuration

{
  "mcp": {
    "servers": {
      "github": {
        "url": "https://toolboost.dev/server/github/github-mcp-server/mcp?api_key=$TOOLBOOST_API_KEY",
        "transport": "http"
      }
    }
  }
}

3. Restart Zed

Quit and restart Zed to load the new environment variables.

Verifying the Connection

After configuration:

1. Open Zed's AI assistant panel
2. Type ? or / to see available commands
3. Your MCP tools should appear in the suggestions
4. Look for a green status indicator

Test Commands

Try these in Zed's AI assistant:

For GitHub MCP:

List my GitHub repositories

For Filesystem MCP:

What files are in the current project?

For Postgres MCP:

Show database tables

Common Issues & Solutions

MCP Not Loading

Problem: MCP doesn't appear in Zed.

Solutions:

• Verify JSON syntax (no trailing commas)
• Check that Zed was fully restarted
• Ensure "transport": "http" is set
• Review Zed's log: View → Debug → Open Log File

Connection Errors

Problem: "Failed to connect to MCP server" error.

Solutions:

• Verify internet connection
• Check the URL is correct (copy fresh from ToolBoost)
• Ensure API key is valid
• Confirm MCP is deployed in your ToolBoost project
• Check Zed's network settings

Authentication Failures

Problem: "401 Unauthorized" errors.

Solutions:

• Verify API key in the URL
• Check for typos or extra spaces
• Ensure API key hasn't been regenerated
• Try copying the connection URL again from ToolBoost

Slow Response Times

Problem: MCP tools are slow to respond.

Solutions:

• Check your internet speed
• Verify ToolBoost status at status.toolboost.dev
• Try with a simpler MCP first
• Consider timeout settings (see Advanced Configuration)

Complete Configuration Examples

Basic Setup

{
  "mcp": {
    "servers": {
      "github": {
        "url": "https://toolboost.dev/server/github/github-mcp-server/mcp?api_key=tb_abc123",
        "transport": "http"
      }
    }
  }
}

Multiple Projects

Global (~/.config/zed/settings.json):

{
  "mcp": {
    "servers": {
      "github": {
        "url": "https://toolboost.dev/server/github/github-mcp-server/mcp?api_key=tb_global",
        "transport": "http"
      }
    }
  }
}

Project A (.zed/settings.json):

{
  "mcp": {
    "servers": {
      "work-db": {
        "url": "https://toolboost.dev/server/modelcontextprotocol/servers-postgres/mcp?api_key=tb_work",
        "transport": "http"
      }
    }
  }
}

Project B (.zed/settings.json):

{
  "mcp": {
    "servers": {
      "personal-db": {
        "url": "https://toolboost.dev/server/modelcontextprotocol/servers-postgres/mcp?api_key=tb_personal",
        "transport": "http"
      }
    }
  }
}

With Environment Variables

{
  "mcp": {
    "servers": {
      "github": {
        "url": "https://toolboost.dev/server/github/github-mcp-server/mcp?api_key=$TOOLBOOST_API_KEY",
        "transport": "http"
      },
      "postgres": {
        "url": "https://toolboost.dev/server/modelcontextprotocol/servers-postgres/mcp?api_key=$TOOLBOOST_API_KEY",
        "transport": "http"
      }
    }
  }
}

Zed-Specific Features

AI Assistant Integration

Zed's AI assistant deeply integrates with MCPs:

• Inline completions: MCP data informs code suggestions
• Chat interface: Ask questions that use MCP tools
• Context-aware: Zed understands when to use which MCP

Collaboration

When collaborating in Zed:

• MCPs work in shared sessions
• All collaborators see MCP tool results
• Configure MCPs per collaborator or share project config

Performance

Zed optimizes MCP performance:

• Parallel requests to multiple MCPs
• Smart caching of MCP responses
• Minimal latency for tool invocations

Advanced Configuration

Custom Headers

Add custom headers for authentication:

{
  "mcp": {
    "servers": {
      "github": {
        "url": "https://toolboost.dev/server/github/github-mcp-server/mcp?api_key=YOUR_KEY",
        "transport": "http",
        "headers": {
          "Authorization": "Bearer YOUR_KEY",
          "X-Custom-Header": "value"
        }
      }
    }
  }
}

Timeout Configuration

Set custom timeouts (in milliseconds):

{
  "mcp": {
    "servers": {
      "github": {
        "url": "https://toolboost.dev/server/github/github-mcp-server/mcp?api_key=YOUR_KEY",
        "transport": "http",
        "timeout": 30000
      }
    }
  }
}

Debug Mode

Enable verbose logging:

{
  "mcp": {
    "debug": true,
    "servers": {
      // ... your servers
    }
  }
}

View logs: Zed → View → Debug → Open Log File

Keyboard Shortcuts

• AI Assistant: Cmd/Ctrl + .
• Command Palette: Cmd/Ctrl + Shift + P
• Settings: Cmd/Ctrl + ,
• Reload Window: From command palette

Best Practices

1. Project Configuration: Use .zed/settings.json for project-specific MCPs
2. Environment Variables: Store API keys in environment variables
3. Descriptive Names: Use clear, meaningful MCP names
4. Version Control: Add .zed/settings.json to .gitignore if it contains secrets
5. Keep Updated: Check for Zed updates regularly

Tips & Tricks

Quick MCP Status Check

1. Open command palette (Cmd/Ctrl + Shift + P)
2. Type "mcp"
3. See available MCP commands and status

Disable MCPs Temporarily

Comment out MCPs in your config:

{
  "mcp": {
    "servers": {
      // "github": {
      //   "url": "...",
      //   "transport": "http"
      // }
    }
  }
}

Test Connection

Use Zed's built-in network tester:

1. Command palette → "zed: test mcp connection"
2. Select your MCP
3. View connection status

Troubleshooting Checklist

• API key is correct and matches your ToolBoost project
• Connection URL is copied exactly from ToolBoost
• MCP is deployed and active in ToolBoost
• Zed has been fully restarted
• No JSON syntax errors in settings.json
• "transport": "http" is specified
• Internet connection is stable
• Check Zed's log file for detailed errors

Next Steps

• Configure Claude Desktop
• Set up Cursor
• Manage Environment Variables
• Deploy More MCPs

Need Help?

• Email: contact@toolboost.dev
• Zed Support: zed.dev/docs
• Zed Discord: discord.gg/zed
• ToolBoost Docs: docs.toolboost.dev