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

Gemini CLI

Configure Runstack MCP in Gemini CLI via settings.json — mcpServers with HTTP or stdio.

Source: https://runstack.engineer/docs/mcp-gemini-cli

geminiCli

Gemini CLI loads MCP servers from settings.json. Point it at Runstack's MCP tools to search the registry and execute toolkit actions.

Config file

  • Global: ~/.muse/settings.json
  • Project: .muse/settings.json (workspace root)

Create the file if it does not exist. Requires Gemini CLI ≥ 0.3 and a Runstack key from API Keys.

HTTP (Streamable HTTP)

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

Some builds accept url or serverUrl instead of httpUrl. If tools do not load, try "url": "https://app.runstack.engineer/mcp".

stdio (@rnsk/mcp)

For a local subprocess (no HTTP config):

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

Environment

Do not mix GEMINI_API_KEY and RUNSTACK_API_KEY. Keep RUNSTACK_API_KEY in shell env or env above; restart Gemini CLI after changing.

Verify

gemini "Use Runstack to search for GitHub tools and list what you found"

Confirm search_tools is discovered in /mcp status. OAuth flows (Gmail, GitHub, etc.) still open via Runstack when check_authentication requires it.

Related