Skip to content

AI connector (MCP)

Connect Claude, ChatGPT or another AI assistant to BokaPOS. The assistant reads the documentation without signing in, and with the approval of the Owner or an Administrator it works with your organization's data, in the sandbox or in production, only as far as you allow.

Updated: 31 October 2026 · Contract version 1.0.0

Addresses

AddressSign-inWhat the assistant gets
https://mcp.bokapos.rs/mcpBokaPOS account; the Owner or an Administrator approves the connectionthe documentation and work with the organization's data, per the connection's permissions
https://mcp.bokapos.rs/docsnonethe documentation only: guide, operations, schemas and errors

Connecting

  1. Add the connector

    In the AI app, add a custom MCP connector with the address https://mcp.bokapos.rs/mcp. In Claude Code one command is enough: claude mcp add --transport http --scope user bokapos https://mcp.bokapos.rs/mcp (--scope user adds the connector to all your projects).

  2. Sign in

    The app opens the BokaPOS sign-in; in Claude Code you open it yourself: type /mcp, pick bokapos and choose Authenticate. Sign in with the account you use for cloud.bokapos.rs; if you are already signed in to the portal, the password is not asked again. Enter your password only on the BokaPOS page, never in the AI app.

  3. Approve the connection

    The BokaPOS approval page shows which app is asking and where it returns to, and you choose the environment (sandbox or production), the permissions and the connection name. Only the organization's Owner and Administrators can approve; an Operator or Viewer is asked to contact them. Production with any write permission also needs an explicit confirmation that the AI app issues real fiscal receipts.

  4. Work and manage

    From then on the assistant sees the tools its permissions cover. You change or remove each connection in the portal, under AI connections.

Supported AI apps

  • Claude: web (claude.ai), desktop and mobile apps, and Claude Code.
  • ChatGPT (custom connector).
  • Cursor: desktop and web.
  • Visual Studio Code with GitHub Copilot.
  • Gemini CLI and Perplexity.

Apps running on your own computer (a local address, for example Claude Code or Cursor) always work. Web apps sign in only through the callback addresses their vendors officially publish, so a fake app on another website cannot get access. We add another web app on request.

Permissions

Each connection has one environment and its own permissions. Reading is always on, and you choose writing per connection. A connection can never do more than an integration API credential and never sees secrets.

Defaults at approval. The Owner or an Administrator changes them before approving and later in the portal.
PermissionWhat it coversSandboxProduction
Read (always)journal, receipts, reports, catalogue, tax rates, taxpayers, premises, security elements, licenceonon
Issue and e-mail receiptssale, copy, sending the receipt to the customeronoff
Refundsrefunding a saleonoff
Advancesopening, payment, payment cancellation, closingonoff
Proforma and trainingproforma and training documentsonoff
Catalogue changesadding, changing and importing productsonoff

A permission change and a removal take effect within a minute. Receipts the connection already issued stay in the journal.

Tools

Tool names are in English and start with bokapos_. The assistant sees only the tools the connection's permissions cover; the /docs address offers only the first group.

GroupTools
Documentationbokapos_search_docs, bokapos_read_docs, bokapos_list_operations, bokapos_get_operation, bokapos_get_schema, bokapos_get_error
Setup and licencebokapos_get_runtime, bokapos_get_license, bokapos_list_taxpayers, bokapos_get_taxpayer, bokapos_list_business_premises, bokapos_get_business_premise, bokapos_list_tax_rates, bokapos_list_security_elements, bokapos_get_security_element
Journal and receiptsbokapos_search_journal, bokapos_get_fiscal_document, bokapos_export_journal, bokapos_get_receipt, bokapos_get_turnover_report, bokapos_export_turnover_report, bokapos_get_operation_status, bokapos_list_receipt_deliveries, bokapos_get_receipt_delivery
Issuingbokapos_issue_sale, bokapos_issue_copy, bokapos_send_receipt_email
Refundsbokapos_create_refund
Advancesbokapos_list_advance_cases, bokapos_get_advance_case, bokapos_create_advance_case, bokapos_add_advance_payment, bokapos_cancel_advance_payment, bokapos_close_advance_case
Proforma and trainingbokapos_issue_proforma_or_training, bokapos_get_proforma_training
Cataloguebokapos_list_products, bokapos_get_product, bokapos_export_products, bokapos_create_product, bokapos_update_product, bokapos_import_products

Rules for fiscal documents

  • Every answer names the environment: in the sandbox these are test documents on the Tax Administration's test system, in production real fiscal receipts.
  • A receipt exists only when the tool returns the signed V-PFR response (fiscalized: true). An accepted request, an error or a sent e-mail is not a receipt.
  • Issuing tools require an idempotencyKey. The same key after an interruption returns the same document, never a new one.
  • OUTCOME_UNKNOWN and a 503 with retryable: false are never repeated; the tool points to bokapos_get_operation_status with the operation id.
  • Before issuing in production the assistant confirms the document with you first.
  • The connector does not change security elements, team members or organization settings.

Security and price

  • The AI app's token is valid only at the connector and never reaches the BokaPOS API. Each connection has its own short-lived API access bound to the organization and environment, so the API checks the same rights as for any integration.
  • Everything the assistant does is recorded in the same journal and activity log as an integration's work.
  • The connector is not charged separately. Documents a connection issues count like all others, per the price list.
  • Using an AI connection is optional. Everything the AI app does through a connection counts as your organization's action, and the AI app is provided by its vendor under its own terms. The rules are in article 9a of the Terms of Use, which you accept by approving a connection.

If you write the integration yourself with an AI assistant, the prompt and the documentation as text are on the Getting started page.