UOL Účetnictví (unofficial)

uol-mcp

Model Context Protocol server for UOL Účetnictví — ask Claude, Cursor or any other MCP client about your bookkeeping: issued and received invoices, who owes you money, uploaded documents, contacts.

Unofficial. Not affiliated with or endorsed by UOL a.s. It talks to the public

UOL REST API with your own API token.

Česky

Status: v0.6 — read-only by default, opt-in writes. What changed: CHANGELOG.md.

What it can do

Example questions: *"Jak si letos stojíme?"*, *"Kolik zaplatím DPH za tento kvartál?"*, *"Kdo mi dluží víc než 30 dní?"*, *"Je faktura 2026000123 zaplacená?"*, *"Na čem nejvíc utrácíme?"*, *"Stáhni mi PDF poslední vydané faktury."*

More read tools are available as opt-in toolsets (UOL_TOOLSETS): ledger (general-ledger postings, internal documents), banking (bank movements, petty-cash documents) and warehouse (products, stock levels, orders).

Ready-made prompts (slash commands in most clients): monthly_review, vat_check, overdue_followup (drafts reminders, sends nothing), process_inbox, and with write access issue_invoice (builds a sales invoice from your description, shows a dry run and creates a draft once you confirm). The uol://guide resource explains the domain to the model.

The uol-ucetnictvi skill goes further: Claude issues an invoice the way you always invoice that customer (DUZP rule, due days, products, line texts and bank account learned from your earlier invoices to them) and reads revenue, profit, VAT and receivables the way an accountant does (unbooked months, estimates, deadlines). Install it in Claude Desktop or claude.ai by zipping the skills/uol-ucetnictvi folder and uploading it under Settings → Capabilities → Skills, or in Claude Code by copying the folder to ~/.claude/skills/.

The server knows the API's quirks: invoice status valid means *draft*, payment status exists only for issued invoices, credit notes come with positive amounts, revenue and expenses have to be read from the ledger (excluding year-end closing entries), purchase invoices ignore issue-date filters, files have three different download shapes, and the rate limit (30 requests / 10 s) is respected client-side. See docs/DESIGN.md.

Getting an API token

