Loyverse + OpenClaw

Connect Loyverse to OpenClaw Prepare a grounded POS sales briefing

Read receipts with OpenClaw and Agent200. Prepare a POS sales briefing using the connected user’s own Loyverse account.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Loyverse tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Save the Agent200 server settings in OpenClaw, inspect tool discovery, then read one receipt the user can access. A saved setting alone does not verify the read.

Start with one identified receipt. Preserve returned receipt, item, customer and amount fields; report missing data and keep the workflow read-only.

Provider reference: Loyverse API.

Connector
Loyverse
Works with
OpenClaw · Agent app, through MCP
Authentication
Managed OAuth, per end user
Tools
5 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Loyverse enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • An end user with a Loyverse account. They approve access once, on Loyverse's own page.
  • OpenClaw, with custom MCP servers allowed. OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.

Connect Loyverse to OpenClaw

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page and store it securely.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Store your key in ~/.openclaw/.env

    OpenClaw fills ${AGENT200_API_KEY} in its config from ~/.openclaw/.env, so the key never sits in the config itself.

    ~/.openclaw/.env
    MCP: OpenClaw key in ~/.openclaw/.env
    AGENT200_API_KEY=your-agent200-api-key
  3. 3

    Step 3: Save the server

    openclaw mcp set takes one JSON object. Always set the transport to streamable-http: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves ${AGENT200_API_KEY} for OpenClaw. In the Control UI, add it under Settings > MCP, then put the header in the config editor on the same page.

    Stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while it is running.

    Terminal
    MCP: OpenClaw save the server from the CLI
    openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}'
  4. 4

    Step 4: Probe the server

    Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.

    Terminal
    MCP: OpenClaw probe the server
    openclaw mcp doctor agent200 --probe
    openclaw mcp status --verbose
  5. 5

    Step 5: Authorize Loyverse

    Connect the intended user and test one accessible receipt.

Test your connection

Run one request to check everything is wired up.

Ask

Read the Loyverse receipt I identify and prepare a POS sales briefing. Name the source and use only receipt, item, customer and amount fields. State access gaps; do not change records.

What should come back

  • The selected receipt is identified.
  • Only the returned receipt, item, customer and amount fields are reported.
  • Access gaps and missing context are explicit; no source data is changed.

Check the selected receipt ID, account scope, read permission and pagination. Receipt totals and customer records are sensitive. Account for refunds, store scope and pagination; do not treat receipts as settled payouts.

Get your API key

Create a key in the Agent200 dashboard. It reaches Loyverse and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Loyverse to OpenClaw.

Agent brief
Goal: connect Loyverse to OpenClaw with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/loyverse/framework/openclaw/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into OpenClaw's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Loyverse is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to OpenClaw: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for OpenClaw's exact menus or commands.
4. The first Loyverse request returns an authorization link if the user has not connected Loyverse yet: show it to them and continue once they have approved access on Loyverse's own page.
5. Check it works with this request: "Read the Loyverse receipt I identify and prepare a POS sales briefing. Name the source and use only receipt, item, customer and amount fields. State access gaps; do not change records."
   What should come back:
   - The selected receipt is identified.
   - Only the returned receipt, item, customer and amount fields are reported.
   - Access gaps and missing context are explicit; no source data is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Loyverse, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/loyverse/framework/openclaw.md

Loyverse tools OpenClaw can call

  • List receipts

    Read
    loyverse_list_receipts

    Find receipts in a selected store and time window.

  • Read a receipt

    Read
    loyverse_get_receipt

    Retrieve one receipt by ID.

  • List items

    Read
    loyverse_list_items

    Find catalog items available to the connection.

  • Read an item

    Read
    loyverse_get_item

    Retrieve one identified catalog item.

  • List customers

    Read
    loyverse_list_customers

    Find customer records in authorized scope.

How it works

  1. 01

    You ask OpenClaw

    In your own words, for something in Loyverse.

  2. 02

    OpenClaw picks a tool

    It sees the Loyverse tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    With your own Loyverse connection, within the tools and scopes your project allows.

  4. 04

    OpenClaw answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Loyverse account.

Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Loyverse enforces what its API grants.

Troubleshooting

The source cannot be read

Check the selected receipt ID, account scope, read permission and pagination. Receipt totals and customer records are sensitive. Account for refunds, store scope and pagination; do not treat receipts as settled payouts.

FAQ

How do I verify this result?

Compare the named receipt and returned receipt, item, customer and amount fields with the source. Treat missing information as missing, not as a fact.

Use Loyverse with another framework

200 OK

Loyverse, connected to OpenClaw.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)