# How to connect Amcards to Hermes Agent (paste one key, 10 tools) > Connect Amcards to Hermes with ClawLink: paste your Amcards key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/amcards Most guides for giving Hermes Agent Amcards access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Amcards setup: pair once in the browser and your always-on Hermes agent can act on Amcards for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Amcards. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Amcards** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 amcards # connect Amcards (browser OAuth) npx -y @useclawlink/cli actions amcards # list available actions npx -y @useclawlink/cli run amcards --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Amcards in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Amcards API key once. Verify the connection by asking Hermes: > Pull the relevant data from Amcards, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The Hermes 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 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Amcards MCP for Hermes Looking for a Amcards MCP server for Hermes Agent? ClawLink connects Amcards to Hermes Agent and exposes 10 Amcards 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 OpenClaw instead? The [OpenClaw Amcards integration](https://claw-link.dev/openclaw/amcards) works the same way. ## What the Hermes Agent Amcards integration can do 10 Amcards tools are ready for Hermes Agent once the account is connected. ### All 10 Amcards tools for Hermes | 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 | ## Example prompts **Get Api Schema** > Pull the relevant data from Amcards, summarize it in plain English, and point out anything that needs attention. **Get Cards** > Pull the relevant data from Amcards, summarize it in plain English, and point out anything that needs attention. **Get Category** > Pull the relevant data from Amcards, summarize it in plain English, and point out anything that needs attention. **Get Category Schema** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Amcards Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Amcards integration? Yes. ClawLink is the fastest way to connect Hermes to Amcards: link your Amcards account once in the browser and Hermes Agent can call the Amcards API through 10 ready-made tools — no custom code or token handling. ### How do I connect Amcards to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Amcards in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to Amcards in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Amcards working from chat. ### Hermes paired but still can't use Amcards Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [ActiveCampaign tools](https://claw-link.dev/hermes/activecampaign) — Marketing automation, CRM, and email marketing - [Hermes Benchmark Email integration](https://claw-link.dev/hermes/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp](https://claw-link.dev/hermes/mailchimp) — Create email campaigns and manage audiences