Connect an assistant app to Kluvan

The workspace owner must first enable global AI consent in Settings AI. This is separate from enabling assistant access and selecting key scopes. Global opt-out blocks external assistant requests too; revoking a key does not recall information already supplied.

If you use an assistant app that speaks MCP (the Model Context Protocol), such as Claude, ChatGPT or another MCP client, you can let it read your Kluvan figures and ask it things like "how were sales this week?" or "what is running low?". The assistant app is yours: you pay its maker, and Kluvan charges nothing per question. It can only read.

Before you start

• Only the owner can switch this on and make keys.
• This connection is new. It follows the MCP standard but has not yet been tried with every assistant app. If yours does not connect, write to support.
• The Claude desktop app needs Node.js installed on that computer.

Steps

1. Open Settings and the assistant access page (its address ends in /settings/ai).
2. Tick the switch that allows access, and the sentence under it, then press Save.
3. Under New key, type a Name you will recognise, for example "My ChatGPT".
4. Tick what this key may see: Reports, Stock, Products, Customers, Bookings, Team, or the records of an app such as Services & Maintenance or Rentals. Untick anything it does not need.
5. If you want, pick Only this branch and a Last day (optional).
6. Press Make the key, then Copy. The key is shown only this once.
7. Open the card for your assistant app (Claude desktop app, Claude on the web (claude.ai), ChatGPT or Any other MCP client). It is already filled with your address and the new key.
8. Follow the card's steps in your assistant app, paste what the card shows, and save.
9. In your assistant app, ask a first question, for example "Using my Kluvan tools, what is running low?".

What each tick allows

• Reports: sales figures, comparisons and best sellers. Stock: quantities, low stock, expiry dates. Products: names, prices, barcodes.
• Customers: names, phones and what they owe. This is personal data, so it is off by default. Without it, a customer shows as hidden.
• Bookings and Team work only when those apps are on.
• App records (Services & Maintenance, Customer Support, Forms, Automations, Production & Assembly, Rentals, Analytics, Trade & Wholesale) also need the Customers tick, because records can hold personal data, and the app must be switched on.

Good to know

• Read-only: no assistant app can sell, refund, take a payment, change a setting or delete anything through this connection.
• Limits per key: 60 calls a minute and 2,000 a day. A list stops at 50 records; the app is told to ask a narrower question. You can hold up to 10 keys.
• Abuse protection: a key that asks 20 times within an hour for something its ticks do not allow is Paused. Every call is refused, the owner gets an alert (when owner alerts are on), and the event is in Team → Activity. Check what the app was asked, then Resume or Revoke the key.
• The address with your key in it is the key. Never paste it anywhere public. Revoke stops it at once; a key also stops on its last day, or when the owner who made it is no longer active.
• Keys cannot be widened. To allow more, make a new key and revoke the old one.
• The activity list at the foot of the page shows the last 50 calls: when, which key, what was asked for, how many rows, and whether it was answered or refused. The questions themselves are not kept.
• Switching access off refuses every key until you switch it on again.
• For your own software that also writes records, use the developer API.