How to connect Runheed to Zed

Zed calls MCP servers context servers. Add Runheed to your settings and the agent panel can read your production errors.

Runheed is an error tracker with an MCP server: your app reports exceptions through a small SDK, and Zed reads them through the server below.

Steps

1. Create an agent key in Runheed under Settings > Agent keys.
2. Add the runheed entry below under context_servers in your settings file.
3. Open Settings > AI > MCP Servers: the dot next to runheed turns green and its tooltip says "Server is active".

Where the config lives: Your Zed settings file (zed: open settings file), under "context_servers". Or Settings > AI > MCP Servers > Add Server > Add Local Server.

{
  "context_servers": {
    "runheed": {
      "command": "npx",
      "args": [
        "-y",
        "https://runheed.com/dl/runheed-mcp-0.1.0.tgz"
      ],
      "env": {
        "RUNHEED_API_KEY": "al_your_key"
      }
    }
  }
}

The npm and PyPI releases are not out yet, so these commands install the same package files straight from runheed.com. Nothing else changes when the registry versions ship.

The server runs with npx, so Node.js 18 or newer must be installed on the machine.

Check that it works

In the agent panel: "Use Runheed to list errors from the last 24 hours."

If the agent reports a problem

Every Runheed tool error says what went wrong and where to fix it. The common ones:

"RUNHEED_API_KEY is not set"

The key is missing from the server env. Add it and restart the client.

"That is a project key (pk_...)"

You pasted the DSN key. The MCP server needs an agent key that starts with al_.

"This agent key is not recognised"

Typo, or the key was revoked. Create a new one in Settings; keys are shown once.

"The workspace has no active plan"

Choose a plan or fix the card in Settings > Billing. The key works again as soon as the plan is active.

"No errors have been reported yet"

The agent side works. Check that the app has RUNHEED_DSN set and calls runheed.init() at startup.

Still need the SDK side? See the setup docs, or tell Zed: Read https://runheed.com/SETUP.txt and set up error tracking. Official reference: Zed MCP docs.

Other clients: Claude Code · Cursor · Claude Desktop · VS Code · Windsurf · Codex CLI · Gemini CLI · Cline