How to connect Curated to OpenClaw
Connect Curated to OpenClaw with ClawLink: paste your Curated key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine.
CuratedAPI KEYMCPCurated is a platform that enables users to collect, curate, and publish newsletters, integrating with various services through its API.. Once connected, OpenClaw can read and act on Curated from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Curated 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 Curated setup: install one ClawHub skill, connect Curated in the browser, and OpenClaw can call real Curated 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 Curated.
1Install 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 Curated
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Curated?"
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-pluginThen 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 Curated in the ClawLink dashboard — paste your Curated API key once.
Verify the connection by asking OpenClaw:
List the relevant items in Curated, group them by priority, and recommend what OpenClaw should do next.
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 loginlogin opens the same browser approval and stores a credential locally. Once Curated is connected in the dashboard, that agent calls the same 6 Curated tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Curated MCP for OpenClaw
Looking for a Curated MCP server for OpenClaw? ClawLink connects Curated to OpenClaw and exposes 6 Curated tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Curated integration works the same way.
What the OpenClaw Curated integration can do
6 Curated tools are ready for OpenClaw once the account is connected.
All 6 Curated tools for OpenClaw
| Tool | What it does |
|---|---|
List categories curated_list_categories | List all categories for a publication |
List email subscribers curated_list_email_subscribers | List all email subscribers for a publication |
List issues curated_list_issues | Lists all issues (newsletters) for a Curated publication with pagination support |
List publications curated_list_publications | List all publications accessible by the API key |
Create draft issue curated_create_draft_issue | Create a draft issue for a publication |
Create link curated_create_link | Create a collected link for a publication |
Try it: find the Curated tool you need
Browse the 6 Curated tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
List the relevant items in Curated, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Curated, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Curated, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Curated, group them by priority, and recommend what OpenClaw should do next.
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 Curated working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Curated API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Curated 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 Curated. | 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 Curated actions to the runtime in a format your agent can reliably use. | 6 tools for Curated are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Curated 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 Curated in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Curated 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 Curated skill but can't call the tools
The ClawHub skill teaches OpenClaw about Curated, but the calls run through the ClawLink plugin and your connected account. Make sure Curated 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 Curated 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 Curated tools
Curated 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 Curated 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.
Curated 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 Curated 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 Curated integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Curated: link your Curated account once in the browser and OpenClaw can call the Curated API through 6 ready-made tools — no custom code or token handling.
How do I add Curated to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Curated skill from ClawHub, then you click Connect in the dashboard to authorize Curated. OpenClaw calls the tools from the next message — no config files, and the Curated key you paste is stored server-side instead of in your environment.
How long does it take to connect Curated to OpenClaw?
About two minutes. Sign in, click Connect next to Curated in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Curated 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 Curated working from chat.
OpenClaw installed the Curated skill but can't call the tools
The ClawHub skill teaches OpenClaw about Curated, but the calls run through the ClawLink plugin and your connected account. Make sure Curated 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.
