Use your own AI assistant with Qruuk
Claude, ChatGPT and other assistants can work in your Qruuk account for you: set up a loyalty program, print the QR code, connect your till, look up a customer or tell you how last month went. You decide what each assistant may do, and anything that costs money waits for your approval.
Connect it
Every assistant uses the same address:
https://api.qruuk.com/mcp- Claude
- Settings → Connectors → Add custom connector. Paste the address, then sign in to Qruuk and choose what Claude may do.
- ChatGPT
- Settings → Apps & Connectors → turn on developer mode, then create a connector with the address and sign in.
- Claude Code
claude mcp add --transport http qruuk https://api.qruuk.com/mcp, then follow the sign-in link.- Cursor, VS Code, n8n
- Add a remote MCP server with the address. They open Qruuk for you to sign in and allow access.
- Your own script
- Create an API key in Qruuk → Settings → API keys with only the permissions it needs, and send it as
Authorization: Bearer ….
Qruuk is listed in the official MCP Registry as com.qruuk/qruuk, so some apps find it by name.
Choose what it may do
When you connect, Qruuk shows every permission the assistant asks for. Untick anything it doesn't need; you can connect again later with more.
| You want it to… | Tick |
|---|---|
| Set up and tidy your programs, packages and extras | See your account · Set up and change your account |
| Plan your class schedule: weekly classes, one-offs, cancellations | See your account · Set up and change your account |
| See who's booked and who came to a class | See your account · See customers (for names) |
| Connect your till (Erply, Loyverse) or Zapier, Make, n8n | See your account · Manage integrations |
| Create webhooks that send events to another system | Manage integrations · Receive events |
| Look up customers, find who hasn't been back | See customers |
| Add customers or record that they opted in | Add and update customers |
| Work the counter: issue cards, add stamps | Issue cards · Validate cards |
| Fix a card issued by mistake (void it, or undo a void) | Issue cards |
Without See customers, the assistant still sees sales totals and activity, but not customers' names, emails or card codes. A stamp means a customer was served, so most shops leave validating cards to their staff.
What waits for you
An assistant never spends your money. Changing your plan, installing a paid add-on and setting up online card payments are requests: you get an email titled "Approve? …" and a banner in Qruuk, and nothing happens until the account owner presses Approve. Requests expire after 7 days, and one you decline can't be asked again for a day.
Each connected assistant can issue at most 200 cards, email 100 and void 50 a day; issued cards count toward your plan like any other. Voiding a card doesn't refund it, and a void can be undone.
Try asking
- "Set up a stamp card for my bakery: 8 coffees, the 9th free. Give me the QR code to print."
- "Connect my Loyverse till so purchases stamp cards automatically."
- "Who were my most loyal customers last month, and who hasn't been back in 60 days?"
- "Add a 10-class pass for €90 that people can buy at the counter."
- "What changed in my account this week, and who did it?"
- "I issued card K7Q2M9XZ to the wrong email. Void it and issue a new one to anna@example.com."
Stay in control
- See everything. Qruuk → Settings → AI agents & connected apps lists each assistant, what it may do and what it changed recently. Changes, refusals and customer look-ups are kept in your activity log.
- Disconnect any time. Its access ends at once, along with any API keys and webhooks it created.
- Lost a password or a laptop? "Sign out everywhere", or resetting your password, disconnects every assistant you connected too.
- Connections expire. After 90 days the assistant asks you to sign in again.
- Don't recognise an app? Don't approve its requests. App names are chosen by the app; Qruuk refuses names that imitate Qruuk or the big assistants, but only allow a connection you started yourself.
- Your assistant's provider. Whatever the assistant reads is processed by the company that runs it (Anthropic, OpenAI…) under their terms. Qruuk sends only what you allowed.
For developers
Remote MCP server (Streamable HTTP) with OAuth 2.1: discovery at /.well-known/oauth-protected-resource/mcp, dynamic client registration, PKCE S256. Inside, the resources qruuk://docs/agent-guide, qruuk://docs/open-api and qruuk://docs/webhooks describe the tools, the REST API and webhook signatures. A summary for machines is at /llms.txt.