Resources · Claude connector

Claude Gamma connectorWhat Claude can do in your Gamma account.

The Claude Gamma connector exposes 3 tools. 2 read your Gamma workspace (themes and folders), 1 creates new content in it, 0 are undocumented. Here: what Claude builds for you, what it cannot touch, and where Gamma's docs and the directory disagree.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can reach Gamma

You already talk an idea through with Claude. With the connector, the same conversation ends with a real Gamma: Claude sends your outline to Gamma, which lays it out as a presentation, a document, a social post or a web page, and saves it in your workspace. No copy and paste between two tabs, no blank slide to start from.

A first draft deck from a meeting recap. You paste your notes, ask for ten slides for the sales team, and generate creates the Gamma. Gamma lets Claude set the tone, the audience, the language, the amount of text per card and the export format, with PDF and PPTX on the list.

On-brand from the first card. Before creating anything, get_themes lets Claude search Gamma's theme library, so a client proposal does not come out in the default look.

Filed where your team expects it. get_folders finds the right folder in your workspace, and Gamma says generated content can be saved to a specific location, so the draft lands in Marketing rather than at the root.

Now the part the directory sheet leaves out. Claude cannot edit a Gamma that already exists: Gamma says editing only happens in its own app. It cannot open or export an old deck either, because those tools are not on the sheet. Every generation uses Gamma credits. And nothing runs on its own: no tool fires when a form comes in or a file lands. For that kind of background job you want an automation tool, which is a different job; the Gamma Make integration covers that side, and the Integrations hub lists the rest.

Vocabulary

The vocabulary in one minute

Five words you will run into while plugging Gamma in.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks the ones it needs on its own, and the directory lists them by name.
Authorization
The sign-in screen of Gamma itself, where you hand Claude the access it will use. Granted once per person, and you can take it back.
Approval
The confirmation Claude waits for before it goes ahead with something that changes your account, shown right in the chat.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Gamma.
Connect

Plug Gamma into Claude in three steps

  1. 01

    Find Gamma in Claude

    In Claude's settings, open Customize, then Connectors, and look for Gamma in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can connect.

  2. 02

    Start the connection

    Click Connect on Gamma's row, then sign in to Gamma in the window Gamma opens itself. If the link ever breaks or expires, use Disconnect and plug it back in.

  3. 03

    Read the authorization screen

    Gamma's consent screen lists what the app asks for: create gammas, read gammas, list folders and list themes in your workspace. That screen belongs to Gamma, not Claude, and it decides what the access covers.

Tools

The 3 tools of the Claude Gamma connector

Gamma gives Claude 3 tools: 2 that read your account, 1 that change something in it.

Two groups: what Claude reads in your workspace, and what it creates there. The names stay the ones Claude shows, in English.

  • 2 read
  • 1 write

What Claude reads (2)

2 tools

Two lookups that help Claude prepare a generation without changing anything.

get_themes

Searches or browses Gamma's theme library so Claude can pick a look before it builds anything. You get a theme that matches the style you described instead of the default one.

When it helps
a freelancer wants a pitch deck in a calm, minimal style and names the mood rather than a theme ID.
Watch out
it only picks a style; the content itself comes from the generation step.

Sourcedevelopers.gamma.app · September 30, 2026 ↗

get_folders

Lists or searches the folders of your Gamma workspace, so Claude knows where a new Gamma should go. It reads the folder tree and leaves it as it is.

When it helps
the events team keeps every webinar deck in one folder and wants the next one filed there too.
Watch out
it lists folders; saving the new Gamma into one is part of the generation.

Sourcedevelopers.gamma.app · September 30, 2026 ↗

What Claude creates (1)

1 tool

One tool that adds new content to your Gamma workspace. No source describes a confirmation of its own, so the general rule below applies.

generate

Approval: see the rule

Builds a brand new presentation, document, web page or social post from your prompt, notes or draft, and adds it to your workspace. Tone, audience, language, images and export format can all be set in the request.

