# How to connect MerchantPro to OpenClaw (paste one key, 10 tools) > Connect MerchantPro to OpenClaw with ClawLink: paste your MerchantPro key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/merchantpro The usual route to MerchantPro 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 MerchantPro setup: install one ClawHub skill, connect MerchantPro in the browser, and OpenClaw can call real MerchantPro 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 MerchantPro. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect MerchantPro** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 merchantpro # connect MerchantPro (browser OAuth) npx -y @useclawlink/cli actions merchantpro # list available actions npx -y @useclawlink/cli run merchantpro --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 MerchantPro in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your MerchantPro API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from MerchantPro, 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: ```bash 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## MerchantPro MCP for OpenClaw Looking for a MerchantPro MCP server for OpenClaw? ClawLink connects MerchantPro to OpenClaw and exposes 10 MerchantPro 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 Hermes instead? The [Hermes MerchantPro integration](https://claw-link.dev/hermes/merchantpro) works the same way. ## What the OpenClaw MerchantPro integration can do 10 MerchantPro tools are ready for OpenClaw once the account is connected. ### All 10 MerchantPro tools for OpenClaw | Tool | What it does | |---|---| | **Get inventory** `merchantpro_get_inventory` | Return inventory and price information for one MerchantPro inventory unit | | **Get product** `merchantpro_get_product` | Return details for one MerchantPro product, including variant IDs when the product has variants | | **Get shop taxonomy** `merchantpro_get_shop_taxonomy` | Return the shop's currencies, languages, payment methods, or warehouses for interpreting | | **List catalog partners** `merchantpro_list_catalog_partners` | List brands or suppliers used by the product catalog; choose one resource type per call | | **List categories** `merchantpro_list_categories` | Find product categories by ID, name, parent, type, or status for catalog navigation and product | | **List customer subscriptions** `merchantpro_list_customer_subscriptions` | List recurring product subscriptions by customer, status, recurrence, type, or renewal date | | **List customers** `merchantpro_list_customers` | Find customers by identity, group, status, registration, newsletter, or location filters | | **List locations** `merchantpro_list_locations` | List countries, states, or cities for address and customer workflows; state and city searches | | **List orders** `merchantpro_list_orders` | Find shop orders by customer, payment, shipping, product, or modification filters without | | **List products** `merchantpro_list_products` | Find products and variants in the shop catalog using common identity, category, brand, stock | ## Example prompts **Get Inventory** > Pull the relevant data from MerchantPro, summarize it in plain English, and point out anything that needs attention. **Get Product** > Pull the relevant data from MerchantPro, summarize it in plain English, and point out anything that needs attention. **Get Shop Taxonomy** > Pull the relevant data from MerchantPro, summarize it in plain English, and point out anything that needs attention. **List Catalog Partners** > List the relevant items in MerchantPro, 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 MerchantPro working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, 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 maintenance** | You 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 usability** | You 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. | ## ClawLink vs. Composio 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 OpenClaw 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the MerchantPro skill but can't call the tools The ClawHub skill teaches OpenClaw about MerchantPro, but the calls run through the ClawLink plugin and your connected account. Make sure MerchantPro 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 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. ### Is there a OpenClaw MerchantPro integration? Yes. ClawLink is the fastest way to connect OpenClaw to MerchantPro: link your MerchantPro account once in the browser and OpenClaw can call the MerchantPro API through 10 ready-made tools — no custom code or token handling. ### How do I add MerchantPro to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink MerchantPro skill from ClawHub, then you click Connect in the dashboard to authorize MerchantPro. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to MerchantPro in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want MerchantPro working from chat. ### OpenClaw installed the MerchantPro skill but can't call the tools The ClawHub skill teaches OpenClaw about MerchantPro, but the calls run through the ClawLink plugin and your connected account. Make sure MerchantPro 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. ## Related - [Cloudcart](https://claw-link.dev/openclaw/cloudcart) — CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently. - [OpenClaw Wix integration](https://claw-link.dev/openclaw/wix) — Manage sites, products, orders, and bookings - [Baselinker](https://claw-link.dev/openclaw/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.