Lovie MCP›Zed

Editor

Zed

Zed calls MCP servers context servers. Leave the Authorization header unset and it runs the standard MCP OAuth flow, which is exactly what Lovie expects.

The only value you need

• Time 1 minute
• Transport HTTP streamable
• Auth OAuth — in-app
• Key context_servers

Add the server

1. Open Settings → AI → MCP Servers.
2. Click Add Server, then Add Remote Server.
3. Name it lovie and paste https://mcp.lovie.co/mcp.
4. Leave the authorization header blank. Zed then runs the standard MCP OAuth flow and prompts you to sign in — which is what Lovie expects.
5. Approve in the browser. The server shows as running in the Agent Panel.

Or write settings.json

{
  "context_servers": {
    "lovie": {
      "url": "https://mcp.lovie.co/mcp"
    }
  }
}

Zed calls MCP servers context servers, so the container key is context_servers rather than mcpServers. A remote one needs only url.

Check it worked

• “Using Lovie, what is my current cap table?”
• “Summarize this month’s spending by category.”

If something goes wrong

Symptom	Cause
No sign-in prompt	An Authorization header is set. Remove it and restart the server.
Server not listed	The block is under mcpServers. Zed reads context_servers.
Tools not offered to the model	Enable the server in the Agent Panel’s tool list for the current thread.

Somewhere else