Giga / MCP

Giga MCP server

Connect compatible AI clients to the tools available in your Giga workspace and its connected integrations.

Connection

Use the production Streamable HTTP endpoint:

https://app.getgiga.com/mcp

The endpoint uses MCP over Streamable HTTP. It is not an HTTP+SSE or local stdio server. Each request must advertise both application/json and text/event-stream response support as required by the protocol.

Authentication

Giga requires an OAuth bearer access token in the Authorization header. MCP clients should start at the endpoint and follow the protected-resource metadata URL in its 401 Unauthorized response. Giga supports authorization code with PKCE (S256), refresh tokens, token revocation, and dynamic client registration. Do not put tokens in URLs or this manifest.

• Protected resource metadata
• Authorization server metadata
• Registry-format server manifest

Scopes

Request the least privilege needed. Resource families use read and write scopes: identity, integrations, tracks, spaces, memory, slack, pulses, skills, workflows, powerups, and admin, all prefixed with giga:. Additional capability scopes currently advertised by the authorization server are giga:vault:use, giga:browser, giga:sessions, and giga:tools.

Available tools and their JSON Schemas depend on the authenticated account, granted scopes, and connected services. After authorization, use MCP tools/list as the authoritative catalog. This page intentionally does not publish a guessed static tool list.

Security boundary

The marketing site hosts only this documentation and manifest. MCP requests, OAuth tokens, account data, and tool execution go directly to app.getgiga.com; they are not processed by getgiga.com. Tool calls remain subject to the permissions of the authenticated Giga account and its connected services.