Connect Gigamcp to Cursor

Cursor speaks Streamable HTTP MCP natively. Two minutes of config and your AI sidebar can read every connector you've wired up.

Recommended: 1-click OAuth

Recent Cursor builds (1.0+) speak OAuth 2.1 to MCP servers natively. If your version supports it, you don’t need a token at all — paste your workspace URL into Cursor’s “Add MCP server” dialog and click Authorize when the browser pops up. See OAuth for MCP for the full flow. Manage and revoke from Connected apps.

Stuck on an older Cursor or scripting around the IDE? Use the machine-token instructions below.

1. Mint your tenant API key

Open the Gigamcp app, switch to your workspace, and go to Settings → API keys. Click Generate, name the key (e.g. cursor-laptop), and copy the token (gmcp_…_…) — it's only shown once.

Any workspace member can mint up to 5 active keys for themselves; you don't need to ask an admin. The key authenticates as you— your group memberships, audit attribution, and quota all flow through it. Revoking your membership immediately invalidates every key you minted in that workspace.

2. Edit your Cursor MCP config

Open ~/.cursor/mcp.json (create it if needed) and add:

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

Replace acme with your workspace slug and the token with the one you minted.

3. Reload Cursor

Cmd-Shift-P → MCP: Reload servers. The server should show up green in the MCP panel.

4. Try it

In a chat, ask "Search the wiki for our incident-response runbook" or "What does the auth-service README say about JWTs?". Cursor will pick up the search_company_rag tool and return cited results.

Per-project URLs

If you work across multiple workspaces, add one entry per slug with a clear name (gigamcp-acme, gigamcp-personal). Cursor lets you toggle each independently.

Troubleshooting

401 → the token is wrong, expired, or revoked. Check API keys in the admin console.
403 → your user is signed into the wrong workspace, or your membership was suspended.
429 → you've hit the rate limit for your plan (Free: 30 req/min). Upgrade or wait the cooldown.