A teammate in Slack that turns a thread into a deck, on Gamma's 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.

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.

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.

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.

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.

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.

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.

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.

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.

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.