gigamcp/ docs

Connect Gigamcp to ChatGPT (Custom Connectors)

ChatGPT’s Custom Connectors directory speaks Streamable HTTP MCP over OAuth 2.1. Gigamcp is a first-class MCP server: paste your workspace URL, authorize once in a popup, and ChatGPT can search your company knowledge base, read connector resources, and call any tool you expose.

Recommended: 1-click OAuth— ChatGPT registers itself dynamically (RFC 7591), there’s no token to copy, and revocation lives in your gigamcp Connected apps page.

1. Open ChatGPT settings

ChatGPT (Pro / Team / Enterprise) → Settings → Connectors → Add connector. You’ll see fields for the connector name and the MCP server URL.

2. Paste your workspace MCP URL

https://app.gigamcp.io/t/<your-workspace-slug>/mcp

The slug is the same one in your gigamcp dashboard URL (e.g. acme for https://app.gigamcp.io/t/acme).

3. Authorize

ChatGPT pops up a gigamcp login window. Sign in with your gigamcp account (the same one that’s a member of the workspace), review the requested scopes, and click Authorize. The popup closes automatically and ChatGPT confirms the connector is live.

Default scopes for ChatGPT: mcp:read + mcp:tools. That covers listing tools, reading resources, and invoking tools like the built-in search_company_rag.

4. Try it

In a chat, ask ChatGPT to “Search the wiki for our incident-response runbook” or “Summarize the latest GitHub issues from the auth-service repo”. It will pick up the gigamcp tools and return cited results.

Multiple workspaces

Add one connector per workspace. ChatGPT lets you toggle each independently in the Connectors panel.

Revoking access

From gigamcp: Connected apps → Revoke next to the ChatGPT row. From ChatGPT: Settings → Connectors → Disconnect. Either side stops the integration; doing both keeps your workspace tidy.

Troubleshooting

  • “Connector failed to register”. Your network may be blocking app.gigamcp.io. ChatGPT’s DCR call is a single POST to /api/oauth/server/register; verify it succeeds from your network.
  • “Authorization failed”.Make sure you’re signing in with a gigamcp account that is a member of the workspace. If you have multiple workspaces, switch to the right one first inside gigamcp, then retry.
  • “invalid_token” on tool calls.The connector is bound to a specific workspace URL via Resource Indicators (RFC 8707). Reusing a connector across workspaces won’t work — add a separate connector per workspace.

Under the hood

Curious about the exact OAuth surface ChatGPT uses? See the OAuth for MCP reference for the discovery URLs, scopes, and sequence diagram.