Connect Gamma to Claude Code
Generate presentations, documents and web pages with AI, then find, export and manage the gammas in a workspace. Add Toolspoke to Claude Code once and it can use 16 Gamma actions. Your Gamma credential stays in Toolspoke, and you choose which actions Claude Code may call.
Set it up in Claude Code
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to Claude Code
Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcpThe sign-in opens in your browser, and Toolspoke asks you to approve it.
Install Gamma and connect it
Add Gamma to a project in your Toolspoke workspace.
API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.
- API key
- Gamma → Settings → API Keys (gamma.app/settings/api-keys) → create a key. API keys need a Pro, Ultra, Teams or Business plan. A key belongs to one workspace and spends its owner's credits there, so teammates sharing a key share one balance. Deleting a gamma also needs the owner to be a workspace admin.
Choose what Claude Code may do
All 16 actions start on. Switch off any of the 6 actions that change something in Gamma, and Claude Code gets a refusal if it tries.
What you can ask Claude Code for
A few of the Gamma actions that only read, so they are safe to try first.
- Check a generation started by create_generation or create_generation_from_template
- Check a generation started by create_agent_generation
- List the themes a generation can use
- List the workspace's folders with their ids, to pass as folderId when generating
What Claude Code can do in Gamma
10 actions read, 4 write and 2 delete or permanently change something.
Reads
Get generation
Check a generation started by create_generation or create_generation_from_template. status is pending, completed or failed; once completed it carries gammaId, gammaUrl, exportUrl when an export was requested, and the credits spent. Poll every few seconds.
Get agent generation
Check a generation started by create_agent_generation. Same polling pattern as get_generation, for gen_-prefixed ids.
List themes
List the themes a generation can use. Gamma's standard themes and the workspace's own custom ones, with their ids. Needs no arguments, spends no credits and always returns something for a working key, which is why an install tests itself with it.
List folders
List the workspace's folders with their ids, to pass as folderId when generating.
Search gammas
Full-text search over the titles and body text of the gammas this key can see, with filters for creator and last-updated time. Hits can carry a text snippet from the document. Send q or at least one filter.
Get gamma
Read one gamma's metadata, title, description, type, URL, author, theme, timestamps and whether it is archived. Not its full content.
Search templates
Search the workspace's templates and Gamma's official explore templates, returned as two lists. A hit's id can be used as gammaId in create_generation_from_template or templateId in create_agent_generation.
List gamma comments
List the comment threads and replies on one gamma. Comments are other people's words, so the output is not retained.
Get gamma analytics
Engagement summary for one gamma, total views, unique viewers and editors, card count, last opened and daily views. Gamma notes the data can lag by about an hour.
Get export
Check an export started by export_gamma. Once status is completed it carries exportUrl, a download link to the document itself, so the output is not retained.
Writes
Create generation
Start an AI generation of one presentation, document, social post or web page from a topic, an outline or a full draft. Returns a generationId at once; poll get_generation until status is completed, then use the gammaUrl it returns. Classified write rather than destructive, and deliberately so: it spends workspace credits, but what it makes is a new gamma inside the workspace, shared by the workspace's default settings, and delete_gamma removes it. This operation does not take Gamma's sharingOptions, emailOptions or publish fields, so it cannot email anyone a link or publish a public site, share from the Gamma app instead.
Create generation from template
Start a generation that adapts an existing one-page gamma used as a template: Gamma keeps its structure and rewrites the content from the prompt. Returns a generationId; poll get_generation. Write, not destructive, for the same reasons as create_generation: it spends credits and makes a new private-by-default gamma, it never changes the template, and it takes no sharing or publish options.
Create agent generation
Start a generation run by the Gamma agent, which can read source URLs and, unless disableConnectors is set, the workspace's connected apps (such as Notion or Slack) while it writes. Returns a gen_-prefixed generationId; poll get_agent_generation. Write rather than destructive: it spends credits and makes a new gamma in the workspace, and it takes no sharing options.
Export gamma
Start an export of an existing gamma to PDF, PPTX or PNG (a .zip with one PNG per card). Returns an exportId; poll get_export for the download link. Write: it creates a file and changes nothing in the gamma.
Deletes or permanently changes
Archive gamma
Archive one gamma, taking it out of the active workspace for everyone who uses it without deleting it. Destructive because this API has no way to undo it: there is no unarchive endpoint, and restoring it means someone doing so in the Gamma app. Idempotent, archiving an archived gamma succeeds.
Delete gamma
Delete one gamma. Gamma archives it first if needed, then marks it for deletion; it is immediately inaccessible and no longer addressable through the API. Needs a workspace admin's key.
Gamma in Claude Code: questions
Does Claude Code see my Gamma credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Can I stop Claude Code from changing things in Gamma?
Yes. Each of the 16 actions can be switched off for a project. Turn off the 6 that change something and Claude Code can only read.
Will 16 actions crowd Claude Code's context?
No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Gamma action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Can I add it once for every project?
Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.
What does it cost?
Tool calls are free on every plan, and a Gamma call does not run in a sandbox, so it bills nothing.
Gamma in your other apps
Try Gamma in Claude Code
Free to start, and tool calls cost nothing on any plan.