# How to connect Gelato to OpenClaw (paste one key, 13 tools)

> Connect Gelato to OpenClaw with ClawLink: paste your Gelato key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/gelato

The usual route to Gelato 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 Gelato setup: install one ClawHub skill, connect Gelato in the browser, and OpenClaw can call real Gelato 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 Gelato.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Gelato** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask OpenClaw in plain English.

**Paste this into OpenClaw to set up ClawLink:**

> I want to connect my apps to OpenClaw through ClawLink.
> Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin`
> When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md

**Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect gelato  # connect Gelato (browser OAuth)
npx -y @useclawlink/cli actions gelato  # list available actions
npx -y @useclawlink/cli run gelato <action> --input '<json>'  # execute (add --confirm for writes)
```

### 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:

```bash
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 Gelato in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Gelato API key once.

Verify the connection by asking OpenClaw:

> Use Gelato to check stock availability and walk me through the result in plain English.

### 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:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Gelato is connected in the dashboard, that agent calls the same 13 Gelato tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## Gelato MCP for OpenClaw

Looking for a Gelato MCP server for OpenClaw? ClawLink connects Gelato to OpenClaw and exposes 13 Gelato tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Gelato integration](https://claw-link.dev/hermes/gelato) works the same way.

## What the OpenClaw Gelato integration can do

13 Gelato tools are ready for OpenClaw once the account is connected. The 12 below are the ones people reach for most; your agent can call all 13.

### 12 of 13 Gelato tools for OpenClaw

| Tool | What it does |
|---|---|
| **Check stock availability** `gelato_check_stock_availability` | Check current regional stock status for 1 to 250 Gelato product UIDs |
| **Get catalogs** `gelato_get_catalogs` | List available Gelato product catalogs, or provide catalog_uid to retrieve one catalog's full |
| **Get order** `gelato_get_order` | Retrieve the full current state, financial status, fulfillment status, shipment tracking |
| **Get product** `gelato_get_product` | Retrieve one Gelato product's attributes, dimensions, weight, supported countries |
| **Get product prices** `gelato_get_product_prices` | Return Gelato's quantity price tiers for one product, optionally localized by destination |
| **Quote order** `gelato_quote_order` | Quote product and shipping costs and delivery estimates for a destination before creating an |
| **Search orders** `gelato_search_orders` | Search Gelato orders with status, reference, date, country, currency, channel, type, store, or |
| **Search products** `gelato_search_products` | Search printable products in a Gelato catalog by catalog attribute values and return one |
| **Create draft order** `gelato_create_draft_order` | Create a Gelato draft for review or later submission without entering production |
| **Create order** `gelato_create_order` | Create a production order that can immediately enter fulfillment and charge the connected |
| **Cancel order** `gelato_cancel_order` | Cancel a regular Gelato order before production advances too far |
| **Submit draft order** `gelato_submit_draft_order` | Convert an existing draft into a regular production order |

## Example prompts

**Check Stock Availability**

> Use Gelato to check stock availability and walk me through the result in plain English.

**Get Catalogs**

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

**Get Order**

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

**Get Product**

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

## 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 Gelato working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Gelato API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Gelato 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 Gelato. | 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 Gelato actions to the runtime in a format your agent can reliably use. | 13 tools for Gelato are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Gelato 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 Gelato in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Gelato key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### OpenClaw installed the Gelato skill but can't call the tools
The ClawHub skill teaches OpenClaw about Gelato, but the calls run through the ClawLink plugin and your connected account. Make sure Gelato 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 Gelato 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 Gelato tools
Gelato 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 Gelato 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.

### Gelato 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 Gelato has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Gelato integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Gelato: link your Gelato account once in the browser and OpenClaw can call the Gelato API through 13 ready-made tools — no custom code or token handling.

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

### How long does it take to connect Gelato to OpenClaw?
About two minutes. Sign in, click Connect next to Gelato in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Gelato up myself?
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 Gelato working from chat.

### OpenClaw installed the Gelato skill but can't call the tools
The ClawHub skill teaches OpenClaw about Gelato, but the calls run through the ClawLink plugin and your connected account. Make sure Gelato 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.

## Related

- [Cloudcart](https://claw-link.dev/openclaw/cloudcart) — CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently.
- [OpenClaw Wix integration](https://claw-link.dev/openclaw/wix) — Manage sites, products, orders, and bookings
- [OpenClaw Baselinker integration](https://claw-link.dev/openclaw/baselinker) — BaseLinker is a comprehensive e-commerce management platform that integrates with various marketplaces, online stores, carriers, and accounting systems to streamline order processing, inventory management, and sales automation.
