Gumroad + OpenClaw

Connect Gumroad to OpenClaw Prepare a grounded sales and product briefing

Read products with OpenClaw and Agent200. Prepare a sales and product briefing using the connected user’s own Gumroad account.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Gumroad tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Save the Agent200 server settings in OpenClaw, inspect tool discovery, then read one product the user can access. A saved setting alone does not verify the read.

Start with one identified product. Preserve returned product, sale and subscription fields; report missing data and keep the workflow read-only.

Provider reference: Gumroad API.

Connector
Gumroad
Works with
OpenClaw · Agent app, through MCP
Authentication
Managed OAuth, per end user
Tools
5 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Gumroad enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • An end user with a Gumroad account. They approve access once, on Gumroad's own page.
  • OpenClaw, with custom MCP servers allowed. OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.

Connect Gumroad to OpenClaw

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page and store it securely.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Store your key in ~/.openclaw/.env

    OpenClaw fills ${AGENT200_API_KEY} in its config from ~/.openclaw/.env, so the key never sits in the config itself.

    ~/.openclaw/.env
    MCP: OpenClaw key in ~/.openclaw/.env
    AGENT200_API_KEY=your-agent200-api-key
  3. 3

    Step 3: Save the server

    openclaw mcp set takes one JSON object. Always set the transport to streamable-http: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves ${AGENT200_API_KEY} for OpenClaw. In the Control UI, add it under Settings > MCP, then put the header in the config editor on the same page.

    Stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while it is running.

    Terminal
    MCP: OpenClaw save the server from the CLI
    openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}'
  4. 4

    Step 4: Probe the server

    Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.

    Terminal
    MCP: OpenClaw probe the server
    openclaw mcp doctor agent200 --probe
    openclaw mcp status --verbose
  5. 5

    Step 5: Authorize Gumroad

    Connect the intended user and test one accessible product.

Test your connection

Run one request to check everything is wired up.

Ask

Read the Gumroad product I identify and prepare a sales and product briefing. Name the source and use only product, sale and subscription fields. State access gaps; do not change records.

What should come back

  • The selected product is identified.
  • Only the returned product, sale and subscription fields are reported.
  • Access gaps and missing context are explicit; no source data is changed.

Check the selected product ID, account scope, read permission and pagination. Sales and subscription states may change through refunds or cancellation. Use returned dates and statuses; do not equate gross sales with payouts.

Get your API key

Create a key in the Agent200 dashboard. It reaches Gumroad and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Gumroad to OpenClaw.

Agent brief
Goal: connect Gumroad to OpenClaw with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/gumroad/framework/openclaw/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into OpenClaw's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Gumroad is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to OpenClaw: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for OpenClaw's exact menus or commands.
4. The first Gumroad request returns an authorization link if the user has not connected Gumroad yet: show it to them and continue once they have approved access on Gumroad's own page.
5. Check it works with this request: "Read the Gumroad product I identify and prepare a sales and product briefing. Name the source and use only product, sale and subscription fields. State access gaps; do not change records."
   What should come back:
   - The selected product is identified.
   - Only the returned product, sale and subscription fields are reported.
   - Access gaps and missing context are explicit; no source data is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Gumroad, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/gumroad/framework/openclaw.md

Gumroad tools OpenClaw can call

  • List products

    Read
    gumroad_list_products

    Find products owned by the authorized seller.

  • Read a product

    Read
    gumroad_get_product

    Retrieve one identified product.

  • List sales

    Read
    gumroad_list_sales

    Find sales within an explicit period or product scope.

  • Read a sale

    Read
    gumroad_get_sale

    Retrieve one identified sale.

  • List subscribers

    Read
    gumroad_list_subscribers

    Find subscriptions for an identified membership product.

How it works

  1. 01

    You ask OpenClaw

    In your own words, for something in Gumroad.

  2. 02

    OpenClaw picks a tool

    It sees the Gumroad tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    With your own Gumroad connection, within the tools and scopes your project allows.

  4. 04

    OpenClaw answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Gumroad account.

Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Gumroad enforces what its API grants.

Troubleshooting

The source cannot be read

Check the selected product ID, account scope, read permission and pagination. Sales and subscription states may change through refunds or cancellation. Use returned dates and statuses; do not equate gross sales with payouts.

FAQ

How do I verify this result?

Compare the named product and returned product, sale and subscription fields with the source. Treat missing information as missing, not as a fact.

Use Gumroad with another framework

200 OK

Gumroad, connected to OpenClaw.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)