Use browser.city in Zed via MCP (context server)

Zed supports MCP via context servers. The easiest way to connect to a hosted remote MCP endpoint is using the mcp-remote bridge (runs as a local process, speaks stdio to Zed, and connects to your remote server).

1) Set your API key

Set BROWSERCITY_API_KEY in your environment.

2) Add browser.city as a context server in Zed

Edit your Zed settings (commonly ~/.config/zed/settings.json) and add a context server.

This version uses npx to run mcp-remote and passes the Authorization header:

{
  "assistant": {
    "context_servers": {
      "browsercity": {
        "command": {
          "path": "bash",
          "args": [
            "-lc",
            "npx -y mcp-remote https://mcp.browser.city/mcp --header \"Authorization: Bearer $BROWSERCITY_API_KEY\""
          ]
        }
      }
    }
  }
}

Notes:

• Using bash -lc allows $BROWSERCITY_API_KEY to expand from your shell environment.
• If you prefer to avoid a shell, you can install mcp-remote globally and provide the token value directly in --header.
• Zed currently expects remote MCP servers over SSE. If your browser.city deployment uses a different MCP URL, swap it in place of https://mcp.browser.city/mcp.

3) Use it

Open the Assistant in Zed and ask it to use browsercity tools:

Open a browser, navigate to a URL, and return markdown.