VS Code

Add the Runstack MCP server in VS Code using HTTP Streamable transport and Bearer auth.

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

vscode

VS Code supports MCP through workspace or user config. Runstack uses the same MCP tools and https://app.runstack.engineer/mcp endpoint as other clients.

Prerequisites

VS Code with MCP support (Command Palette: MCP: Open User Configuration)
Runstack API key — API Keys

One-click install

VS Code supports MCP install links. Click Open in VS Code for the transport you want, then replace the placeholder API key in the generated config.

Install links for VS Code MCP configuration are available in the interactive docs. Manual config: add {"servers":{"runstack":{"type":"http","url":"https://app.runstack.engineer/mcp","headers":{"Authorization":"Bearer rnsk_YOUR_API_KEY"}}}} to .vscode/mcp.json.

Links use vscode:mcp/install?{json} where {json} is URL-encoded JSON ({"name":…,"type":…,…}). Insiders builds use vscode-insiders:mcp/install?….

Manual setup (`mcp.json`)

Add Runstack in .vscode/mcp.json (workspace) or your user MCP config. VS Code expects HTTP servers under servers with type: "http":

{
  "servers": {
    "runstack": {
      "type": "http",
      "url": "https://app.runstack.engineer/mcp",
      "headers": {
        "Authorization": "Bearer rnsk_YOUR_API_KEY",
        "Content-Type": "application/json"
      }
    }
  }
}

Replace rnsk_YOUR_API_KEY with your key, or reference an environment variable if your VS Code MCP setup supports it.

Reload the window or restart the MCP server from the MCP view if tools do not appear.

stdio alternative

If your VS Code build prefers command-based MCP, use @rnsk/mcp the same way as Cursor stdio (npx -y @rnsk/mcp with RUNSTACK_API_KEY).

Verify