Gamma for AI agents
Gamma uses AI to generate presentations and interactive content, letting teams create decks and pages from a prompt or outline. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Gamma.
Generate a deck from a prompt
Generate a presentation from an outline once a user provides the topic and key points.
Create from an existing template
Create a new Gamma from a template so it matches an established brand style.
Check available themes
List themes as a read-only step before picking one for a new presentation.
5 Gamma actions, graded by risk.
Every Gamma action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- gamma.list_themesList Themes
- gamma.list_foldersList Folders
- gamma.get_gamma_file_urlsGet Gamma File URLs
write
2Create and change things. Allow, or ask the user first.
- gamma.create_from_templateCreate from Template
- gamma.generate_gammaGenerate a Gamma
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Gamma in three steps.
- 01Your users connect GammaThey add their Gamma api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create from Template” can wait for the user to approve.
- 03Any agent can actYour agent calls Gamma through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('gamma', { read: 'allow', write: 'ask', // create_from_template destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Gamma connects.
Users add their Gamma api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Gamma connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Gamma from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Gamma and Arc0, answered.
Can I use Gamma with Claude, ChatGPT or Cursor?
Yes. Connect Gamma to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Gamma actions you allow.
How do users connect Gamma?
Users add their Gamma api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Gamma actions can my agent take?
5 in total: 3 read, 2 write and 0 destructive, such as “create from Template”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Gamma?
Yes. Allow read actions and deny writes in the Gamma policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Gamma too?
Yes. The same Gamma connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Gamma into your agent.
Your users connect Gamma once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan