# How to connect Loyverse to OpenClaw (paste one key, 58 tools) > Connect Loyverse to OpenClaw with ClawLink: paste your Loyverse key once and 58 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/loyverse The usual route to Loyverse 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 Loyverse setup: install one ClawHub skill, connect Loyverse in the browser, and OpenClaw can call real Loyverse 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 Loyverse. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Loyverse** — 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 loyverse # connect Loyverse (browser OAuth) npx -y @useclawlink/cli actions loyverse # list available actions npx -y @useclawlink/cli run loyverse --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 Loyverse in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Loyverse API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Loyverse, 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 Loyverse is connected in the dashboard, that agent calls the same 58 Loyverse 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). ## Loyverse MCP for OpenClaw Looking for a Loyverse MCP server for OpenClaw? ClawLink connects Loyverse to OpenClaw and exposes 58 Loyverse 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 Loyverse integration](https://claw-link.dev/hermes/loyverse) works the same way. ## What the OpenClaw Loyverse integration can do 58 Loyverse tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 58. ### 30 of 58 Loyverse tools for OpenClaw | Tool | What it does | |---|---| | **Get category** `loyverse_get_category` | Get a single category by ID | | **Get customer** `loyverse_get_customer` | Get a single customer by their ID | | **Get discount** `loyverse_get_discount` | Get a single discount by ID | | **Get employee** `loyverse_get_employee` | Get a single employee by ID | | **Get item** `loyverse_get_item` | Get a single item by ID including all its variants | | **Get jwks** `loyverse_get_jwks` | Fetch JSON Web Key Set for OpenID Connect | | **Get merchant info** `loyverse_get_merchant_info` | Get merchant information | | **Get modifier** `loyverse_get_modifier` | Get a single modifier by ID | | **Get open ID configuration** `loyverse_get_open_id_configuration` | Retrieve the OpenID Connect discovery document | | **Get payment type** `loyverse_get_payment_type` | Get a single payment type by its ID | | **Get pos device** `loyverse_get_pos_device` | Retrieve details of a specific POS device by its ID | | **Get receipt** `loyverse_get_receipt` | Retrieve a single receipt by its receipt number | | **Get store** `loyverse_get_store` | Retrieve details of a specific store by its ID | | **Get supplier** `loyverse_get_supplier` | Get a single supplier by their ID | | **Get tax** `loyverse_get_tax` | Get a single tax by ID | | **Get variant** `loyverse_get_variant` | Get a single item variant by its ID | | **Get webhook** `loyverse_get_webhook` | Get a single webhook by its ID | | **List categories** `loyverse_list_categories` | List categories with optional filtering and pagination | | **List customers** `loyverse_list_customers` | Get a list of customers | | **List discounts** `loyverse_list_discounts` | List discounts | | **List employees2** `loyverse_list_employees2` | Get a list of employees with advanced filtering options | | **List inventory** `loyverse_list_inventory` | Retrieves inventory levels for item variants across stores in the Loyverse system | | **List items** `loyverse_list_items` | Retrieves a paginated list of items (products) from the Loyverse inventory | | **List modifiers2** `loyverse_list_modifiers2` | Get a list of modifiers sorted by created_at in descending order | | **List payment types** `loyverse_list_payment_types` | List payment types | | **List pos devices** `loyverse_list_pos_devices` | Get a list of POS devices sorted by creation date in descending order | | **List receipts** `loyverse_list_receipts` | Retrieve a list of receipts | | **List shifts** `loyverse_list_shifts` | List shifts | | **List stores** `loyverse_list_stores` | Get a list of stores sorted by creation date (newest first) | | **List suppliers** `loyverse_list_suppliers` | Retrieve a list of suppliers | ## Example prompts **Get Category** > Pull the relevant data from Loyverse, summarize it in plain English, and point out anything that needs attention. **Get Customer** > Pull the relevant data from Loyverse, summarize it in plain English, and point out anything that needs attention. **Get Discount** > Pull the relevant data from Loyverse, summarize it in plain English, and point out anything that needs attention. **Get Employee** > Pull the relevant data from Loyverse, 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 Loyverse working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Loyverse API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Loyverse 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 Loyverse. | 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 Loyverse actions to the runtime in a format your agent can reliably use. | 58 tools for Loyverse are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Loyverse 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 Loyverse in the browser, and the 58 tools above work from chat. There is no SDK and no config file, and the Loyverse 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 Loyverse skill but can't call the tools The ClawHub skill teaches OpenClaw about Loyverse, but the calls run through the ClawLink plugin and your connected account. Make sure Loyverse 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 Loyverse 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 Loyverse tools Loyverse 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 Loyverse 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. ### Loyverse 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 Loyverse has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Loyverse integration? Yes. ClawLink is the fastest way to connect OpenClaw to Loyverse: link your Loyverse account once in the browser and OpenClaw can call the Loyverse API through 58 ready-made tools — no custom code or token handling. ### How do I add Loyverse to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Loyverse skill from ClawHub, then you click Connect in the dashboard to authorize Loyverse. OpenClaw calls the tools from the next message — no config files, and the Loyverse key you paste is stored server-side instead of in your environment. ### How long does it take to connect Loyverse to OpenClaw? About two minutes. Sign in, click Connect next to Loyverse in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Loyverse 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 Loyverse working from chat. ### OpenClaw installed the Loyverse skill but can't call the tools The ClawHub skill teaches OpenClaw about Loyverse, but the calls run through the ClawLink plugin and your connected account. Make sure Loyverse 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 - [OpenClaw Cloudcart integration](https://claw-link.dev/openclaw/cloudcart) — CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently. - [Wix](https://claw-link.dev/openclaw/wix) — Manage sites, products, orders, and bookings - [OpenClaw Baselinker integration](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.