Gamma
by Gamma
Generate presentations, documents, sites and images in Gamma from an AI agent. Anthropic lists 3 tools; Gamma documents 17, including viewer-level analytics. Every generation spends credits, and no tool reads the balance before the spend.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Gamma via MCP
https://mcp.gamma.app/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Gamma Tools & Capabilities (17)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- No editing, at all. Gamma states editing is only available in the Gamma app. Revising a generated deck means generating a new one — and paying for it again.
- No delete or archive tool. Gamma's REST API exposes
POST /gammas/{id}/archiveandDELETE /gammas/{id}, the latter restricted to workspace admins. Neither has an MCP counterpart, so the connector accumulates gammas it cannot clean up. - Every generation spends credits at a rate that varies by more than 50×, and no tool reads the balance before spending. The floor is a
402, unless auto-recharge is on, in which case there is no floor. - No idempotency key on any generation tool. A retried timeout can bill twice.
- Anthropic's directory lists 3 of 17 tools, omitting all four analytics tools, both content read tools and the comment reader. A reader sizing this connector from the listing will under-count the personal data it can reach.
- Gamma's own setup-page FAQ also under-lists, omitting the multi-page, analytics and comment tools that the Capabilities section on the same page describes.
- The consent screen's four permissions predate the current surface. Gamma documents consent covering create, read, list folders and list themes — nothing naming analytics or viewer email addresses, which
gamma:readpresumably carries. - Export URLs are unauthenticated bearer links valid for about a week. Anyone with the link downloads the file.
- Analytics lag by about an hour and are eventually consistent, per Gamma's tools reference.
- We could not read tool schemas or annotations from the server. The endpoint returned 401 to an anonymous request on 2026-08-23. The per-tool safety hints on this page are Gamma's published table, not our observation of a
tools/listresponse. - The documentation URL Anthropic publishes for this connector could not be read. It points at a Gamma-hosted deck,
gamma.app/docs/Gamma-MCP-Server-Documentation-m6p43kobgzy15zj?mode=doc, which is itself a client-rendered Gamma. Every route returned HTTP 403 with a 679KB Cloudflare challenge whose extractable text is nine words. We applied the RSC-flight,__NEXT_DATA__,__NUXT__, embedded-JSON, Next.js data-route, oEmbed and archive extractors and all seven returned zero — the origin was never reached, so this is bot mitigation rather than an absent document. This page is built from Gamma's GitBook developer documentation instead, which is richer, machine-readable and explicitly opted in to AI synthesis.
Frequently asked questions
Yes, both, and neither is a separate tool. Gamma documents a sharingOptions object on the generation tools whose externalAccess field grants people outside your workspace view, comment or edit rights, and whose emailOptions.recipients field shares the new gamma to a list of email addresses. The reach is a parameter of generate, not a publish step someone has to take afterwards.
One tool can. Gamma documents a publish boolean on generate_multi_page_gamma that, when true, publishes the result as a live multi-page site on a Gamma-generated subdomain once every page succeeds. It defaults to off, so an agent has to be asked. That makes it the opposite of a silent default, but it is still one boolean from a public URL.
Seventeen, per Gamma's own MCP tools reference. Anthropic's directory lists three — generate, get_themes and get_folders — which matches the connector as it launched in January 2026 and has not tracked the fourteen tools added since. The fourteen unlisted ones include reading gammas, reading comments, and four analytics tools that name individual viewers.
They cost credits, and nothing can check the balance beforehand. Gamma charges 1-3 credits per card and 2-125 credits per AI image depending on the model, and returns credits.deducted and credits.remaining only on the status response after a job finishes. No tool among the seventeen reads a balance, so the first observation of the cost arrives once it is already spent.
Two, and they are real application scopes. The server's RFC 9728 descriptor and its authorization server both advertised generate and gamma:read on 2026-08-23. The boundary falls between reading a gamma and creating one, which is the useful place. It does not separate a private generation from one that emails external recipients, because both are generate.
It can do neither. Gamma states plainly that editing is only available in the Gamma app, and no tool among the seventeen carries an edit, update, archive or delete verb. Gamma's REST API does expose archive and delete endpoints, with deletion restricted to workspace admins, but neither has an MCP counterpart. Revision means generating a new gamma.
Named viewers and their email addresses. Gamma's get_gamma_viewer_analytics tool returns a paginated list of everyone who opened a gamma with display name, email, last-opened time and cards viewed, and get_gamma_viewer_detail_analytics returns one person's per-card dwell time. Gamma requires manage permission to see all viewers; edit permission returns only your own row.
Because nothing deduplicates it. Gamma documents no idempotency key on any generation tool, and warns that calling generate_image again to check progress starts a new, separately billed generation. A call that times out may have succeeded, so a retry can produce a second gamma and a second charge. Poll the status tool with the returned ID instead.
Sources
- Gamma MCP tools reference (retrieved 2026-08-23). The 17-tool list, the per-tool annotation table,
sharingOptions, thepublishboolean and the error table all come from here. · retrieved 2026-08-23 - Gamma MCP server setup (retrieved 2026-08-23) · retrieved 2026-08-23
- Gamma access and pricing, credit rates (retrieved 2026-08-23) · retrieved 2026-08-23
- Gamma asynchronous patterns and polling (retrieved 2026-08-23) · retrieved 2026-08-23
- Gamma generate parameters guide, sharing defaults (retrieved 2026-08-23) · retrieved 2026-08-23
- Gamma API scope and limits, archive and delete endpoints (retrieved 2026-08-23) · retrieved 2026-08-23
- Gamma connectors and integrations (retrieved 2026-08-23) · retrieved 2026-08-23
- Gamma API changelog (retrieved 2026-08-23) · retrieved 2026-08-23
- Gamma documentation index — and (retrieved 2026-08-23).
developers.gamma.app/robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes— synthesis expressly permitted. · retrieved 2026-08-23 - Live OAuth posture check: 401 with
www-authenticateathttps://mcp.gamma.app/mcp, RFC 9728 metadata athttps://mcp.gamma.app/.well-known/oauth-protected-resource, and authorization server metadata athttps://auth.gamma.app/.well-known/oauth-authorization-server(2026-08-23) · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Gamma support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Gamma
- Tools
- 17
- Domain
- mcp.gamma.app
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.