Connect your AI Agents to Gamma in minutes

What is a Gamma MCP?

It's an MCP server that connects your agents to Gamma's AI content generation platform via tools. Your agents can invoke these tools to generate presentations, documents, and webpages from text, create content from templates, track generation status, and more.

Gamma offers an official MCP server, but you can also use one from a third-party platform, like Merge Agent Handler.

How can I use the Gamma MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Automated deck generation from deal briefs: When a sales rep fills out a deal brief in a CRM, an agent takes the key details and calls Gamma to generate a tailored pitch deck, then shares the link back in Slack so the rep has it ready before the call

• Template-based report publishing: On a weekly schedule, an agent pulls performance data from an analytics tool, selects the appropriate Gamma template, and generates a branded summary doc that gets shared automatically with the leadership team

• Meeting prep decks from agenda notes: When a meeting is created in a calendar tool with linked notes, an agent reads the agenda, generates a Gamma presentation covering the key topics, and attaches the link to the calendar invite before the meeting begins

• Content repurposing on publication: When a blog post or product update is finalized in a content tool, an agent generates a corresponding Gamma one-pager or social post from the same source material, cutting out manual reformatting work

What are popular tools for Gamma's MCP server?

Here are some of the most commonly used tools:

• generate_gamma: creates a new Gamma presentation, document, webpage, or social post from a text prompt, with control over tone, audience, layout, and theme. Use this when an agent needs to produce polished content from scratch based on data or text pulled from another system

• generate_gamma_from_template: generates new Gamma content using an existing template as the structural and design foundation. Good for workflows that need consistent branded output across recurring reports, proposals, or client-facing decks

• get_generation_status: checks the status of an in-progress Gamma generation job, returning pending, completed, or failed. Call this when an agent needs to confirm a generation has finished before linking or sharing the output downstream

• list_folders: retrieves workspace folders and their IDs from a Gamma account. Helpful when an agent needs to route generated content into the right folder or locate existing presentations before triggering new ones

• list_themes: returns the themes available in a Gamma workspace for customizing visual output. Use this when an agent needs to match generated content to a specific brand theme before kicking off a generation job

What makes Merge Agent Handler's Gamma MCP server better than alternative Gamma MCP servers?

Gamma has its own official MCP server, but routing it through Merge Agent Handler adds production-grade controls that matter when content generation is part of a larger automated workflow:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Gamma, this means you can prevent prompt content, generated document text, and workspace folder structures from being surfaced to agents that don't need full visibility

• Managed authentication and credentials: Merge stores and manages your Gamma OAuth credentials on your behalf. You never embed tokens in agent configuration or handle re-authorization when they expire

• Real-time observability and audit trail: Every tool call against Gamma is logged with timestamp, tool name, input parameters, and response data. Teams can audit exactly what content an agent generated or what workspace it accessed without any custom instrumentation

• Tool Packs and controlled access: Tool Packs let you bundle specific Gamma tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Gamma MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack, then find and enable the Gamma connector. Choose tools that fit your workflow: list_folders and list_themes handle discovery and setup, while generate_gamma, generate_gamma_from_template, and get_generation_status are needed for agents that create and track content.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, authenticate Gamma by completing the OAuth flow. Merge stores and manages the credentials going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your Gamma tools are now accessible through that endpoint.