What Claude asks for
no source describes a confirmation specific to this tool, so the general approval rule below covers it.
When it helps
a trainer turns a course outline into a handout document the night before a session.
Watch out
each generation uses Gamma credits.

Sourcedevelopers.gamma.app · September 30, 2026 ↗

Approvals

What Claude asks before it acts

By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.

On a Team or Enterprise workspace, the owners decide whether a member can let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keep reading open and close writing. That setting applies to everyone, and nobody gets around it from their own account. Claude also works with your Gamma rights and nothing more: a workspace you cannot reach stays out of its reach too.

Plans

Which plans include it

Out of the 819 sheets in the official directory, not one shows availability by plan. The connector by connector answer is published nowhere: that is a real gap in the catalogue.

The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member can connect. For the current status, check the Gamma sheet in the official directory, from your own account.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a form comes in, a file changes or a deadline passes.

This connector is documented only by its publisher: no Claude help page covers it. The tool list is an observed floor, not a promise, since an admin can open actions that no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Plug in what comes from a publisher you trust, here Gamma itself.

Two official sources disagree

How many Gamma tools can Claude actually use?

What this page followsNeither side is stale: Gamma documents its whole server, the sheet shows what the Claude connector exposes. For your account, the sheet is the one that counts. Gamma adds that some platforms review its updates before release, so check the directory sheet from your own account.

Need help

Need help connecting Gamma to Claude?

A person reads every message.

FAQ

Questions about the Claude Gamma connector

01What can Claude do with the Gamma connector?
Claude can create a new Gamma for you from a conversation. The three tools on the directory sheet let it search Gamma's theme library, browse the folders of your workspace, and generate a presentation, document, web page or social post from a prompt, notes or a full draft. Gamma lets the request set tone, audience, language, images and export format. Reading an existing Gamma or exporting an old one are not among the tools the sheet lists today.
02Can Claude edit or delete my existing Gammas?
No, editing is off the table for now. Gamma answers that question in its own documentation: editing a Gamma through its connector is not possible today, and it only happens inside the Gamma app. The only tool on the sheet that changes your workspace is generate, and it adds new content rather than touching what already exists. No source describes a deletion tool either. The sheet is still a floor, so check it again from your account before you rely on it.
03Does Claude ask before creating a Gamma?
By default, yes: Claude asks for confirmation before each action it takes on an account for you. No source describes a confirmation specific to generate, so this default rule is what covers it. On a Team or Enterprise workspace, owners decide whether members can let some actions through without a prompt, and they can also close content creation for the whole organization while keeping the theme and folder lookups open.
04Which Claude plans include the Gamma connector?
No official source publishes availability plan by plan for a given connector, and none of the directory sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner switching the connector on first on Team and Enterprise. On Gamma's side, its docs say the connector works on all Gamma plans and that generations charge credits. The directory sheet is the place to check your own account.
05Does Claude see my whole Gamma workspace?
No, Claude works with your rights and nothing more. When you connect, Gamma's consent screen lists what the app requests in your workspace: creating gammas, reading gammas, listing folders and listing themes. Anything you cannot open yourself in Gamma stays out of Claude's reach as well. On Team and Enterprise, an owner can also restrict what the connector may do for the whole organization, and a member cannot lift that from their own account.
06Why does a Gamma feature I read about not show up in Claude?
Because Gamma documents more tools than the Claude directory sheet shows. Gamma's reference lists templates, multi-page Gammas, image generation, export and reading, while the sheet lists three tools. Gamma also says some platforms review app updates before users get them, so a feature can exist on its side before it reaches your assistant. Check the directory sheet from your account, and if something that used to work stops, disconnect and reconnect as Gamma advises.
07Claude or an automation tool for Gamma: which one fits?
They do different jobs, so pick by use rather than by ranking. The connector fits when you want a deck or document out of a conversation you are already having, with a human reading the result. An automation tool such as Make fits when a Gamma should be produced every time something happens elsewhere, like a new form entry, with no chat involved. Nothing in the connector starts on its own, so recurring or event-driven jobs belong to automation.