How to connect Gamma to OpenClaw (paste one key, 5 tools)

The usual route to Gamma access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Gamma setup: install one ClawHub skill, connect Gamma in the browser, and OpenClaw can call real Gamma actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect OpenClaw to Gamma.

1
Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin
2
Connect Gamma
Paste your API key in the dashboard.
3
Use it from chat
Ask OpenClaw: "What can you do with Gamma?"

Install by command

The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:

openclaw plugins install clawhub:clawlink-plugin

Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Gamma in the ClawLink dashboard — paste your Gamma API key once.

Verify the connection by asking OpenClaw:

Pull the relevant data from Gamma, summarize it in plain English, and point out anything that needs attention.

Using a different agent?

The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Gamma is connected in the dashboard, that agent calls the same 5 Gamma tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Gamma MCP for OpenClaw

Looking for a Gamma MCP server for OpenClaw? ClawLink connects Gamma to OpenClaw and exposes 5 Gamma tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Gamma integration works the same way.

What the OpenClaw Gamma integration can do

5 Gamma tools are ready for OpenClaw once the account is connected.

All 5 Gamma tools for OpenClaw

Tool	What it does
Get gamma file URLS `gamma_get_gamma_file_urls`	Retrieve generation status and file URLs
List folders `gamma_list_folders`	Retrieve a paginated list of folders in your Gamma workspace
List themes `gamma_list_themes`	Fetch the list of themes available in your workspace
Create from template `gamma_create_from_template`	Create new Gamma content based on an existing template
Generate gamma `gamma_generate_gamma`	Generate a Gamma presentation, document, webpage, or social media content using AI

Try it: find the Gamma tool you need

Browse the 5 Gamma tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Gamma, summarize it in plain English, and point out anything that needs attention.

List the relevant items in Gamma, group them by priority, and recommend what OpenClaw should do next.

Create it in Gamma for me, then confirm the important fields before you finish.

ClawLink vs. building it yourself

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Gamma working from chat.

	Manual	ClawLink
Credential handling	Collect, validate, store, and rotate the Gamma API key yourself, then make sure every tool call uses the right account.	Users complete the hosted ClawLink setup once and the connected Gamma account becomes available to the agent without you building credential management.
Ongoing maintenance	You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Gamma.	ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usability	You still need to expose the right Gamma actions to the runtime in a format your agent can reliably use.	5 tools for Gamma are already exposed through ClawLink, so the agent can read and act from chat immediately.

ClawLink vs. Composio

Composio also exposes Gamma to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Gamma in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the Gamma key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

OpenClaw installed the Gamma skill but can't call the tools

The ClawHub skill teaches OpenClaw about Gamma, but the calls run through the ClawLink plugin and your connected account. Make sure Gamma is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

Connection succeeds but no tools appear

Reconnect Gamma from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

"Tool schema not loaded yet" error when calling Gamma tools

Gamma tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Gamma call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Gamma returns 403 or "permission denied" on one action while others work

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

API key setup works but results look incomplete

Double-check that the API key for Gamma has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a OpenClaw Gamma integration?

Yes. ClawLink is the fastest way to connect OpenClaw to Gamma: link your Gamma account once in the browser and OpenClaw can call the Gamma API through 5 ready-made tools — no custom code or token handling.

How do I add Gamma to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Gamma skill from ClawHub, then you click Connect in the dashboard to authorize Gamma. OpenClaw calls the tools from the next message — no config files, and the Gamma key you paste is stored server-side instead of in your environment.

How long does it take to connect Gamma to OpenClaw?

About two minutes. Sign in, click Connect next to Gamma in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring Gamma up myself?

OpenClaw installed the Gamma skill but can't call the tools

How to connect Gamma to OpenClaw

Setup

Install the plugin

Connect Gamma

Use it from chat