Docs · static mirror — the interactive version loads with JavaScript.

Windsurf

Add the Runstack MCP server in Windsurf (Codeium) via mcp_config.json — HTTP or stdio.

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

windsurf

Windsurf's Cascade agent can call Runstack's four MCP tools at https://app.runstack.engineer/mcp. You need a Runstack API key (rnsk_…) from API Keys.

Configuration file

Windsurf reads MCP servers from mcp_config.json:

  • macOS / Linux: ~/.codeium/windsurf/mcp_config.json
  • Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

Create the file if it does not exist.

HTTP (hosted /mcp)

{
  "mcpServers": {
    "runstack": {
      "serverUrl": "https://app.runstack.engineer/mcp",
      "headers": {
        "Authorization": "Bearer rnsk_YOUR_API_KEY",
        "Content-Type": "application/json"
      }
    }
  }
}

Some Windsurf builds accept url instead of serverUrl. If tools do not appear, try replacing serverUrl with url. Replace the placeholder with your key.

stdio (@rnsk/mcp)

If you prefer a local subprocess over HTTP, use the stdio bridge @rnsk/mcp:

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

Set RUNSTACK_API_KEY or hardcode the key in env (not recommended for shared machines).

Reload

Restart Windsurf or reload Cascade after saving. Open Cascade → confirm Runstack meta tools (search_tools, check_authentication, initiate_connection, execute_tool) are listed.

Verify

Ask Cascade: “Use Runstack to search for GitHub issue tools”. It should discover tools via search_tools and prompt for OAuth via initiate_connection when needed.

Related