Which integrations are available for this server?

Allows including GIFs from GIPHY as images in generated presentations, documents, social posts, or webpages. Allows including stock photos from Pexels as images in generated content.

How do I use gamma-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@gamma-mcp create a presentation about AI in healthcare" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

gamma-mcp

by Purple-Horizons

Overview Schema Source Related Servers Score Discussions Admin

JavaScript

Remote

Gamma MCP Server

MCP server for Gamma.app - AI-powered presentation, document, and website generation.

Features

Generate from scratch - Create presentations, documents, social posts, or webpages from text
Create from template - Adapt existing Gamma templates with new content
List themes - Browse available themes for styling
List folders - Browse workspace folders for organization
Poll generation status - Check when async generation completes

Related MCP server: Gamma MCP Server

Installation

npm install @purple-horizons/gamma-mcp

Or clone and build:

git clone https://github.com/Purple-Horizons/gamma-mcp.git
cd gamma-mcp
npm install
npm run build

Configuration

Environment Variable

Set your Gamma API key:

export GAMMA_API_KEY=sk-gamma-xxxxxxxx

Get your API key from Gamma Account Settings (requires Pro, Ultra, Teams, or Business plan).

Claude Desktop / OpenClaw

Add to your MCP config:

{
  "mcpServers": {
    "gamma": {
      "command": "node",
      "args": ["/path/to/gamma-mcp/dist/index.js"],
      "env": {
        "GAMMA_API_KEY": "sk-gamma-xxxxxxxx"
      }
    }
  }
}

mcporter

Add to ~/.config/mcporter/mcporter.json:

{
  "servers": {
    "gamma": {
      "command": "node",
      "args": ["/path/to/gamma-mcp/dist/index.js"],
      "env": {
        "GAMMA_API_KEY": "sk-gamma-xxxxxxxx"
      }
    }
  }
}

Tools

gamma_generate

Generate a new gamma from text input.

Parameters:

inputText (required) - Content to generate from (text + image URLs)
textMode (required) - generate | condense | preserve
format - presentation | document | social | webpage
themeId - Theme ID (from gamma_list_themes)
numCards - Number of slides (1-60 for Pro, 1-75 for Ultra)
cardSplit - auto | inputTextBreaks
additionalInstructions - Extra generation guidance
folderIds - Array of folder IDs to save to
exportAs - pdf | pptx
textAmount - brief | medium | detailed | extensive
textTone - Tone description (e.g., "professional, inspiring")
textAudience - Target audience
textLanguage - Language code (default: "en")
imageSource - aiGenerated | pictographic | pexels | giphy | webAllImages | webFreeToUse | webFreeToUseCommercially | placeholder | noImages
imageModel - AI model for images (e.g., "flux-1-pro", "imagen-4-pro")
imageStyle - Image style description
dimensions - Card dimensions (format-dependent)

Returns: { generationId: "..." }

gamma_get_generation

Check generation status.

Parameters:

generationId (required) - ID from gamma_generate

Returns:

{
  "status": "pending" | "completed",
  "generationId": "...",
  "gammaUrl": "https://gamma.app/docs/...",
  "credits": { "deducted": 150, "remaining": 3000 }
}

gamma_create_from_template

Create a gamma based on an existing template.

Parameters:

gammaId (required) - Template gamma ID
prompt (required) - Instructions and content
themeId - Override theme
folderIds - Destination folders
exportAs - pdf | pptx
imageModel - AI model for new images
imageStyle - Style for new images

Returns: { generationId: "..." }

gamma_list_themes

List available themes.

Parameters:

query - Search by name
limit - Max results (default 50)
after - Pagination cursor

Returns:

{
  "data": [{ "id": "...", "name": "...", "type": "standard|custom" }],
  "hasMore": false,
  "nextCursor": null
}

gamma_list_folders

List workspace folders.

Parameters:

query - Search by name
limit - Max results (default 50)
after - Pagination cursor

Returns:

{
  "data": [{ "id": "...", "name": "..." }],
  "hasMore": false,
  "nextCursor": null
}

Usage Example

// 1. Generate a presentation
const gen = await gamma_generate({
  inputText: "5 ways AI is transforming healthcare",
  textMode: "generate",
  format: "presentation",
  numCards: 10,
  imageSource: "aiGenerated",
  imageStyle: "modern, professional photography"
});

// 2. Poll for completion
let status;
do {
  await sleep(5000);
  status = await gamma_get_generation({ generationId: gen.generationId });
} while (status.status === "pending");

// 3. Use the result
console.log(status.gammaUrl); // https://gamma.app/docs/xxxxx

Credits

Gamma uses a credit-based system:

~3-4 credits per card
~2-120 credits per image (depends on model)

Check your remaining credits in the generation response.

License

MIT

Available Tools

5 tools

gamma_create_from_templateB

Create a new gamma based on an existing template. Adapts content to match template structure.

ParametersJSON Schema

