Skip to main content
Zed stores MCP servers under context_servers, not mcpServers. Add a remote server from Settings → AI → MCP Servers, or edit the settings file.
You need your PostQueen API key first. In the app at app.postqueen.ai, open Settings → API Keys and click Reveal.
If a remote server has no Authorization header, Zed starts the standard MCP OAuth flow. PostQueen /mcp with an API key is not that flow. Always send Authorization: Bearer YOUR_API_KEY. Putting the key in the URL is not enough on its own: without the header, Zed still tries OAuth.

​
Option A: Zed UI

1

Open MCP Servers

Settings → AI → MCP Servers. The same page is under agent: open settings, then MCP Servers.
2

Add a remote server

Click Add Server → Add Remote Server. Name it postqueen. Paste the MCP URL and the Bearer header.

​
Option B: settings.json

Open the settings file with zed: open settings file.
Shape per Zed’s MCP documentation. A green indicator next to postqueen on the MCP Servers page means the server is active.
Your API key can post to every account you have connected. Settings files are plain text. If the key leaks, regenerate it in Settings → API Keys and update every client that uses it.

​
Self-hosted

Swap the host for your NEXT_PUBLIC_BACKEND_URL. Most self-hosted setups serve the backend under /api, so the path sits at /api/mcp. The reverse proxy has to forward /mcp and stream the response: MCP on a self-hosted install.

​
Verify

In the Agent Panel, ask:
“List my connected social media accounts”
Your channel names come back when Zed calls integrationList. If the indicator is not green, open Settings → AI → MCP Servers and confirm the Authorization header is present.