---
title: "Gamma MCP in Slack: ask an AI teammate to turn a thread into a deck | Chickpea"
description: "Use Gamma's MCP server from Slack. Give a channel an AI teammate connected to Gamma, then ask it for a deck, a one-page doc, or a PDF. Open source."
canonical: https://chickpea.co/connectors/gamma
keyword: "Gamma MCP in Slack"
verified: 2026-09-17
---

# A teammate in Slack that turns a thread into a deck, on Gamma's MCP server.

> Chickpea gives a channel a named AI teammate that holds its own Gamma connection. It calls Gamma's MCP server at [mcp.gamma.app/mcp](https://developers.gamma.app/mcp/gamma-mcp-server) with an API key you paste once, so there is no client to configure. Ask it in Slack to write up the thread as a ten-card deck, find the gamma someone made last week, or export one to PowerPoint, and the link lands back in the thread.

Facts checked against the sources on September 17, 2026. The HTML page is at https://chickpea.co/connectors/gamma; every connector is listed at https://chickpea.co/connectors; the site index for agents is at https://chickpea.co/llms.txt.

**Gamma** (Gamma Tech, Inc., https://gamma.app): Create and browse presentations, documents, and webpages. Category: Docs and files. Lane: Vendor MCP server. Sign in: API key.

**Chickpea**: an open source Slack app that gives a workspace named AI teammates, each with its own handle, instructions, memory, connected accounts, schedules, and model, deployed to your own Cloudflare account or a Node host.

## What people ask it
The teammate in these examples is @growth, published to #growth.

### Turn a thread or an outline into a deck
- @growth make a 10-card deck out of this thread for the Thursday review, professional theme
- @growth take the outline Marco posted and build a presentation from it, brief text, no stock photos

Generating is the one thing Gamma charges for, so the teammate proposes the deck and waits for a yes. Gamma prices a generation at one to three credits a card, and more when it draws images, so the reply says what it is about to spend. It cannot quietly start one. Chickpea refuses any MCP tool whose name is not an unambiguous read verb unless your own message names the action.

### Write a one-page doc or a webpage
- @growth turn the decision in this thread into a one-page doc for the leadership channel
- @growth make a webpage from this launch brief, four sections, save it to the Marketing folder

Gamma's generate tool takes a format of presentation, document, social, or webpage, so the same ask makes a doc or a page instead of a deck. It also takes a folder and a theme, both of which the teammate looks up first. This spends credits too, so it asks before it runs.

### Find and read a gamma that already exists
- @growth find the gammas with onboarding in the title and say when each was made
- @growth read the Q3 roadmap gamma and pull out the dates it commits to

Browsing and reading are reads, so they go straight through and spend nothing. Gamma documents a tool that searches your gammas and templates, and a read-only tool that returns the full content of one from its ID or URL. A long answer comes back as a table in the thread.

### Export a gamma to PDF or PowerPoint
- @growth export the pricing deck as a pptx and drop the link here
- @growth give me a PDF of the onboarding gamma for the offsite pack

Gamma exports an existing gamma to PDF, PPTX, or PNG, and PNG comes back as a zip with one image a card. Nothing new is written and no card is generated, so this applies at once and the download link is posted when the export finishes. Your message still has to name the export.

### On a schedule
- @growth every Monday at 9am Pacific, list the gammas with weekly update in the title here
- @growth every Friday at 4pm Eastern, post the view counts on the launch deck

A schedule saves on the spot. It needs an explicit time zone, runs under the Gamma connection of the person who asked, and is paused rather than run if that connection goes away. Gamma's browse tool takes a search term and not a date range, so ask for a phrase it can match. Keep scheduled runs to reads unless you want credits spent while nobody is watching.

### Example conversations

**Turn the thread into a deck**
> **Dana:** @growth make a 10-card deck out of this thread for Thursday’s review, professional theme.
> **@growth:** Here is the outline I would hand Gamma, on the Consultant theme. Generating spends credits, so I am asking first.
> Buttons: Generate the deck · Change the outline · Leave it
> **@growth:** Gamma charges one to three credits a card, so ten cards is roughly 10 to 30. Your message has to name the change for me to make one.

**Find one that exists**
> **Marco:** @growth find the gammas with onboarding in the title and say which is newest.
> **@growth:** Five match. The newest is Onboarding, engineering, v3, and it is the only one that mentions the new stack.
>
> | Title | Type | Cards | Folder |
> |---|---|---|---|
> | Onboarding, engineering, v3 | Presentation | 14 | People |
> | Onboarding, engineering, v2 | Presentation | 11 | People |
> | Customer onboarding, 2026 | Document | 6 | Northwind |
> | Onboarding checklist | Document | 3 | People |
> | Onboarding deck (template) | Template | 9 | , |
> **@growth:** Browsing and reading are reads, so nothing was generated and no credits went.

**Export it**
> **Sofia:** @growth export the pricing deck as a pptx and drop the link here.
> **@growth:** Done. Pricing, Q4, 18 cards, as a PowerPoint file. Download the pptx
> **@growth:** An export makes a file from what is already there, so it went straight through. Nothing was generated and no card changed. PDF and PNG work the same way, and PNG comes back as a zip with one image a card.

**Every Monday**
> **Priya:** @growth every Monday at 9am Pacific, list the gammas with weekly update in the title here.
> **@growth:** Saved. Every Monday at 9:00 AM Pacific I’ll search for gammas with weekly update in the title and post them in #growth. First run is Mon Sep 21.
> **@growth:** It runs on my Gamma connection and only searches, so it spends no credits. Say “pause the Monday list” if you want it to stop.

## Connect Gamma
1. Check the plan. Gamma says API keys are available on its **Pro**, **Ultra**, **Teams**, and **Business** plans. Free and Plus accounts can use Gamma's own connectors, but they cannot make a key, so they cannot make this connection.
2. In Gamma, open [Settings → API keys](https://gamma.app/settings/api-keys) and create one. It starts with `sk-gamma-`. The key acts as the Gamma account that made it, and every generation it runs spends that account's credits.
3. In Chickpea Admin, open the teammate, then **Connections**, find **Gamma**, and choose **Connect**. Or ask in Slack, `@growth connect Gamma`, and follow the link it posts.
4. Choose who uses it. **Team** is one shared key that everyone who can use the teammate acts through, and one credit balance behind it. **Personal** means each member pastes their own. Then paste the key into the write-only **Credential** field, which is stored once on your deployment and sent as the `X-API-KEY` header.
5. Ask something. `@growth find the gammas with onboarding in the title` is a good first question, because browsing reads, changes nothing, and spends no credits.

A connection belongs to one teammate. Giving a second teammate Gamma means a second key, so the credits a design teammate burns on image-heavy decks never come out of the balance behind the growth teammate.

## What the teammate is handed with Gamma
There is no built-in Chickpea skill for Gamma, and none is needed. The tools arrive from Gamma's MCP server: Chickpea connects before it saves anything, records what the server answered with, and exposes only those tools. Gamma documents tools for generating from scratch, generating a multi-page gamma, generating from a template, checking a generation, making a standalone image, exporting to PDF, PPTX, or PNG, browsing gammas, reading one, reading its comments, reading engagement analytics, and browsing themes and folders.

Gamma lists the tools and what each one does: https://developers.gamma.app/mcp/mcp-tools-reference

## Beside Gamma
- **Google Slides:** A Gamma deck for the draft, Slides for the file the client edits
- **Google Docs:** The doc that holds the decision, written up as the deck that presents it
- **Notion:** Notion holds the spec, Gamma holds the readout it turns into
- **Google Drive:** Export the gamma to PDF, then file it where the team already looks
- All 37 connectors: https://chickpea.co/connectors

## Questions people ask

### Does Gamma have an MCP server?
Yes. Gamma describes it as a hosted server that lets AI tools create new gammas, browse and read existing ones, generate images, and export to PDF, PPTX, or PNG on your behalf. Gamma says the same server powers its connectors in Claude and ChatGPT and its own Slack app. Chickpea connects to that server, so a teammate in a Slack channel uses it with no client installed anywhere.

### What is the URL for the Gamma MCP server?
mcp.gamma.app/mcp, over streamable HTTP. In Chickpea you never type it. The Gamma preset carries that URL, and a connection made from the preset cannot be pointed at another address. The connector never touches Gamma's REST API, which is a different product with its own endpoints.

### Which Gamma plan does this need?
A paid one. Gamma says API keys are available on Pro, Ultra, Teams, and Business plans, and a key is what this connection stores. Gamma also says its ChatGPT and Claude connectors work on all plans, including Free and Plus, so a Free account can use Gamma inside those assistants but cannot make the key a Chickpea teammate needs.

### Does it spend Gamma credits?
Generating does. Gamma bills the API on credits and puts a generation at one to three credits a card, with images charged separately from two credits each up to a hundred and twenty-five for its largest model. Gamma returns the credits deducted and the balance remaining with each finished generation, so the teammate can say what a deck cost. Browsing, reading, and exporting are not on Gamma's credit table. Rates change, and Gamma says so, which is another reason the teammate asks before it generates.

### Can it edit a gamma that already exists?
No. Gamma is direct about this: editing is only available in the Gamma app, and its read tool cannot modify anything. What the teammate can do is make a new gamma from an existing template, which keeps the template's structure and adapts the content. So an ask to "update the deck" produces a new one rather than a changed one, and the reply says so.

### Can it delete a gamma?
No. There is no delete among the tools Gamma documents for its MCP server, and an MCP connection can only call tools the server answered with. Gamma's REST API does have a delete endpoint, but this connector does not reach the REST API. Nothing already in your workspace can be removed through the teammate.

### Is this Gamma's own AI?
The making is Gamma's. Gamma writes the cards, picks the layout, and sources the images, exactly as it does when you type a prompt on gamma.app. Chickpea is the part in Slack: a named teammate with saved instructions, a channel it works in, schedules, and its own connection. It hands Gamma the brief and posts back the link.

### Do I still need the Gamma app for Slack?
Keep it if you like it. Gamma ships its own Slack app, powered by the same MCP server, and it does a lot: mention it in a thread and it reads the conversation and makes a gamma, generates images from up to four attached reference images, browses your templates, exports, and previews gamma links pasted in a channel. It is Gamma and nothing else. A Chickpea teammate holds Gamma beside its other connections, so the deck can be built from the ticket, the doc, or the dashboard that prompted it, and the whole run is visible in one thread. Both can be installed.

### Can I use the Gamma connector in Claude or ChatGPT instead?
Yes, and Gamma documents both, along with Glean, Superhuman, and Atlassian Rovo, on any plan and with no API key. Those put Gamma in one person's assistant, where only that person sees what came back. A teammate puts the same server in a channel, with a stored connection, saved instructions, schedules, and every generation visible where someone asked for it. Plenty of teams run both.

### Where does the API key live?
On your deployment, in a write-only Credential field outside the teammate record. It never enters the model's context, the tool arguments the model writes, or Slack. The model picks a connection by id and the key goes into the X-API-KEY header at the last step on the way out. Disconnect the account and the stored secret is removed, after any schedule that depended on it is paused.

## Sources
- [Chickpea docs: connector catalog, the Gamma preset, its lane and its plan note](https://docs.chickpea.co/reference/connector-catalog/)
- [Chickpea docs: connections, team and personal accounts, the binding as a ceiling](https://docs.chickpea.co/agents/connections/)
- [Chickpea docs: authority and confirmation, including the read-verb gate](https://docs.chickpea.co/security/authority-and-confirmation/)
- [Chickpea docs: connect a service, the write-only credential field and the Slack link](https://docs.chickpea.co/agents/connect-a-service/)
- [Chickpea docs: schedules, time zones and what a paused schedule does](https://docs.chickpea.co/agents/schedules/)
- [Chickpea source: the Gamma preset (server URL, transport, the X-API-KEY header)](https://github.com/pejmanjohn/chickpea/blob/main/src/config/presets.ts)
- [Chickpea source: an MCP connection exposes approved tools that are still discovered](https://github.com/pejmanjohn/chickpea/blob/main/src/config/types.ts)
- [Gamma docs: the MCP server, what it can do, and that it powers the Slack app](https://developers.gamma.app/mcp/gamma-mcp-server)
- [Gamma docs: the MCP tools reference, every tool and whether it is read-only](https://developers.gamma.app/mcp/mcp-tools-reference)
- [Gamma docs: access and pricing, the plans an API key needs and the credit table](https://developers.gamma.app/get-started/access-and-pricing)
- [Gamma docs: connect integrations, the Slack app and the ChatGPT and Claude connectors](https://developers.gamma.app/connectors/connectors-and-integrations)
- [Chickpea source on GitHub](https://github.com/pejmanjohn/chickpea)

## More
- [Ahrefs MCP in Slack](https://chickpea.co/connectors/ahrefs.md)
- [Airtable MCP in Slack](https://chickpea.co/connectors/airtable.md)
- [Asana AI agent in Slack](https://chickpea.co/connectors/asana.md)
- [Jira and Confluence MCP in Slack](https://chickpea.co/connectors/atlassian.md)
- [BugSnag MCP in Slack](https://chickpea.co/connectors/bugsnag.md)
- [Cloudflare MCP in Slack](https://chickpea.co/connectors/cloudflare-api.md)
- [Exa MCP in Slack](https://chickpea.co/connectors/exa.md)
- [Firecrawl MCP in Slack](https://chickpea.co/connectors/firecrawl.md)
- [Fireflies MCP in Slack](https://chickpea.co/connectors/fireflies.md)
- [Gmail AI agent in Slack](https://chickpea.co/connectors/gmail.md)
- [Gong AI agent in Slack](https://chickpea.co/connectors/gong-managed.md)
- [Google Ads AI agent in Slack](https://chickpea.co/connectors/google-ads.md)
- [Google Analytics AI agent in Slack](https://chickpea.co/connectors/google-analytics.md)
- [Google Calendar AI agent in Slack](https://chickpea.co/connectors/google-calendar.md)
- [Google Docs AI agent in Slack](https://chickpea.co/connectors/google-docs.md)
- [Google Drive AI agent in Slack](https://chickpea.co/connectors/google-drive.md)
- [Google Search Console AI agent in Slack](https://chickpea.co/connectors/google-search-console.md)
- [Google Sheets AI agent in Slack](https://chickpea.co/connectors/google-sheets.md)
- [Google Slides AI agent in Slack](https://chickpea.co/connectors/google-slides.md)
- [Granola MCP in Slack](https://chickpea.co/connectors/granola.md)
- [HubSpot AI agent in Slack](https://chickpea.co/connectors/hubspot-managed.md)
- [Hugging Face MCP in Slack](https://chickpea.co/connectors/huggingface.md)
- [incident.io MCP in Slack](https://chickpea.co/connectors/incident-io.md)
- [Intercom MCP in Slack](https://chickpea.co/connectors/intercom.md)
- [Linear MCP in Slack](https://chickpea.co/connectors/linear.md)
- [LunarCrush MCP in Slack](https://chickpea.co/connectors/lunarcrush.md)
- [Meta Ads MCP in Slack](https://chickpea.co/connectors/meta-ads.md)
- [Monday.com MCP in Slack](https://chickpea.co/connectors/monday.md)
- [Neon MCP in Slack](https://chickpea.co/connectors/neon.md)
- [Notion Slack integration with an AI agent](https://chickpea.co/connectors/notion-managed.md)
- [PostHog MCP in Slack](https://chickpea.co/connectors/posthog.md)
- [Sentry MCP in Slack](https://chickpea.co/connectors/sentry.md)
- [Stripe MCP in Slack](https://chickpea.co/connectors/stripe.md)
- [Supabase MCP in Slack](https://chickpea.co/connectors/supabase.md)
- [YouTube AI agent in Slack](https://chickpea.co/connectors/youtube-managed.md)
- [Zendesk AI agent in Slack](https://chickpea.co/connectors/zendesk.md)
- [All connectors](https://chickpea.co/connectors.md)

## Try Chickpea
- Site: https://chickpea.co/
- Deploy to Cloudflare: https://deploy.workers.cloudflare.com/?url=https://github.com/pejmanjohn/chickpea
- Source, Apache 2.0: https://github.com/pejmanjohn/chickpea
- Docs: https://docs.chickpea.co