1. Open the API tokens page of your UOL tenant (path /api_tokens, e.g. https://firma.ucetnictvi.uol.cz/api_tokens) and create a token.
2. The UOL user needs the REST API permission. A dedicated user with only the rights you want the assistant to have is a good idea.

Your tenant is the first part of your UOL address: https://firma.ucetnictvi.uol.cz → firma.

Want to try it first? UOL_TENANT=demo uses UOL's public DEMO company, no token needed.

Configuration

Claude Desktop

Settings → Developer → Edit Config, then add:

{

"mcpServers": { "uol": { "command": "npx", "args": ["-y", "uol-mcp"], "env": { "UOL_TENANT": "firma", "UOL_EMAIL": "you@example.com", "UOL_TOKEN": "your-token" } } } }

Claude Code

claude mcp add uol -e UOL_TENANT=firma -e UOL_EMAIL=you@example.com -e UOL_TOKEN=your-token -- npx -y uol-mcp

Cursor / VS Code

Cursor (.cursor/mcp.json) uses the same mcpServers block as Claude Desktop. VS Code (.vscode/mcp.json):

{

"servers": { "uol": { "type": "stdio", "command": "npx", "args": ["-y", "uol-mcp"], "env": { "UOL_TENANT": "firma", "UOL_EMAIL": "you@example.com", "UOL_TOKEN": "your-token" } } } }

Docker

docker run -i --rm -e UOL_TENANT=firma -e UOL_EMAIL=you@example.com -e UOL_TOKEN=your-token -v "$HOME/Downloads/uol-mcp:/data" ghcr.io/jakubbegera/uol-mcp

Exported and downloaded files are written to /data inside the container; the -v mount keeps them. In an MCP client config, use docker as the command and the rest as args.

Claude Desktop extension

Each release ships uol-mcp.mcpb. Open it to install, then fill in tenant, e-mail and token in the form; the token is stored as a secret. bash scripts/build-mcpb.sh builds the bundle from source.

HTTP server (self-hosting)

MCP_TRANSPORT=http MCP_AUTH_TOKEN=$(openssl rand -hex 32) UOL_TENANT=firma UOL_EMAIL=you@example.com UOL_TOKEN=your-token npx -y uol-mcp

The endpoint is http://127.0.0.1:3000/mcp (HOST, PORT to change; /health for probes). Two modes:

• One tenant: UOL credentials in the server's env. Clients must send Authorization: Bearer ; the server refuses to start without the token.
• Pass-through: no UOL credentials in the env. Each client sends its own X-UOL-Tenant, X-UOL-Email and X-UOL-Token headers with every request; the server stores nothing. MCP_AUTH_TOKEN is optional on localhost.

Over HTTP, exported invoices and downloaded documents come back inside the tool result instead of being saved on the server, and upload_document takes the file as content_base64 — it reads no paths on the server unless UOL_UPLOAD_DIRS is set. In Docker, bind to all interfaces and publish the port: docker run -p 3000:3000 -e MCP_TRANSPORT=http -e HOST=0.0.0.0 -e MCP_AUTH_TOKEN=… -e MCP_ALLOWED_HOSTS=mcp.example.com ….

The server speaks plain HTTP: anywhere beyond localhost, put it behind a reverse proxy that terminates TLS. The server refuses to start on a non-loopback address without MCP_AUTH_TOKEN and MCP_ALLOWED_HOSTS.

Check the setup

UOL_TENANT=firma UOL_EMAIL=you@example.com UOL_TOKEN=your-token npx -y uol-mcp doctor

Writing (opt-in)

With UOL_ACCESS=write these tools appear:

UOL_ACCESS=full adds delete_sales_invoice (drafts only), repair_sales_invoice (storno or back to draft for issued invoices) and api_request (a raw write to any endpoint).

Invoice lines need a UOL product (list_codebook with kind: products lists them). Every write supports dry_run (shows exactly what would be sent), creates are safe to retry (idempotency key), and the tools are marked so clients ask you before running them. Set UOL_AUDIT_LOG to keep a record of every write.

Several companies

Accountants with several clients on UOL can serve them all from one server. List the accounts in UOL_ACCOUNTS and give each one its own variables (name upper-cased, - becomes _):

"env": {

"UOL_ACCOUNTS": "firma,novak", "UOL_ACCOUNT_FIRMA_TENANT": "firma", "UOL_ACCOUNT_FIRMA_EMAIL": "ja@firma.cz", "UOL_ACCOUNT_FIRMA_TOKEN": "op://Private/UOL firma/credential", "UOL_ACCOUNT_NOVAK_TENANT": "novak", "UOL_ACCOUNT_NOVAK_EMAIL": "ja@firma.cz", "UOL_ACCOUNT_NOVAK_TOKEN": "op://Private/UOL novak/credential", "UOL_ACCOUNT_NOVAK_LABEL": "Novák s.r.o." }

The first account is the default (or set UOL_DEFAULT_ACCOUNT). With the 1Password CLI, start the server as op run -- node …/dist/index.js and the op:// references are replaced by the tokens at startup — nothing secret sits in the config. uol-mcp doctor checks every account.

Alternatively, point UOL_PROFILES_FILE at a JSON file:

{

"default": "firma", "accounts": { "firma": { "tenant": "firma", "email": "ja@firma.cz", "token_env": "UOL_TOKEN_FIRMA" }, "novak": { "tenant": "novak", "email": "ja@firma.cz", "token_env": "UOL_TOKEN_NOVAK", "label": "Novák s.r.o." } } }

token_env names an environment variable holding the token, so the file needs no secrets (an inline token works too; keep such a file chmod 600). The server then offers list_accounts, and every tool takes an account argument — *"Kdo dluží firmě Novák?"* goes to the right tenant. Each account keeps its own rate limit.

Accounts can have their own access level: with UOL_ACCESS=write and UOL_ACCOUNT_NOVAK_ACCESS=read (or "access": "read" in the profiles file), writes to Novák are refused while the ot