Gamma MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GAMMA_API_KEY | Yes | Your Gamma API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_gammaA | Generate a Gamma presentation, document, or social media post using AI. Requires GAMMA_API_KEY environment variable to be set. The inputText parameter is required and should contain the content you want in your slides. Supports various customization options including format, theme, number of cards, text options, image options, and more. |
| get_gamma_generationA | Retrieve the status and URLs of a Gamma generation. By default, automatically polls every 5 seconds until generation is complete (recommended). Returns the final URLs to the generated Gamma, plus PDF/PPTX export URLs if requested. Supports both automatic polling (default) and single status checks. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one initiates a generation and the other retrieves its status/results. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun pattern: generate_gamma and get_gamma_generation. The naming is predictable and grammatically consistent.
With only 2 tools, the server feels minimal and borderline for its stated purpose. While the tools cover the core generate-and-retrieve workflow, the server would benefit from additional tools such as listing templates or canceling generations.
The two tools provide a complete lifecycle for a single generation request: create and retrieve. Minor gaps exist such as no update or delete functionality, but these are not critical for the primary use case of generating content.