Zed

Connect Runstack MCP in Zed via context_servers — stdio with @rnsk/mcp or remote HTTP.

Source: https://runstack.engineer/docs/mcp-zed

zed

Zed's Agent Panel uses context_servers (not mcpServers) in settings.json to configure MCP servers. Wire it to Runstack's MCP tools at https://app.runstack.engineer/mcp.

Prerequisites

Zed with Agent Panel enabled
Runstack API key — API Keys (rnsk_…)

Open settings

Zed → Settings → Open Settings (zed: open settings file) or Settings → AI → MCP Servers → Add Server.

Remote HTTP (Streamable HTTP)

{
  "context_servers": {
    "runstack": {
      "url": "https://app.runstack.engineer/mcp",
      "headers": {
        "Authorization": "Bearer rnsk_YOUR_API_KEY"
      }
    }
  }
}

If Zed prompts for OAuth without a header, keep the Authorization header configured. Restart the Agent Panel if tools do not appear.

stdio (`@rnsk/mcp`) — recommended for Zed

Zed does not support HTTP natively in all builds without mcp-remote. The stdio bridge @rnsk/mcp is the most reliable path:

{
  "context_servers": {
    "runstack": {
      "command": "npx",
      "args": ["-y", "@rnsk/mcp"],
      "env": {
        "RUNSTACK_API_KEY": "rnsk_YOUR_API_KEY"
      }
    }
  }
}

For a remote endpoint over stdio, some Zed users wrap with npx -y mcp-remote https://app.runstack.engineer/mcp --header "Authorization: Bearer rnsk_..." — prefer the direct URL config above when available.

Extensions alternative

Many MCP servers are available as Zed extensions (zed: extensions → filter context-servers). Runstack is configured as a custom server (above), not an extension.

Tool permissions

In Agent Panel → agent.tool_permissions.default:

confirm (default) — approves each mcp:runstack:* tool call
allow — auto-approves

For granular control, use per-tool keys like mcp:runstack:execute_tool.

Verify

In Agent Panel: “Use Runstack to search for Linear issue tools”. Confirm the four meta tools appear under context servers and are green/active in Settings → AI → MCP Servers.

Zed