Provider REST API

16 actions

Connect Claude to Gamma

Generate presentations, documents and web pages with AI, then find, export and manage the gammas in a workspace. Toolspoke puts 16 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API key
Actions exposed: 16
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Gamma
Open the marketplace in your workspace, add Gamma to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with api key. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Gamma shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Gamma asks for

API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

API keyRequired: Gamma → Settings → API Keys (gamma.app/settings/api-keys) → create a key. API keys need a Pro, Ultra, Teams or Business plan. A key belongs to one workspace and spends its owner's credits there, so teammates sharing a key share one balance. Deleting a gamma also needs the owner to be a workspace admin.; sk-gamma-…

What Claude can do in Gamma

16 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 10Reads
Writes: 4Writes
Destructive: 2Destructive

Reads

Fetches data and changes nothing.

get_generation
Check a generation started by create_generation or create_generation_from_template. status is pending, completed or failed; once completed it carries gammaId, gammaUrl, exportUrl when an export was requested, and the credits spent. Poll every few seconds.
get_agent_generation
Check a generation started by create_agent_generation. Same polling pattern as get_generation, for gen_-prefixed ids.
list_themes
List the themes a generation can use - Gamma's standard themes and the workspace's own custom ones - with their ids. Needs no arguments, spends no credits and always returns something for a working key, which is why an install tests itself with it.
list_folders
List the workspace's folders with their ids, to pass as folderId when generating.
search_gammas
Full-text search over the titles and body text of the gammas this key can see, with filters for creator and last-updated time. Hits can carry a text snippet from the document. Send q or at least one filter.
get_gamma
Read one gamma's metadata - title, description, type, URL, author, theme, timestamps and whether it is archived. Not its full content.
search_templates
Search the workspace's templates and Gamma's official explore templates, returned as two lists. A hit's id can be used as gammaId in create_generation_from_template or templateId in create_agent_generation.
list_gamma_comments
List the comment threads and replies on one gamma. Comments are other people's words, so the output is not retained.
get_gamma_analytics
Engagement summary for one gamma - total views, unique viewers and editors, card count, last opened and daily views. Gamma notes the data can lag by about an hour.
get_export
Check an export started by export_gamma. Once status is completed it carries exportUrl, a download link to the document itself, so the output is not retained.

Writes

Creates or updates something on the other side.

create_generation
Start an AI generation of one presentation, document, social post or web page from a topic, an outline or a full draft. Returns a generationId at once; poll get_generation until status is completed, then use the gammaUrl it returns. Classified write rather than destructive, and deliberately so: it spends workspace credits, but what it makes is a new gamma inside the workspace, shared by the workspace's default settings, and delete_gamma removes it. This operation does not take Gamma's sharingOptions, emailOptions or publish fields, so it cannot email anyone a link or publish a public site - share from the Gamma app instead.
create_generation_from_template
Start a generation that adapts an existing one-page gamma used as a template: Gamma keeps its structure and rewrites the content from the prompt. Returns a generationId; poll get_generation. Write, not destructive, for the same reasons as create_generation: it spends credits and makes a new private-by-default gamma, it never changes the template, and it takes no sharing or publish options.
create_agent_generation
Start a generation run by the Gamma agent, which can read source URLs and, unless disableConnectors is set, the workspace's connected apps (such as Notion or Slack) while it writes. Returns a gen_-prefixed generationId; poll get_agent_generation. Write rather than destructive: it spends credits and makes a new gamma in the workspace, and it takes no sharing options.
export_gamma
Start an export of an existing gamma to PDF, PPTX or PNG (a .zip with one PNG per card). Returns an exportId; poll get_export for the download link. Write: it creates a file and changes nothing in the gamma.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

archive_gamma
Archive one gamma, taking it out of the active workspace for everyone who uses it without deleting it. Destructive because this API has no way to undo it: there is no unarchive endpoint, and restoring it means someone doing so in the Gamma app. Idempotent - archiving an archived gamma succeeds.
delete_gamma
Delete one gamma. Gamma archives it first if needed, then marks it for deletion; it is immediately inaccessible and no longer addressable through the API. Needs a workspace admin's key.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 16 actions above are the whole of it. A call to any other name is refused before it reaches Gamma rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to Gamma of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Gamma: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Gamma. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Gamma's own rate limits. A call that Gamma refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Gamma?

16 named actions: 10 that only read, 4 that write and 2 that delete or permanently alter something. They include create_generation, create_generation_from_template and get_generation. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Gamma connector need?

API key. The connector asks for api key. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Gamma connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 16 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Gamma connector not do?

The 16 actions above are the whole of it. A call to any other name is refused before it reaches Gamma rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Gamma of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Gamma. An agent has to ask. Toolspoke does not retry, queue or back off around Gamma's own rate limits. A call that Gamma refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Gamma's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Gamma?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More productivity connectors

Browse all of them