Operator-narrative review · Updated 2026-05-22

Gamma MCP Review (2026): the only first-party MCP shipping in the AI-presentation category

Gamma ships an official MCP server, documented at https://developers.gamma.app/mcp/gamma-mcp-server, that exposes Gamma's generation surface to Claude and other MCP-aware clients. Stdio install, GAMMA_API_KEY auth (available on every plan), tools for creating presentations / docs / social posts, browsing themes, and checking generation status. For operators already using Gamma for sales decks, fundraising decks, or internal docs, this is the structural shift that lets the LLM generate them in-conversation. As of mid 2026, Gamma is the only AI-presentation tool with a first-party shipping MCP.

Quick context. We run StackSwap MCP so we evaluate MCP servers as the operators that ship them, not as a checklist. We are a Gamma affiliate; the review below is the same operator analysis we'd give a friend evaluating Gamma cold against Tome and Beautiful.ai.

Want to try Gamma?

Gamma MCP — the only AI-presentation MCP shipping with first-party support in 2026

API key is available on every plan including Free. Generate presentations, docs, and social posts in Claude. Multi-MCP composition with Apollo / HubSpot / StackSwap means the deck-with-data workflow happens in one conversation.

Start with Gamma →Affiliate link — StackSwap earns a commission if you sign up for Gamma. We only partner with tools we'd recommend anyway.

What Gamma MCP is, in operator terms

Gamma is the AI-native presentation/document platform that competes with Tome, Pitch.com, and Beautiful.ai (and indirectly with Canva for the deck use case). It ships an official MCP server documented at https://developers.gamma.app/mcp/gamma-mcp-server. You add the MCP entry to your Claude Desktop config with GAMMA_API_KEY in env, restart Claude, and the Gamma tools appear: create generation, browse themes, check status, retrieve outputs.

Two distinctions matter. First, this is first-party and officially supported — published by Gamma, on Gamma's developer-docs domain. Schema changes and tool definitions ship together. Second, the MCP isn't a gated entitlement: the API key is on every Gamma plan including Free. The only resource the MCP consumes is generation credits, which is the same pool the UI uses.

The capability surface — what you actually get

Gamma MCP vs the field — Tome, Pitch, Beautiful.ai

The honest landscape as of mid 2026:

ToolFirst-party MCPAPI surfaceAuthOperator fit
GammaYes, official, shippingFull REST + MCP, schema docs at developers.gamma.appGAMMA_API_KEYThe default for AI-first deck workflows in 2026
TomeNo (community wrappers only)REST API, no MCP serverAPI tokenIf your team is on Tome already, manual workflow stays manual
Pitch.comNoREST API, no MCPAPI tokenStrong manual UX, but no LLM-driven generation today
Beautiful.aiNo public MCPLimited public APIPer integrationSlide-template strength, weak on AI-driven workflow

The category will close — Tome and Pitch.com both have the API surface to ship MCP, and the protocol is the obvious next step. But right now (mid 2026), Gamma is alone with a first-party shipping MCP. For operators making the AI-first deck decision in 2026, that asymmetry is meaningful.

The credit-pool gotcha — generation cost is real

Same operator warning that applies to every credit-priced MCP: the LLM is eager. "Generate a deck for each of these 10 prospects" via Gamma MCP is 10 generations against your monthly credit cap. On Free, that's your monthly cap. On Plus and Pro, it's a meaningful dent.

Three mitigations:

Where StackSwap MCP fits alongside

Gamma MCP generates presentations and documents. StackSwap MCP exposes the cross-vendor GTM catalog — ~400 tools, overlap pairs, cost models. Different shapes, both useful in the same Claude session. "Generate a sales-deck draft for this prospect" (Gamma MCP) after "recommend the right stack for their team" (StackSwap MCP) is a natural combination. Or: scheduled Claude task that pulls weekly pipeline data via HubSpot MCP, runs StackSwap analysis on the deal stack, and generates a Gamma deck with the synthesis — board-ready in 30 seconds.

Connect StackSwap MCP free → (one URL + OAuth, same protocol).

Want to try Gamma?

Gamma MCP is the AI-first presentation default in 2026 — and the only one shipping

API key on every plan including Free. Generate decks, docs, and social posts in Claude. The structural shift that makes Gamma the LLM-native default in the presentation category.

Start with Gamma →Affiliate link — StackSwap earns a commission if you sign up for Gamma. We only partner with tools we'd recommend anyway.

FAQ

Gamma MCP is the official MCP server published by Gamma (the AI-native presentation/document platform) that lets LLM clients generate presentations, docs, and social media posts from a prompt. The tool surface (per Gamma's developer docs at https://developers.gamma.app/mcp/gamma-mcp-server): create a new generation from a prompt, browse available themes, check generation status, and retrieve generated outputs. The deliverable is a real, polished Gamma deck or document — not just an outline. For operators that already use Gamma for fundraising decks, sales decks, or internal docs, the MCP lets the LLM generate them in-conversation.

Stdio via an MCP-compatible client, authenticated with a GAMMA_API_KEY. The API key is available on every Gamma plan (Free, Plus, Pro). You add an MCP server entry to your Claude Desktop config that runs the Gamma MCP launcher with GAMMA_API_KEY in env, restart Claude, and the Gamma tools appear. Same auth posture as the REST API — the key is scoped to your Gamma workspace and the LLM inherits the workspace's plan and credit pool.

Mixed. The MCP layer itself is included on every plan including Free — the API key is on every tier. But generation credits are not free. Each presentation/doc/social post generation consumes credits at the same rate as the UI. The Free plan ships limited generations per month; Plus and Pro raise the cap. The MCP doesn't change the cost model, it just routes the existing credit-based generation through the LLM. Start on Free for evaluation; upgrade when the credit cap bites.

Three differences. (1) In-conversation iteration. The LLM can generate a deck, you respond with 'shorter, more numbers in slide 4, swap the theme', and the LLM re-generates without you opening the Gamma UI. (2) Multi-step orchestration. Pull data from another MCP (Apollo, HubSpot, StackSwap), feed it into a Gamma generation, return the deck — all in one conversation. (3) Agent-driven decks. A scheduled Claude task can generate weekly sales decks, monthly board decks, or daily team updates from structured input data, with the operator only reviewing the output.

Gamma MCP is the only first-party, shipping, officially-supported MCP in the AI-presentation category as of mid-2026. Tome publishes API access but no native MCP server (community wrappers exist, maintenance-by-someone-else). Beautiful.ai has no public MCP. The honest read: if you want LLM-native presentation generation today and you want it to actually work reliably, Gamma is the only option. The category will likely close — Tome and Pitch.com both have the API surface to ship MCP — but right now Gamma is alone.

Three primary formats: presentations (slide decks for sales, fundraising, board updates, internal training), documents (one-pagers, briefs, reports formatted with Gamma's polish layer), and social media posts (graphic-heavy LinkedIn or X content). Each takes a prompt — text input describing what to make, optional theme selection from Gamma's library, optional source content (the LLM can pass research it gathered from other MCPs as input). The output is a real Gamma object you can edit further in the UI if needed.

Yes, with one caveat. The auth model is API-key-based and standard — the LLM inherits your workspace's permissions and credit pool. The audit trail is in your Gamma activity log. The caveat: the LLM generates the deck, but a human should review before sending — Gamma's output is good but not pitch-perfect on first generation, and a fundraising deck or top-of-funnel sales deck has too much weight on it to ship without operator review. Treat the MCP output as a first-draft that saves 80% of the time, not a final deliverable.

Probably yes, for the LLM-driven workflows specifically. The cost is one API key and a config entry. You can keep your existing Tome/Pitch workspace for the UI-driven deck-building (where their feature sets are competitive) and use Gamma MCP for the in-Claude generation flows that Tome and Pitch cannot yet support. Many operators converge on a multi-tool shape: Gamma for AI-first decks generated in Claude, the other tool for the manually-crafted ones. The MCP is the differentiator that makes Gamma the AI-first default in 2026.

Related reading

Canonical URL: https://stackswap.ai/gamma-mcp-review. Disclosure: StackSwap is a Gamma affiliate. The structural read above is the same operator analysis we'd give a friend evaluating Gamma against Tome and Beautiful.ai cold.