How to connect a Gamma MCP with Claude Code (5 steps)

Claude Code can generate structured content from any data source: changelog entries, sprint summaries, architecture decisions, incident postmortems. Getting that content into a polished Gamma deck still requires opening a browser, copying the output, and reformatting it by hand.

In other words, the gap between "Claude Code generated this" and "this is a shareable deck" is manual work that happens outside the terminal.

To help your developers create and update Gamma decks directly from generated content in the terminal, we'll show you how to connect Gamma with Merge Agent Handler's Gamma MCP server.

How it works

Merge Agent Handler sits between Claude Code and the Gamma API. You configure a Tool Pack and Registered User in Merge Agent Handler, which generates a unique MCP URL. Claude Code connects to that URL over HTTP and uses an API key (generated in Merge Agent Handler) for authentication.

Here's the connection config before you substitute your specific values:

claude mcp add 
--transport http --header "Authorization: Bearer YOUR_API_KEY"
agent-handler
"https://ah-api.merge.dev/api/v1/tool-packs/YOUR_TOOL_PACK_ID/registered-users/YOUR_REGISTERED_USER_ID/mcp"

Claude Code sends requests to that MCP URL, and Merge handles credential management and API calls to Gamma on the backend. You don't store Gamma tokens locally or manage authentication state yourself. Merge handles both.

Prerequisites

Before getting started, you'll need the following:

• A Merge Agent Handler account
• Claude Code installed (run claude --version to confirm)
• A Gamma account with API access enabled

Related: How to use a Zoom MCP in Claude Code

1. Create a Tool Pack

Log into Merge Agent Handler and navigate to Tool Packs. Click Create Tool Pack and give it a name tied to your use case, like Deck generator agent.

Under connectors, select Gamma and choose which tools to enable.

For content generation workflows, such as creating decks from structured output or reading existing presentations, enabling deck creation and retrieval covers the core cases. Add update tools if your agent needs to modify existing decks after creation.

Save the Tool Pack. You'll return here in step 4 to copy your MCP URL.

2. Add a Registered User

Inside your Tool Pack, create a Registered User. This is the identity context under which your agent operates: the Gamma account it acts on behalf of when creating or retrieving decks.

Give it a name that maps to your environment, like dev-local or your own name. Once created, Merge generates a unique MCP URL scoped to this user.

3. Authenticate Gamma

From the Registered User detail page, click Add Connector and select Gamma. Complete the authentication flow using the Gamma account that owns the workspace where you want decks created. Grant the requested permissions.

Once the auth flow completes, Merge stores and manages the credential. You won't need to re-authenticate unless you revoke access.

Related: A guide to integrating a Google Slides MCP with Claude Code

4. Gather your credentials

You need two things before configuring Claude Code:

1. MCP URL: found on the Tool Pack detail page under the Registered User you just created. It looks like this:

‍https://ah-api.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp

2. API key: found in Settings > API Keys in your Merge Agent Handler dashboard. Create one if you don't have one yet.

Keep both handy for the next step.

5. Configure Claude Code with Gamma

Run the following command in your terminal, substituting your actual MCP URL and API key:

claude mcp add 
--transport http --header "Authorization: Bearer YOUR_API_KEY"
agent-handler
"https://ah-api.merge.dev/api/v1/tool-packs/YOUR_TOOL_PACK_ID/registered-users/YOUR_REGISTERED_USER_ID/mcp"

Verify the connection registered with the command claude mcp list. agent-handler should appear in the output with a connected status.

To confirm the connector is accessible, open a Claude Code session and run a command like "List my recent Gamma decks and summarize the title and slide count of each one created in the last 30 days."

You should see an output that looks something like the following:

{{this-blog-only-cta}}

Gamma MCP FAQ

In case you have more questions on setting up and using the Gamma MCP in Claude Code, we've addressed several more commonly-asked questions below.

What can you do once the Gamma MCP is connected to Claude Code?

With Gamma connected, Claude Code can:

• Create decks: generate a new Gamma presentation from structured content, such as a changelog, sprint summary, or architecture doc, without opening a browser

• List decks: browse existing presentations in your Gamma workspace to find the right deck before querying or updating it

• Read deck content: retrieve the content and structure of an existing presentation so an agent can summarize, extend, or cross-reference it

• Update decks: modify an existing deck with new content when source data changes, such as appending a new slide when a new incident closes

• Cross-reference content: combine Gamma deck data with other connected tools, such as pulling this week's closed GitHub issues and generating a release summary deck from them

Why use Merge Agent Handler vs. a self-hosted Gamma MCP server?

You can build a self-hosted MCP server that calls the Gamma API directly. For a solo developer generating decks from their own workspace, the setup is straightforward: get an API key, write tool schemas for the operations you need, and wire it to Claude Code.

The problems emerge when multiple people need access or when the decks contain sensitive content.

A self-hosted setup gives your agent credentials that carry access to everything in the workspace, not just the specific decks you intend to expose. There are no tool-level controls to limit an agent to read-only access or prevent it from creating decks outside the intended scope.

At team scale, credential management adds overhead. Each developer either shares API credentials (a security risk) or manages their own configuration (a maintenance burden). There is no central log of which agent created or modified which deck, and no clean way to revoke one agent's access without rotating credentials for everyone.

Merge Agent Handler adds a control layer at the tool level.

You define exactly which Gamma tools each Tool Pack exposes, so a read-only summarization agent never gets access to deck creation or deletion tools. And each Registered User has isolated credentials and a separate audit trail.

Why connect Gamma to Claude Code?

Gamma is where a lot of internal communication gets finalized: product updates, technical proposals, launch readouts, engineering retrospectives. The content for all of those already exists in code, tickets, and logs. The gap is moving it from the terminal into a shareable deck, which currently requires a browser and manual formatting.

Connecting Gamma via MCP closes that gap.

A developer can ask Claude Code to pull the last sprint's closed Jira tickets, group them by theme, and create a Gamma retrospective deck with one slide per theme; a release manager can ask Claude Code to read the changelog since the last tag, identify breaking changes, and generate a structured deck for the API consumers call, and the list of examples goes on.