Claude

Connect Giga to Claude with a custom remote MCP connector and use Giga's company context, permissions, and Connections from Claude.

Use Giga from Claude when you want Claude's interface with Giga's company context and connected systems underneath.

Giga is not yet listed in Claude's Connector Directory, so the current setup uses a custom connector backed by Giga's remote MCP server.

Connect Giga to Claude

Individual Claude accounts

Open Connectors

In Claude, go to Customize → Connectors.

Add a custom connector

Select + → Add custom connector.

Name the connector Giga.

Add Giga's MCP endpoint

Enter:

https://app.getgiga.com/mcp

Giga uses its normal OAuth flow, so you do not need to enter a separate Client ID or Client Secret.

Add and authenticate

Select Add.

Claude will open Giga's normal OAuth flow. Sign in to Giga if prompted and approve access so the connector can act with your Giga permissions.

Enable Giga in a Chat

In a Claude Chat, select the + button, open Connectors, and enable Giga for the conversation.

Team and Enterprise workspaces

On Claude Team and Enterprise, an Owner or Primary Owner first adds Giga for the organization:

Open organization connectors

Go to Organization settings → Connectors.

Add Giga

Select Add, hover over Custom, then choose Web.

Enter the Giga endpoint

Add https://app.getgiga.com/mcp and complete Giga's OAuth flow when prompted.

Let members connect

Each member then goes to Customize → Connectors, finds Giga, and selects Connect to authenticate individually.

Screenshot guide

Screenshot placeholder 1

Claude Customize → Connectors with the Add custom connector option visible.

Screenshot placeholder 2

The custom connector form with Giga and https://app.getgiga.com/mcp entered.

Screenshot placeholder 3

Giga shown as connected in Claude's Connectors list.

Screenshot placeholder 4

A Claude Chat with Giga enabled from the + → Connectors menu.

What carries through from Giga

Claude remains the interface. Giga continues to resolve the current user's permitted company context and capabilities.

Depending on the task and permissions, that can include:

Groups
Tracks and Track memory
Connections
Agents
Skills
files and other permitted company context

Giga's Company Brain remains permission-aware, so connecting Giga to Claude does not give a user access to company resources they could not otherwise use.

Using Giga in Claude

Enable Giga when the request needs company context, live connected data, or an action through Giga.

For example:

"Use Giga to summarize what changed on the Atlas Track this week."
"Use Giga to check the CRM and prepare me for this account."
"Use Giga to find the latest relevant company context for this decision."

A Chat can link to at most one Track, and the Track should be explicitly selected or confirmed.

Saving to Giga's memory

Say "save this" or "remember that". Giga asks which Track it belongs to, with Keep it private as an option, then saves the specific points you want kept, never the whole conversation. Anything kept private waits in Brain → To file in the Giga web app until you file it.

Learn how memory works from ChatGPT and Claude →

Availability

Anthropic currently supports custom remote MCP connectors on Claude Free, Pro, Max, Team, and Enterprise. Free accounts are limited to one custom connector, and Team/Enterprise organizations require an Owner to add the connector first.

For current Claude requirements, see Anthropic's custom connector guide.

Was this page helpful?