Feature requests

It would be great to have a /list endpoint on the gamma api to pull all the gammas that are api generated on our gamma account. Right now, we need to maintain the generation_id for each APi generated gamma and continue storing for displaying a completed gamma later. It would be good to have a fallback where all gammas can be accessed through an enumeration-like endpoint!

The Gamma MCP currently only supports creating new documents and presentations via the generate tool. There's no way to amend, update, or edit an existing Gamma after it's been created — the available tools are limited to generate, read_gamma, get_folders, and get_themes. This means any change, no matter how small, requires either manually editing in the Gamma web editor or regenerating the entire document from scratch (which creates a new file, loses any manual tweaks, and clutters the workspace).lease add tools to the Gamma MCP that allow: Updating an existing Gamma by ID — amend specific cards/sections, update text, replace tables, change dates, etc. without creating a new file Appending cards to an existing document or deck Replacing individual cards in place, so manual formatting on other cards is preserved This would make Gamma genuinely usable as part of an iterative AI-assisted workflow, rather than a one-shot generator.

When generating documents or presentations via the MCP/API, the cardOptions.dimensions parameter (e.g. a4, 16x9) is currently treated as a layout hint rather than enforced. The output defaults to Gamma's fluid/responsive layout regardless of the dimension passed, which means every generated file needs to be opened in the editor and manually set to the requested page/slide size before it can be used. Please make cardOptions.dimensions a hard constraint at generation time for both document and presentation formats, so that API/MCP users can generate print- or projection-ready files in a single step.

What to be able to create bulk images\graphics from the API

A way to connect to Claude code, currently I only see connectors to Claude desktop.

I’m using the Gamma Generate API to automatically create presentations from my own system. Right now, the API allows me to: create content with POST /generations check status and get the URL with GET /generations/{generationId} For my use case it’s very important that I can also delete specific presentations created via the API, without deleting my entire Gamma account. Why a DELETE endpoint would be helpful: I need to clean up presentations when a project or assignment is finished. I need to remove specific items for privacy and data management reasons when users request it. Manually deleting many API-generated presentations in the UI doesn’t scale. What I’d love to see: An officially supported DELETE endpoint (for example DELETE /v1.0/generations/{generationId}) that works with the existing API key, or another API-based way to remove or schedule deletion of individual items created through the API. This would make it much easier to use Gamma in workflows where privacy and document lifecycle management are important.

I would like to be able to send an image that has a url within my markdown file and that gets incorporated into the gamma generated cards. Something like this: ## Modular Deployment Structure Rather than placing all resources in a single flat configuration, the deployment uses a modular structure . A single root module orchestrates four child modules: - Networking — VPC, subnets, route tables, and internet gateway - TLS — Certificate generation for secure communication - Load Balancer — Application Load Balancer configuration and target groups - EC2 — Launch templates, Auto Scaling Group, and instance configuration

Like I want to build a presentation that can be updated with new data

Currently, if I want to get the pptx file I need to request a public link. This is irrelevant when the data is sensitive.

Now I know the API hasn't even launched yet... BUT... as I'm watching a video on claude code agents and thinking about what I do with Notion MCP in Claude today it got me thinking about some of my workflows and how it would be nice to be have a Gamma MCP server • getting a link to an existing gamma to share since half the time it takes me a while to find a gamma if it's not the most recent one • moving gammas to a directory rather than clicking one by one • creating an initial gamma • creating and editing images (tbh I want to do this outside of the scope of a gamma)