Cursor

Install the Runstack MCP server in Cursor over HTTP or stdio — one-click deeplinks and mcp.json configuration.

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

cursor

Connect Cursor to Runstack so Agent can use the four MCP tools against your linked toolkits. You need a Runstack API key (rnsk_…) from API Keys.

One-click install

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

Install links for Cursor MCP configuration are available in the interactive docs.

Deeplinks use cursor://anysphere.cursor-deeplink/mcp/install?name=…&config=… where config is base64-encoded JSON (same shape as below).

Manual setup (mcp.json)

Add Runstack in Cursor Settings → MCP or in a project file at .cursor/mcp.json (or globally at ~/.cursor/mcp.json). Full format: Cursor MCP docs.

HTTP (hosted /mcp)

{
  "mcpServers": {
    "runstack": {
      "url": "https://app.runstack.engineer/mcp",
      "headers": {
        "Authorization": "Bearer ${env:RUNSTACK_API_KEY}",
        "Content-Type": "application/json"
      }
    }
  }
}

Set RUNSTACK_API_KEY in your shell or use envFile with a local .env (stdio only supports envFile; for HTTP, prefer ${env:…} in headers).

stdio (@rnsk/mcp)

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

Restart Cursor or reload MCP from Customize after saving. For logs: Output → MCP Logs.

Verify

In chat, ask Agent to run search_tools for a toolkit you use (for example linear). You should see the four Runstack meta tools under available MCP tools.