Overview
Loyverse MCP Server is an open-source Model Context Protocol (MCP) server that connects Claude to a Loyverse point-of-sale account. It provides read and write access to the Loyverse catalogue, inventory, customers, receipts, and sales reports. The server can be installed as a one-click Claude Desktop extension or run from source in any MCP client. It is built against the published Loyverse API v1.0 reference, and every read tool has been run against a live Loyverse account.
The server includes twenty-six read tools and fifteen write tools across the documented API surface. It adds a loyverse_sales_summary tool that aggregates a date range into totals and a ranked breakdown by day, item, category, payment type, employee, or store in a single call. Other features include cursor pagination, automatic retry with backoff against the API rate limit, and errors translated into plain sentences.
For web and mobile use, a hosted server signs merchants in through Loyverse's own OAuth and issues its own tokens, which can be revoked by disconnecting the connector. It offers two scopes: loyverse:read (the 26 read tools) and loyverse:write (all 41 tools). Read is the default when a client asks for nothing, and a refresh can narrow scope but never widen it.
The server stores no data of its own. Tokens it issues are stored only as SHA-256 hashes, and Loyverse tokens it holds are encrypted with AES-256-GCM under a key that lives in the environment. Authorization codes are single use, and redeeming one twice revokes the entire grant.
Pricing
Free
Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.
Visit WebsitePrices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.
Use Cases
- Teams use Loyverse MCP Server to ask sales reporting questions in plain English, such as top-selling dishes or cash versus card takings.
- Teams use Loyverse MCP Server to check stock levels, for example identifying items with fewer than three in stock at a main store.
- Teams use Loyverse MCP Server to edit the catalogue, such as adding a new item and setting its opening stock.
- Teams use Loyverse MCP Server to reconcile shifts that closed more than a specified amount away from expected cash.
- Teams use Loyverse MCP Server to look up loyalty customers who have not visited in a given period.
Features
Connect Claude to Loyverse POS
Access POS item information
Work with inventory data
Access customer records
Retrieve receipt information
Generate sales reports in one call
Reviews
No reviews yet. Be the first to share your experience!
FAQ
Is this an official Loyverse integration?
No. It is an independent open-source project, not built, endorsed or supported by Loyverse.
Do I need a paid Loyverse plan?
No. The only paid feature that matters here is Unlimited Sales History, without which the API serves the last 31 days of receipts.
Which MCP clients does it work with?
Any MCP client, since it speaks MCP over stdio. It has been tested end to end in Claude Desktop as a .mcpb extension, and the from-source build has been driven directly over stdio. The desktop extension is the easiest route.
Is my sales data sent anywhere?
No. Requests go only to api.loyverse.com. The server has no database, no logging and no analytics.
Can it change or delete my data?
Yes. Fifteen of the forty-one tools write, and three of those are irreversible. They are annotated so your client can warn you, but treat the access token as full account access, because that is what Loyverse gives it.
Does it support more than one store?
Yes. Tools that make sense per store take a store_id, and the sales summary can group by store.
Does it support Loyverse OAuth instead of an access token?
Not yet. OAuth is needed for a hosted, multi-tenant deployment and is planned. The client is already written to take a token per session, so it is a transport change rather than a rewrite.