# How to connect Cloudcart to Hermes Agent (paste one key, 150 tools) > Connect Cloudcart to Hermes with ClawLink: paste your Cloudcart key once and 150 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/cloudcart Most guides for giving Hermes Agent Cloudcart 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 Cloudcart setup: pair once in the browser and your always-on Hermes agent can act on Cloudcart for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — 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. ## Setup It takes three steps to connect Hermes to Cloudcart. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Cloudcart** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **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 cloudcart # connect Cloudcart (browser OAuth) npx -y @useclawlink/cli actions cloudcart # list available actions npx -y @useclawlink/cli run cloudcart --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 Cloudcart in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Cloudcart API key once. Verify the connection by asking Hermes: > Use Cloudcart to add category properties and walk me through the result in plain English. ### 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 Cloudcart is connected in the dashboard, that agent calls the same 150 Cloudcart 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). ## Cloudcart MCP for Hermes Looking for a Cloudcart MCP server for Hermes Agent? ClawLink connects Cloudcart to Hermes Agent and exposes 150 Cloudcart 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 Cloudcart integration](https://claw-link.dev/openclaw/cloudcart) works the same way. ## What the Hermes Agent Cloudcart integration can do 150 Cloudcart tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 150. ### 30 of 150 Cloudcart tools for Hermes | Tool | What it does | |---|---| | **Add category properties** `cloudcart_add_category_properties` | Add properties to a category relationship | | **Add to cart** `cloudcart_add_to_cart` | Add an item to the cart | | **Clear cart** `cloudcart_clear_cart` | Remove all items from the specified cart | | **Create blog category** `cloudcart_create_blog_category` | Create a new blog category in CloudCart | | **Get blog author** `cloudcart_get_blog_author` | Retrieve details of a specific blog author by ID | | **Get blog category** `cloudcart_get_blog_category` | Retrieve details of a specific blog category by ID | | **Get blog post** `cloudcart_get_blog_post` | Retrieve a single blog post by its ID | | **Get blog tag** `cloudcart_get_blog_tag` | Retrieve details of a specific blog tag by ID | | **Get cart** `cloudcart_get_cart` | Retrieve the current shopping cart | | **Get categories** `cloudcart_get_categories` | Retrieve a list of all categories | | **Get categories properties** `cloudcart_get_categories_properties` | Retrieve properties relationship for a category | | **Get category** `cloudcart_get_category` | Retrieve details of a specific category by ID | | **Get customer** `cloudcart_get_customer` | Retrieve details of a specific customer by ID | | **Get customer billing address** `cloudcart_get_customer_billing_address` | Retrieve a specific customer billing address by its ID | | **Get customer group** `cloudcart_get_customer_group` | Retrieve details of a specific customer group by ID | | **Get customer groups customers** `cloudcart_get_customer_groups_customers` | Retrieve customers from a specific customer group | | **Get customer shipping address** `cloudcart_get_customer_shipping_address` | Retrieve a single customer shipping address by ID | | **Get customer tag** `cloudcart_get_customer_tag` | Retrieve details of a specific customer tag | | **Get customers** `cloudcart_get_customers` | Retrieve a list of all customers | | **Get image** `cloudcart_get_image` | Retrieve details of a specific image by ID | | **Get orders** `cloudcart_get_orders` | Retrieve a paginated list of orders from your CloudCart store | | **Get payment methods** `cloudcart_get_payment_methods` | Retrieve all available payment methods | | **Get product with relations** `cloudcart_get_product_with_relations` | Retrieves detailed information about a specific product including its relationships (category | | **Get products** `cloudcart_get_products` | Retrieve a list of products with optional filters | | **Get products linked product** `cloudcart_get_products_linked_product` | Retrieve linked products for a specific product | | **Get products linked products** `cloudcart_get_products_linked_products` | Retrieve linked products for a specific product | | **Get property** `cloudcart_get_property` | Retrieve details of a specific property by ID | | **Get property option** `cloudcart_get_property_option` | Retrieve details of a specific property option by ID | | **Get property options relationship** `cloudcart_get_property_options_relationship` | Retrieve property options relationship for a product | | **Get shipping methods** `cloudcart_get_shipping_methods` | Retrieve all available shipping methods | ## Example prompts **Add Category Properties** > Use Cloudcart to add category properties and walk me through the result in plain English. **Add To Cart** > Use Cloudcart to add to cart and walk me through the result in plain English. **Clear Cart** > Use Cloudcart to clear cart and walk me through the result in plain English. **Create Blog Category** > Create it in Cloudcart for me, then confirm the important fields before you finish. ## 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 Cloudcart working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Cloudcart API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Cloudcart 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 Cloudcart. | 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 Cloudcart actions to the runtime in a format your agent can reliably use. | 150 tools for Cloudcart are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Cloudcart 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 Cloudcart in the browser, and the 150 tools above work from chat. There is no SDK and no config file, and the Cloudcart 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 Cloudcart 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 Cloudcart 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 Cloudcart tools Cloudcart 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 Cloudcart 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. ### Cloudcart 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 Cloudcart 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 Cloudcart integration? Yes. ClawLink is the fastest way to connect Hermes to Cloudcart: link your Cloudcart account once in the browser and Hermes Agent can call the Cloudcart API through 150 ready-made tools — no custom code or token handling. ### How do I connect Cloudcart 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 Cloudcart in the dashboard and Hermes can use it from the next message — no config files, and the Cloudcart key you paste is stored server-side instead of in your environment. ### How long does it take to connect Cloudcart to Hermes Agent? About two minutes. Sign in, click Connect next to Cloudcart in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Cloudcart 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 Cloudcart working from chat. ### Hermes paired but still can't use Cloudcart 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 - [Connect Baselinker](https://claw-link.dev/hermes/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. - [Shippo tools](https://claw-link.dev/hermes/shippo) — Generate shipping labels, track packages, and manage fulfillment - [Connect Zoho Inventory](https://claw-link.dev/hermes/zoho-inventory) — Manage stock levels, orders, warehouses, and fulfillment