Name	Required	Description
`prompt`	Yes	Instructions and content for adapting the template. Can include text and image URLs.
`gammaId`	Yes	ID of the template gamma to base the new one on.
`themeId`	No	Theme ID to override template's theme.
`exportAs`	No	Export format.
`folderIds`	No	Folder IDs to save the gamma to.
`imageModel`	No	AI image model for new images.
`imageStyle`	No	Style for new AI-generated images.

TDQS

B3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. The description only says 'adapts content' without detailing behavioral aspects like permission requirements, rate limits, or what happens to the template.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no redundancy. Could benefit from more structure (e.g., listing key parameters), but still concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description fails to explain return values, error conditions, or detailed behavior. Highly incomplete for a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all 7 parameters. The description adds minimal context ('adapts content') but does not significantly enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'create' and the resource 'gamma based on an existing template', distinguishing it from siblings like gamma_generate (generate from scratch) and listing tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings (e.g., gamma_generate). No mention of prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

gamma_generateA

Generate a new presentation, document, social post, or webpage from text input. Returns a generationId to poll for completion.

ParametersJSON Schema

Name	Required	Description	Default
`format`	No	Output format type.	presentation
`themeId`	No	Theme ID to use. Get from gamma_list_themes.
`exportAs`	No	Export format. Links expire, download promptly.
`numCards`	No	Number of cards/slides to generate (1-60 for Pro, 1-75 for Ultra).
`textMode`	Yes	How to handle input text. 'generate' expands, 'condense' summarizes, 'preserve' keeps as-is.
`textTone`	No	Tone/voice of content (e.g., 'professional, inspiring').
`cardSplit`	No	How to split content into cards. 'auto' uses numCards, 'inputTextBreaks' uses \n---\n markers.	auto
`folderIds`	No	Folder IDs to save the gamma to.
`inputText`	Yes	Content to generate from. Can include text and image URLs. Max ~100k tokens.
`dimensions`	No	Card dimensions. Presentation: fluid/16x9/4x3. Document: fluid/pageless/letter/a4. Social: 1x1/4x5/9x16.
`imageModel`	No	AI image model (if imageSource is 'aiGenerated'). E.g., 'flux-1-pro', 'imagen-4-pro'.
`imageStyle`	No	Image style description (e.g., 'photorealistic', 'minimal line art').
`textAmount`	No	How much text per card.
`imageSource`	No	Where to source images from.	aiGenerated
`textAudience`	No	Target audience description.
`textLanguage`	No	Output language code (e.g., 'en', 'es', 'fr').	en
`additionalInstructions`	No	Extra instructions for generation (max 2000 chars).

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It correctly mentions asynchronous generation and polling, and export link expiration from the schema. However, it omits auth requirements, rate limits, and error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no wasted words. The first sentence defines the action, the second specifies the return value and polling need. Efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 17 parameters and no output schema or annotations, the description is too brief. It fails to explain the generation workflow, asynchronous nature, or provide examples. The parameter descriptions in the schema are thorough, but the tool description itself is incomplete for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with individual parameter descriptions. The tool description adds minimal parameter context beyond stating the return value. It does not elaborate on parameter interactions or behaviors.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it generates presentations, documents, social posts, or webpages from text input, and returns a generationId. This distinguishes it from siblings like gamma_create_from_template (template-based) and gamma_get_generation (polling).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a polling workflow by mentioning returns a generationId, but does not explicitly state when to use this tool versus alternatives. Sibling tools exist for templates and polling, but no direct guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

gamma_get_generationA

Check the status of a gamma generation. Poll until status is 'completed'.

ParametersJSON Schema

Name	Required	Description	Default
`generationId`	Yes	The generation ID returned from gamma_generate.

TDQS

A4.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description must convey behavior. It discloses polling as the primary action but lacks details on rate limits, error handling, or auth requirements. For a simple status check, this is adequate but not exhaustive. More context on potential response fields or failure modes would elevate transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with two sentences, each carrying essential information: purpose and polling behavior. No superfluous words. It front-loads the action ('Check the status') and provides a clear instruction ('Poll until status is completed').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema, no nested objects), the description covers the critical aspects: what it does and how to use it (polling). It does not detail the response format or error states, but for a polling status check, this level of completeness is sufficient. An example or more explicit success/failure cues would make it fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter 'generationId' has a clear description in the schema ('The generation ID returned from gamma_generate'), and the tool description adds value by explaining the polling context and expected status field. This goes beyond the schema, helping the agent understand the parameter's role in the overall workflow.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the purpose: checking the status of a gamma generation and polling until completion. It distinguishes itself from sibling tools like gamma_generate (which creates) and gamma_list_folders/themes (which list resources), making the tool's specific role unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage after generating, with polling behavior ('Poll until status is completed'). While it does not explicitly state when not to use it or name alternatives, the context of generation and polling is clear. An explicit exclusion (e.g., 'Do not use before generating') would improve, but current guidance is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

gamma_list_foldersA

List folders in your workspace. Use the returned IDs for folderIds parameter.

ParametersJSON Schema

