# Connect Loyverse to Muse Prepare a grounded POS sales briefing

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

- Page: https://www.agent200.com/connectors/loyverse/framework/muse/
- Connector: [Loyverse](https://www.agent200.com/connectors/loyverse.md)
- Framework: Muse
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect Loyverse to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/loyverse/framework/muse/

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 Muse'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 Muse: 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 Muse'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.

## Overview

Use Muse to prepare a short POS sales briefing for review. Put the Agent200 key in Muse’s secure credential interface, then inspect the source before sharing the result.

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](https://developer.loyverse.com/docs/).

- **Connector:** [Loyverse](https://www.agent200.com/connectors/loyverse/)
- **Works with:** Muse · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [5 tools](https://www.agent200.com/connectors/loyverse/framework/muse/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) 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.
- **Muse, with custom MCP servers allowed.** Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

## Connect Loyverse to Muse

### Step 1: Create your Agent200 API key

Create a key on the [API keys page](https://agent200.com/platform/apikeys/) and store it securely.

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Create the custom connector

Connect to `https://api.agent200.com/mcp/` over Streamable HTTP with an Authorization: Bearer header. Enter the key in Muse’s secure credential interface.

File `Muse chat`:

```text
Create a Custom Connector for the Agent200 remote MCP server and connect to it:
Name: Agent200
Transport: remote streamable HTTP
URL: https://api.agent200.com/mcp/
Auth: API key sent in the Authorization header as "Bearer <key>"
Open the secure credentials store so I can enter the API key there, not in this chat.
Then list its tools to confirm the connection works.
```

### Step 3: Inspect read tools

Confirm the Loyverse operations and schemas advertised by the connection.

### Step 4: Authorize Loyverse

Connect the intended user and test one accessible receipt.

## Test your connection

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.

## Loyverse tools Muse can call

- **List receipts** (`loyverse_list_receipts`, read): Find receipts in a selected store and time window.
- **Read a receipt** (`loyverse_get_receipt`, read): Retrieve one receipt by ID.
- **List items** (`loyverse_list_items`, read): Find catalog items available to the connection.
- **Read an item** (`loyverse_get_item`, read): Retrieve one identified catalog item.
- **List customers** (`loyverse_list_customers`, read): Find customer records in authorized scope.

## How it works

1. **You ask Muse.** In your own words, for something in Loyverse.
2. **Muse picks a tool.** It sees the Loyverse tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own Loyverse connection, within the tools and scopes your project allows.
4. **Muse 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

- [Loyverse + Claude](https://www.agent200.com/connectors/loyverse/framework/claude.md)
- [Loyverse + ChatGPT](https://www.agent200.com/connectors/loyverse/framework/chatgpt.md)
- [Loyverse + Claude Code](https://www.agent200.com/connectors/loyverse/framework/claude-code.md)
- [Loyverse + Grok Bot](https://www.agent200.com/connectors/loyverse/framework/grok-bot.md)
- [Loyverse + OpenAI Dots](https://www.agent200.com/connectors/loyverse/framework/openai-dots.md)
- [Loyverse + Claude Duet](https://www.agent200.com/connectors/loyverse/framework/claude-duet.md)
- [Loyverse + Hermes Agent](https://www.agent200.com/connectors/loyverse/framework/hermes-agent.md)
- [Loyverse + OpenClaw](https://www.agent200.com/connectors/loyverse/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
