ClawLink

How to connect MerchantPro to Hermes Agent

Connect MerchantPro to Hermes with ClawLink: paste your MerchantPro key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
MerchantPro
MerchantPro
MerchantProAPI KEYMCP

MerchantPro is an eCommerce platform for managing storefront catalogs, customers, orders, inventory, content, and related commerce operations.. Once connected, Hermes Agent can read and act on MerchantPro from chat — pairing, token refresh, and tool wiring handled for you.

10 tools

Most guides for giving Hermes Agent MerchantPro 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 MerchantPro setup: pair once in the browser and your always-on Hermes agent can act on MerchantPro 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 MerchantPro.

  1. 1

    Install and pair

    Install the ClawLink plugin, then pair Hermes with a one-time browser approval:

    hermes plugins install ClawLink-HQ/hermes-plugin --enable
  2. 2

    Connect MerchantPro

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with MerchantPro?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

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 MerchantPro in the ClawLink dashboard — paste your MerchantPro API key once.

Verify the connection by asking Hermes:

Pull the relevant data from MerchantPro, 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:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once MerchantPro is connected in the dashboard, that agent calls the same 10 MerchantPro tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

MerchantPro MCP for Hermes

Looking for a MerchantPro MCP server for Hermes Agent? ClawLink connects MerchantPro to Hermes Agent and exposes 10 MerchantPro tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw MerchantPro integration works the same way.

What the Hermes Agent MerchantPro integration can do

10 MerchantPro tools are ready for Hermes Agent once the account is connected.

All 10 MerchantPro tools for Hermes

ToolWhat it does
Get inventory merchantpro_get_inventoryReturn inventory and price information for one MerchantPro inventory unit
Get product merchantpro_get_productReturn details for one MerchantPro product, including variant IDs when the product has variants
Get shop taxonomy merchantpro_get_shop_taxonomyReturn the shop's currencies, languages, payment methods, or warehouses for interpreting
List catalog partners merchantpro_list_catalog_partnersList brands or suppliers used by the product catalog; choose one resource type per call
List categories merchantpro_list_categoriesFind product categories by ID, name, parent, type, or status for catalog navigation and product
List customer subscriptions merchantpro_list_customer_subscriptionsList recurring product subscriptions by customer, status, recurrence, type, or renewal date
List customers merchantpro_list_customersFind customers by identity, group, status, registration, newsletter, or location filters
List locations merchantpro_list_locationsList countries, states, or cities for address and customer workflows; state and city searches
List orders merchantpro_list_ordersFind shop orders by customer, payment, shipping, product, or modification filters without
List products merchantpro_list_productsFind products and variants in the shop catalog using common identity, category, brand, stock

Try it: find the MerchantPro tool you need

Browse the 10 MerchantPro tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

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

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

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

List the relevant items in MerchantPro, group them by priority, and recommend what Hermes should do next.

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

ManualClawLink
Credential handlingCollect, validate, store, and rotate the MerchantPro API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected MerchantPro account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for MerchantPro.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right MerchantPro actions to the runtime in a format your agent can reliably use.10 tools for MerchantPro are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes MerchantPro 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 MerchantPro in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the MerchantPro 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

Hermes paired but still can't use MerchantPro

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 MerchantPro 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 MerchantPro tools

MerchantPro 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 MerchantPro 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.

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

FAQ

Is there a Hermes Agent MerchantPro integration?

Yes. ClawLink is the fastest way to connect Hermes to MerchantPro: link your MerchantPro account once in the browser and Hermes Agent can call the MerchantPro API through 10 ready-made tools — no custom code or token handling.

How do I connect MerchantPro 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 MerchantPro in the dashboard and Hermes can use it from the next message — no config files, and the MerchantPro key you paste is stored server-side instead of in your environment.

How long does it take to connect MerchantPro to Hermes Agent?

About two minutes. Sign in, click Connect next to MerchantPro in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring MerchantPro 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 MerchantPro working from chat.

Hermes paired but still can't use MerchantPro

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.