FAQ — Versino AI SAP B1 MCP

1. Download the current binary from the download repository — Windows (.exe) or Linux (64-bit).
2. Place your licence file versino.key in the same folder (it is found automatically next to the binary — no path needed).
3. Create a .env with SAP_BASE_URL, SAP_DATABASES and SAP_AUTH_MODE and start the server.

Step-by-step guides for Windows and Linux (incl. Windows service) are in the download repository under docs/.

• 64-bit Windows 10/11 / Server 2019+ or 64-bit Linux (glibc, x86-64).
• Network access to your SAP B1 Service Layer (https://<host>:50000/b1s/v2/).
• A valid versino.key (edition BASIC/PRO/ENTERPRISE).
• For stdio-only clients: Node.js (for the mcp-remote bridge).

The server speaks streamable HTTP at http://<host>:8000/mcp.

• Streamable-HTTP-capable clients (Claude Desktop “Custom Connector”, Cline, Continue, Cursor …): point directly at the /mcp URL.
• Stdio-only clients or plain http://: bridge npx mcp-remote http://<host>:8000/mcp.

An upstream reverse proxy with TLS is recommended for network operation.

Can: read master data (business partners, items, price lists, warehouses, employees, currencies …) incl. fuzzy search.

Cannot: read transactional data (invoices, orders, deliveries, postings), joins via $expand, the vetted AI_* SQL reports — and no writing. Capped at 60 queries/hour and 50 rows per query.

If you need “read a lot, write nothing”, PRO is usually the right choice (full read scope) — otherwise talk to us.

• BASIC — looking up master data at small scale.
• PRO — the usual choice: analyses across all data and creating/updating documents.
• ENTERPRISE — additionally deleting and document actions (e.g. closing an order) plus unlimited volumes.

Yes. The edition only sets the frame — in the end SAP Business One enforces the rights of the signed-in user 1:1. Additionally, the whole instance can be fully write-locked via SAP_OPERATION_MODE=READ_ONLY.

A signed offline licence file. After purchase you receive it by e-mail and via your customer portal. Place it next to the binary — it is detected automatically. Without a valid licence the server does not start.

A seat = a distinct SAP user who connects. Reconnecting the same user does not consume an additional seat; disconnecting releases it. Multiple instances of one company share the licence's seat count.

With an ongoing subscription the licence renews automatically. "Phone-home" is active by default, so the installation adopts the renewed key by itself — no manual key swap per billing period. If it is switched off, you receive a new versino.key in good time.

Yes. The licence check is offline (signed key). Phone-home never blocks on network problems — the delivered key stays valid until its expiry date.

No. The server runs self-hosted in your infrastructure; SAP data only flows between your SAP B1 and the LLM client. Phone-home transmits metadata only (customer number, edition, version, seat count) — no business data.

No. Every user signs in with their own SAP credentials; entry happens via a dialog or a web login — the credentials never reach the chat or LLM context.

Operation is self-hosted and designed to minimise data (no business-data outflow; phone-home carries metadata only). The data-protection assessment of your specific deployment is yours to make as the operator — we are happy to help.

Per seat and month via Stripe. Cancellable monthly. With the annual contract you save and the key is valid for 12 months. All prices plus VAT (B2B; VAT ID and billing address are collected at checkout).

Manage subscription takes you to the Stripe customer portal. Up-/downgrades and seat changes take effect on your licence automatically (it is re-signed). Cancellations there as well.