Name	Required	Description
`after`	No	Cursor for pagination (from previous response's nextCursor).
`limit`	No	Max results per page (max 50).
`query`	No	Search folders by name (case-insensitive).

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full burden. It only states it lists folders and mentions IDs, but fails to disclose pagination behavior (though schema includes pagination params) or any other behavioral traits like read-only nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences with no extraneous words, directly addressing the tool's purpose and a key usage insight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with three parameters and no output schema, the description covers the main purpose and a usage hint. However, it lacks explanation of pagination behavior and response format, which would be helpful given no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds a small hint about using returned IDs, but does not significantly enhance understanding beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists folders in the workspace, which is distinct from sibling tools like gamma_create_from_template or gamma_generate. It also specifies the purpose of the returned IDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description hints at using returned IDs for other tools' folderIds parameter, but does not explicitly state when to use this tool versus other list tools, nor provides guidance on when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

gamma_list_themesA

List available themes in your workspace. Use the returned IDs for themeId parameter.

ParametersJSON Schema

Name	Required	Description
`after`	No	Cursor for pagination (from previous response's nextCursor).
`limit`	No	Max results per page (max 50).
`query`	No	Search themes by name (case-insensitive).

TDQS

A3.6/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden for behavioral traits. It does not mention that the tool is read-only, nor does it disclose pagination, rate limits, or authentication needs. The behavior is implied but not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, using two sentences. The first sentence clearly states the purpose, and the second provides actionable usage guidance. No unnecessary words, and it is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with no output schema, the description is largely complete. It explains the purpose and hints at output usage. The parameters are fully described in the schema. However, it could briefly mention the output format or pagination behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the parameters are already well-documented. The tool description does not add additional meaning or constraints beyond the schema, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List'), resource ('themes'), and scope ('in your workspace'), and distinguishes it from sibling tools like gamma_list_folders. The additional hint about using returned IDs for the themeId parameter adds context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some usage guidance by telling the agent to use the returned IDs for the themeId parameter, implying use when needing theme IDs. However, it does not specify when not to use this tool or mention any alternative tools, leaving room for ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

5 tool updatesv0.1.0Jun 28, 2026
- First observedgamma_create_from_template
- First observedgamma_generate
- First observedgamma_get_generation
- First observedgamma_list_folders
- First observedgamma_list_themes

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.8/5.0

Scored 2026-06-28 12:10 across 5 tools

Disambiguation5/5

Each tool targets a distinct operation: creating from template, generating new content, polling status, listing folders, and listing themes. No overlap.

Naming Consistency5/5

All tools follow a consistent 'gamma_verb_noun' pattern, with verbs like create_from_template, generate, get_generation, list_folders, list_themes.

Tool Count5/5

Five tools is well-scoped for a presentation/document generation server, covering creation, status polling, and resource listing without excess.

Completeness4/5

Covers the core workflow (generate, poll, list resources), but is missing delete or update operations for folders or themes, which are minor gaps.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

presentationsOAuth
com.getalai
Generate, edit, and export AI presentations to PDF, PPTX, or a shareable link.
App Automation Workplace & Productivity Design Tools
25
MagicSlidesOAuth
io.github.theindianappguy
Create presentations, docs, sheets and meeting notes from chat. Hosted link, editor, PPTX & PDF.
Workplace & Productivity Design Tools Content Management Systems
1
ClipiaOAuth
io.github.clipia-ai
Generate AI images, video, speech, music and presentations from Claude, ChatGPT and Cursor.
AI & Machine Learning Image & Video Processing
3
IndianAppGuy-magicslide-mcp-actual-test
ai.smithery
Generate polished PowerPoint presentations from text prompts, YouTube videos, or structured outlin…
Workplace & Productivity Multimedia Processing App Automation
2

Related MCP Servers

Gamma MCP Server
Content Management Systems Workplace & Productivity App Automation
sarafina98
A
license
Not graded
quality
D
maintenance
Enables AI-powered generation of presentations, documents, and webpages through the Gamma API. Supports theme selection, folder management, and automatic export to PowerPoint or PDF formats.
Updated 10 months ago (2025-11-12 01:54 UTC)
7
MIT
Gamma MCP Server
Content Management Systems Workplace & Productivity App Automation
isakskogstad
F
license
Not graded
quality
Not graded
maintenance
Enables AI assistants to generate presentations, documents, and webpages through the Gamma.app API with support for custom themes, tones, audiences, and image generation.
Updated 10 months ago (2025-11-19 05:40 UTC)
7
-
gamma-app-mcp
Workplace & Productivity Marketing
cphoskins
A
license
A
quality
C
maintenance
Enables generating presentations, documents, webpages, and social posts via Gamma's API with full parameter surface including templates, folders, headers/footers, and email sharing.
Updated 5 months ago (2026-04-09 00:17 UTC)
6
MIT
Gamma MCP Server
AI & Machine Learning Content Management Systems Marketing
Themoneyhollic
A
license
Not graded
quality
D
maintenance
Enables generating AI-powered presentations via the Gamma API directly from MCP clients like Claude for Desktop.
Updated a year ago (2025-05-14 21:19 UTC)
7
MIT