Warp

Add Runstack MCP in Warp terminal — Settings → MCP servers or file-based .warp/.mcp.json.

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

warp

Warp local agents can call Runstack's MCP tools over Streamable HTTP or stdio. Auth with Authorization: Bearer rnsk_… from API Keys.

Add via UI

Settings → Agents → MCP servers (or Warp Drive → Personal → MCP Servers or Command Palette → Open MCP Servers)
Click + Add
Choose Streamable HTTP or SSE Server (URL) or CLI Server (Command)
Paste one of the configs below and save.

HTTP (Streamable)

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

stdio (`@rnsk/mcp`)

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

Set working_directory only if your command uses relative paths.

File-based config

Warp auto-detects file configs (global auto-spawns; project-scoped requires approval):

Warp global: ~/.warp/.mcp.json
Warp project: .warp/.mcp.json at project root
Also reads Claude Code / Codex / .agents/.mcp.json if Auto-spawn servers from third-party agents is toggled on.

Example ~/.warp/.mcp.json:

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

The built-in /agent-add-mcp skill can write this file for you.

Manage

On the MCP servers page, Start/Stop the server, View Logs for diagnostics, and Share (env vars are scrubbed). Closing Warp with a server running restarts it on next launch.

Logs: ~/Library/Group Containers/2BBY89MBSN.dev.warp/Library/Application Support/dev.warp.Warp-Stable/mcp (macOS).

Verify

Open a Warp Agent and prompt: “Use Runstack to search for Linear tools”. Check the MCP servers page shows runstack green/active and tools search_tools/execute_tool are available.