generate-presentationLABSCO SUMMARY
A deck from a sentence, without leaving the conversation.
The value is in the parameters rather than the generation: audience, tone and length are set in the same request as the topic, so what comes back is already aimed at the room you are presenting to.
What it is
A single-tool server in front of Gamma's generation API. You pass a topic and the parameters that shape the deck; it posts to Gamma and returns the link to the finished presentation.
What you get
generate-presentation— takesinputTextas the topic or prompt and returns a link to the generated deck- Shaping arguments:
tone,audience,textAmountas short, medium or long,textModeas generate or summarize, andnumCardsfor slide count - Further optional controls for
imageModel,imageStyle,editorModeandadditionalInstructions
Requirements
A Gamma API key in GAMMA_API_KEY, loaded from a .env in the project root — the server logs a fatal error and exits at startup if the key is missing. Node.js v16 or higher and npm. It runs from source over stdio with npx ts-node src/index.ts, so the client entry needs cwd set to the absolute path of the project directory and the key available to the process the client launches. Requests go to https://api.gamma.app/public-api/v0.1/generate.
Setup effort
Build from source — git clone https://github.com/nickloveinvesting/gamma-mcpserver.git
USE CASES
01
Turning a discussion into slides
Feed the conclusion you just reached as the prompt and get a deck link back without restating it in a slide editor.
02
Aiming the same content at a different room
Regenerate with a different audience and tone so the executive version and the engineering version come from one source.
03
Keeping a deck short
Set numCards and textAmount up front rather than cutting slides afterwards.
04
Condensing an existing document
Switch textMode to summarize and pass the long-form text, so the deck compresses what you have instead of inventing new material.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- npx on PATH
- Node.js
- GAMMA_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/nickloveinvesting/gamma-mcpserver.git
cd gamma-mcpserver
npm install @modelcontextprotocol/sdk zod node-fetch typescript ts-node @types/nodeCreate a file named .env in the project root containing GAMMA_API_KEY="<YOUR_GAMMA_API_KEY>"
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"gamma-presentation-generator": {
"command": "npx",
"args": [
"ts-node",
"src/index.ts"
],
"cwd": "<YOUR_PATH_TO_GAMMA_MCP_SERVER>"
}
}
}<YOUR_PATH_TO_GAMMA_MCP_SERVER> is the full path of the gamma-mcpserver folder the clone step created (run pwd inside it). The server reads GAMMA_API_KEY from the .env file in that folder.
The configuration on this page does not set GAMMA_API_KEY; the project's instructions put it in a .env file. Check which folder the server reads that file from before you rely on it.
