How to connect Amcards to OpenClaw
Connect Amcards to OpenClaw with ClawLink: paste your Amcards key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
AmcardsAPI KEYMCPAMCards enables users to create personalized greeting cards, automate mailing campaigns, strengthen customer relationships using a convenient online platform for individualized connections.. Once connected, OpenClaw can read and act on Amcards from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Amcards 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 Amcards setup: install one ClawHub skill, connect Amcards in the browser, and OpenClaw can call real Amcards 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 Amcards.
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 Amcards
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Amcards?"
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 Amcards in the ClawLink dashboard — paste your Amcards API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Amcards, 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 loginlogin opens the same browser approval and stores a credential locally. Once Amcards is connected in the dashboard, that agent calls the same 10 Amcards tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Amcards MCP for OpenClaw
Looking for a Amcards MCP server for OpenClaw? ClawLink connects Amcards to OpenClaw and exposes 10 Amcards tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Amcards integration works the same way.
What the OpenClaw Amcards integration can do
10 Amcards tools are ready for OpenClaw once the account is connected.
All 10 Amcards tools for OpenClaw
| Tool | What it does |
|---|---|
Get API schema amcards_get_api_schema | Retrieve the entire schema for AMCards API V1 |
Get cards amcards_get_cards | Retrieves a list of all cards associated with the authenticated account |
Get category amcards_get_category | Retrieve details of a specific category by ID |
Get category schema amcards_get_category_schema | Retrieve the schema for Category resource |
Get contacts amcards_get_contacts | Retrieves a list of contacts from AMCards |
Get gift amcards_get_gift | Retrieve details of a specific gift by ID |
Get public template amcards_get_public_template | Retrieve details of a specific public template by ID |
List categories amcards_list_categories | Retrieve a list of card template categories from AMCards |
List gifts amcards_list_gifts | Retrieve a list of Gift items offered by AMcards |
List public templates amcards_list_public_templates | Retrieve a list of public templates available to all users |
Try it: find the Amcards tool you need
Browse the 10 Amcards 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 Amcards, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Amcards, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Amcards, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Amcards, 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 Amcards working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Amcards API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Amcards 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 Amcards. | 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 Amcards actions to the runtime in a format your agent can reliably use. | 10 tools for Amcards are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Amcards 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 Amcards in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Amcards 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 Amcards skill but can't call the tools
The ClawHub skill teaches OpenClaw about Amcards, but the calls run through the ClawLink plugin and your connected account. Make sure Amcards 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 Amcards 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 Amcards tools
Amcards 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 Amcards 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.
Amcards 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 Amcards 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 Amcards integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Amcards: link your Amcards account once in the browser and OpenClaw can call the Amcards API through 10 ready-made tools — no custom code or token handling.
How do I add Amcards to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Amcards skill from ClawHub, then you click Connect in the dashboard to authorize Amcards. OpenClaw calls the tools from the next message — no config files, and the Amcards key you paste is stored server-side instead of in your environment.
How long does it take to connect Amcards to OpenClaw?
About two minutes. Sign in, click Connect next to Amcards in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Amcards 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 Amcards working from chat.
OpenClaw installed the Amcards skill but can't call the tools
The ClawHub skill teaches OpenClaw about Amcards, but the calls run through the ClawLink plugin and your connected account. Make sure Amcards 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.
