How to integrate Gamma MCP with OpenClaw

OpenClaw is only as useful as the tools it can authenticate. Composio’s OpenClaw guide for Gamma documents two ways to wire that up: paste a dashboard setup prompt into an OpenClaw chat, or install the Composio plugin, set a consumer key, and restart the gateway. Either path is meant to let an OpenClaw agent call Gamma presentation tools over managed MCP.

Gamma is an AI-powered platform for making beautiful, interactive presentations and documents. Composio lists five Gamma tools plus managed auth — OAuth, API keys, token refresh, and scopes — so you build against the tools instead of the token lifecycle. After you connect, the same guide says you can run Gamma actions from the OpenClaw interface you already use (Telegram, WhatsApp, TUI, and others) with natural language.

The steps below follow Composio’s hosted OpenClaw guide. They are not a first-party OpenClaw or Gamma product announcement.

Why route Gamma through Composio

Apart from a managed and hosted MCP server, Composio lists three reasons to sit in the middle:

• Programmatic tool calling lets the LLM write code in a remote workbench for complex tool chaining, which reduces round trips for frequent calls.
• Handling large tool responses outside the LLM context, to minimize context rot.
• Dynamic just-in-time access to 20,000 tools across 1500+ other apps, loading only what the task needs so the model is not overwhelmed by unused tools.

The Gamma MCP server is an implementation of the Model Context Protocol that connects an AI agent to a Gamma account. Composio describes it as structured, secure access so the agent can generate presentations, monitor generation progress, and retrieve finished files.

Path 1: Setup prompt

Use this if you would rather paste a prompt than edit plugin config.

1. Open the Composio dashboard OpenClaw connect flow.
2. Copy the setup prompt.
3. Run it in your OpenClaw chat interface.
4. Authenticate Gamma from the Composio dashboard.
5. Return to OpenClaw and start asking questions.

The page does not document extra CLI flags for this path. You copy the prompt, authenticate Gamma in the dashboard, then issue requests from chat.

Path 2: OpenClaw Composio plugin

This is the copy-paste plugin path.

Install the plugin:

openclaw plugins install @composio/openclaw-plugin

Copy the API key from the Composio dashboard, then set the consumer key. The documented command is:

openclaw config set plugins.entries.composio.config.consumerKey "ck_your_key_here"

Replace ck_your_key_here with your real consumer key. Composio describes that value as a consumer key in ck_... form.

Restart OpenClaw:

openclaw gateway restart

Go to your chat interface and start asking questions. When prompted, authenticate the app.

Configuration keys

The guide shows this plugin entry:

{
  "plugins": {
    "entries": {
      "composio": {
        "enabled": true,
        "config": {
          "consumerKey": "ck_your_key_here"
        }
      }
    }
  }
}

Documented options:

• enabled — Enable or disable the plugin. Default: true.
• consumerKey — Your Composio consumer key (ck_...). No default.
• mcpUrl — MCP server URL (advanced). Default: https://connect.composio.dev/mcp.

If a key is not on that table, it is unknown. Do not invent extra flags.

How the plugin registers Gamma tools

The plugin connects to Composio’s MCP server at https://connect.composio.dev/mcp and registers all available tools directly into the OpenClaw agent. Tools are called by name — no extra search or execute steps needed.

If a tool returns an auth error, the agent will prompt you to connect that toolkit in the Composio dashboard OpenClaw connect flow.

Composio’s FAQ on the same page distinguishes a standalone Gamma MCP server (a fixed set of Gamma tools tied to that server) from Composio Tool Router, which can dynamically load tools from Gamma and other apps through a single MCP endpoint. The FAQ also states that OpenClaw supports MCP integration, and that you can configure which Gamma scopes and actions are allowed when connecting your account, including bringing your own OAuth credentials or API configuration.

Gamma actions the agent can call

The page lists five supported tools:

1. Generate a Gamma — Generate a Gamma presentation, document, webpage, or social media content using AI.
2. Create from Template — Create new Gamma content based on an existing template.
3. List Themes — Fetch the list of themes available in your workspace.
4. List Folders — Retrieve a paginated list of folders in your Gamma workspace.
5. Get Gamma File URLs — Retrieve generation status and file URLs.

The same section describes what that looks like in practice: create decks or documents through simple prompts; produce summaries, reports, or educational material as shareable Gamma presentations; monitor each presentation request and completion status; and fetch download URLs for finished files so you can share or embed them. The hero copy mentions a pitch deck for a startup idea and an interactive onboarding presentation, driven by natural language, with authentication handled for you.

After you connect

Composio’s conclusion assumes the plugin path succeeded. You then interact with Gamma from your terminal, Web UI, or a messenger app using natural language. Benefits it lists: integration across TUI, Web UIs, and messenger apps such as Telegram, WhatsApp, and Slack; natural language commands for Gamma operations; managed authentication through Composio; access to 20,000+ tools across 1500+ apps for cross-app workflows; and programmatic tool calling for complex chaining.

Ask OpenClaw to generate a Gamma deck, then follow up so the agent can check generation status and retrieve file URLs. If authentication fails, connect Gamma in the Composio dashboard and retry from chat. For the exact install commands and tool names, stay on Composio’s OpenClaw Gamma guide.

Sources

• How to integrate Gamma MCP with OpenClaw