Connect Gigamcp to Claude Desktop

Claude Desktop ships with MCP support built-in. Configuration lives in a JSON file under your OS user profile.

Recommended: 1-click OAuth

Recent Claude Desktop builds support OAuth-based MCP connections directly — no token to mint, no JSON to edit. In the app go to Settings → Connectors → Add MCP server, paste your workspace URL (e.g. https://app.gigamcp.io/t/acme/mcp), and click Authorize when the browser opens. See OAuth for MCP for the full flow. Manage and revoke from Connected apps.

On an older Claude Desktop or running a kiosk-style setup that needs a static token? Use the machine-token instructions below.

1. Mint your API key

Same as for Cursor — in the Gigamcp app go to Settings → API keys and click Generate. Copy the gmcp_…token. Every workspace member can self-mint; up to 5 active keys per person. The key authenticates as you — your group memberships gate which content Claude can read.

2. Open `claude_desktop_config.json`

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

3. Add the Gigamcp server

{
  "mcpServers": {
    "gigamcp": {
      "transport": "http",
      "url": "https://app.gigamcp.io/t/acme/mcp",
      "headers": {
        "Authorization": "Bearer gmcp_..._..."
      }
    }
  }
}

4. Restart Claude Desktop

Quit completely and re-open. The "MCP servers" indicator at the bottom of the message bar should show gigamcp as connected.

5. Try it

Ask Claude something like "Find me the latest deploy runbook in our docs". Claude will request approval to use thesearch_company_rag tool, then surface the results.

Tip: per-tenant toggles

Claude Desktop lets you enable / disable each MCP server per conversation. If you have separate workspaces (work, side project), add both and toggle accordingly.