MCP server for POHODA (Stormware) accounting software. Manage invoices, stock, orders, bank documents, warehouse, and accounting from any MCP-compatible client.
48 tools covering all major POHODA agendas via mServer XML API, including PDF printing and a raw XML escape hatch. Every tool's XML is checked against Stormware's official XSD schema.
MCP server for POHODA (www.stormware.cz/pohoda/) — invoices, stock, orders, bank, warehouse, accounting (48 tools)
Bintang
4
Tool
—
Uptime
—
Requirements
Node.js 22+
POHODA with mServer enabled and running
mServer user credentials with XML communication rights
Installation
git clone https://github.com/hlebtkachenko/pohoda-mcp.git
cd pohoda-mcp
npm ci
npm run build
The server uses stdio transport. Point your MCP client to:
node /path/to/pohoda-mcp/dist/index.js
With environment variables set for authentication (see below).
Environment Variables
Variable
Required
Description
POHODA_URL
Yes
mServer URL (default port: 444)
POHODA_USERNAME
Yes
POHODA user with XML rights
POHODA_PASSWORD
No
POHODA password (default: empty, for a user without a password while POHODA access rights are off)
POHODA_ICO
Yes
Company IČO (accounting unit)
POHODA_TIMEOUT
No
Request timeout in ms (default: 120000)
POHODA_MAX_RETRIES
No
Max retries of list (read) requests on timeout/408/503 (default: 2). Writes are never retried
POHODA_READ_ONLY
No
true registers only list, status, company info and file download tools (default: false)
POHODA_CHECK_DUPLICITY
No
Sends STW-Check-Duplicity: true (default: false). POHODA matches resends by dataPack/dataPackItem id, and every request here gets a new UUID id, so this does not catch a resent write. Protection against double writes is that writes are never retried and a timed-out write is reported as outcome unknown
POHODA_LIST_LIMIT
No
Max records a list tool returns (default: 100); larger results are truncated with a note
POHODA_EXE_PATH
No
Path to Pohoda.exe; with POHODA_CONFIG_NAME enables mServer autostart
POHODA_CONFIG_NAME
No
mServer configuration name to start and stop
Read-only mode
With POHODA_READ_ONLY=true the create, update, delete, print and raw XML tools are not registered, and the client refuses to send anything but list requests. Use it to try the server against a real POHODA without risk. Any value other than true or false stops startup.
Write results
A write fails when POHODA reports an error at any level (response pack, item, document response or import detail); every error is listed with its errno, and warnings are shown on success too. When POHODA changes a value you sent (errno 603: replaced by a default, e.g. an unknown předkontace, normalised or truncated), create invoice, voucher, bank and internal document, and create or update address, start their answer with Created (ID …), but POHODA did not apply values you set: … naming each field and value; the record still exists, so the result is not an error. Fields you did not send that POHODA filled itself are listed in one POHODA filled defaults for: … line. Update and delete report "no record matched, or unconfirmed" when POHODA does not confirm the action. A write is never resent. When its answer is lost (timeout, connection dropped while reading, HTTP 5xx, or a 200 that is not a POHODA responsePack), the result says the outcome is unknown, so check with a list tool before trying again. When the connection is refused, nothing was sent and the result says Not sent: POHODA mServer is not running or not reachable at <url>; start mServer (on a remote host: scripts/mserver/pohoda-mserver start <config> <port>, see Run mServer on demand) and retry.
A list fails when the list element itself is in state error (its note is shown) and when mServer answers 200 with something other than a responsePack, so neither looks like an empty list.
Booking fields
pohoda_create_invoice, pohoda_create_voucher, pohoda_create_bank and pohoda_create_internal_doc accept optional booking fields. Every field is optional; an omitted field is not sent and POHODA applies its default. Reference fields take the POHODA abbreviation (sent as typ:ids); number series, bank accounts, cash registers, centres and activities come from pohoda_list_settings, VAT classifications from pohoda_list_vat, contracts from pohoda_list_contracts; předkontace abbreviations have no list tool, take them from POHODA.
paymentAccountNo + paymentBankCode (counterparty account, both or neither)
yes
no
yes
no
Line items on all four accept payVAT and the item-level accounting, classificationVAT, classificationKVDPH, centre, activity and contract.
mServer autostart (Windows)
With POHODA_EXE_PATH and POHODA_CONFIG_NAME set, the server checks on the first tool call whether mServer answers, and if not runs Pohoda.exe /HTTP start "<config>" and waits up to 30 s. On shutdown it stops mServer again, but only if it started it.
Run mServer on demand (POHODA on a remote Windows host)
When POHODA runs on another Windows machine, scripts/mserver/ starts mServer there over SSH only when you need it, tunnels its port to your machine, and stops it after a set time without XML requests. Stormware advises against running mServer as a Windows service or keeping it running all the time: a running mServer blocks backups and database maintenance of that company in other POHODA windows. These scripts use Task Scheduler start and stop, as Stormware recommends. The scripts are not in the npm package; take them from this repository.
Prerequisites
A POHODA user with rights to the XML communication.
An mServer configuration per company, created in POHODA: Účetní jednotky → Databáze → POHODA mServer. Note each configuration's name and port.
OpenSSH Server on the Windows host with key login, logging in as the Windows user who runs POHODA or as an administrator. Windows PowerShell 5.1 as the SSH shell works.
That Windows user signed in on the host (a locked screen is fine): mServer starts in their desktop session, next to their own POHODA window, and shows its monitoring window there.
Install (once, on the Windows host)
Copy scripts/mserver/windows/ to the host.
In an elevated Windows PowerShell, from that folder:
-User defaults to the current user; set it when you run the installer as a different administrator. Other options: -IdleMinutes (default 60), -PohodaExe (default C:\Program Files (x86)\STORMWARE\POHODA\Pohoda.exe), -LogDir (default C:\ProgramData\STORMWARE\POHODA\Log\HTTP).
This registers, per configuration, the tasks POHODA mServer start <config> and POHODA mServer stop <config> (running Pohoda.exe /HTTP start|stop "<config>" as that user), and one task POHODA mServer idle stop. -Config lists every configuration: running the installer again replaces all POHODA mServer * tasks with the new set. The idle script lives in C:\ProgramData\pohoda-mcp, writable only by SYSTEM and Administrators; the installer stops if that folder is a junction or owned by anyone else, since SYSTEM runs the script inside.
Use (macOS or Linux)
scripts/mserver/pohoda-mserver needs bash and ssh. Set POHODA_SSH_HOST to an ssh host alias with key login:
start runs the start task (unless the port already listens), waits up to 60 s for the port, and opens an ssh tunnel from 127.0.0.1:<port> to the host. Then point the MCP server at the tunnel: POHODA_URL=http://127.0.0.1:<port>. Set POHODA_LOCAL_PORT to use a different local port. stop runs the stop task and closes the tunnel. status shows whether the remote port listens and whether the tunnel is open. Exit codes: 0 ok, 1 remote command failed, 2 usage, 3 mServer not listening, 4 tunnel failed or closed, 5 host unreachable. State (tunnel control socket, watcher PID and log) lives in ${XDG_STATE_HOME:-~/.local/state}/pohoda-mserver/.
Idle stop
The task POHODA mServer idle stop runs every 5 minutes as SYSTEM. It reads the tail of each configuration's mServer log (<LogDir>\<config>.log); the last POST /xml request or the last server start counts as activity, GET /status does not. A running configuration idle for -IdleMinutes or longer is stopped through its stop task, and the action is written to C:\ProgramData\pohoda-mcp\idle-stop.log. On your machine, start leaves a watcher that checks every 5 minutes whether the remote port still listens and closes the tunnel once it does not, so the host is left alone. To change the minutes, run the installer again with the same -Config and a new -IdleMinutes.
Uninstall
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -Force
.\Install-MServerTasks.ps1 -Uninstall
This removes every POHODA mServer * task. The folder C:\ProgramData\pohoda-mcp (idle script and its log) stays; remove it by hand if you no longer need it.
Tools
System (4)
Tool
Description
pohoda_status
Check mServer status (processing queue, idle/working) and the POHODA program version from the last XML answer
pohoda_company_info
Get accounting unit info (company name, database, period)
pohoda_download_file
Download a file from POHODA's documents folder
pohoda_raw_xml
Send any dataPackItem XML not covered by a dedicated tool; the envelope and all namespace prefixes are added automatically
Print (1)
Tool
Description
pohoda_print
Print a record with a print report, or save it as PDF on the POHODA machine and optionally return the PDF in the response
Address Book (4)
Tool
Description
pohoda_list_addresses
Export contacts with filters (name, IČO, code, date)
pohoda_create_address
Create a new contact in address book (company = firm name / Firma, name = contact person / Jméno)
pohoda_update_address
Update an existing contact by ID
pohoda_delete_address
Delete a contact by ID
Invoices (2)
Tool
Description
pohoda_list_invoices
Export invoices of one type: issued, received, advance, proforma, credit notes, receivables, commitments
pohoda_create_invoice
Create an invoice with line items, partner, symbols, VAT and booking fields
POHODA's XML API cannot update or delete invoices, cash vouchers, bank documents, internal documents or contracts: their XSDs have no actionType. These agendas are create-only through this server; make corrections in POHODA itself.
Orders (3)
Tool
Description
pohoda_list_orders
Export issued/received orders with filters
pohoda_create_order
Create an order with items and partner
pohoda_delete_order
Delete an order by ID and type
Offers (2)
Tool
Description
pohoda_list_offers
Export issued/received offers
pohoda_create_offer
Create an offer with items
Enquiries (2)
Tool
Description
pohoda_list_enquiries
Export issued/received enquiries
pohoda_create_enquiry
Create an enquiry with items
Contracts (2)
Tool
Description
pohoda_list_contracts
Export contracts with filters
pohoda_create_contract
Create a new contract
Bank Documents (2)
Tool
Description
pohoda_list_bank
Export bank documents (receipts/expenses)
pohoda_create_bank
Create a bank document with items and booking fields
Cash Vouchers (2)
Tool
Description
pohoda_list_vouchers
Export cash register vouchers
pohoda_create_voucher
Create a cash voucher (receipt/expense) with booking fields
Internal Documents (2)
Tool
Description
pohoda_list_internal_docs
Export internal accounting documents
pohoda_create_internal_doc
Create an internal document with booking fields
Stock / Inventory (5)
Tool
Description
pohoda_list_stock
Export stock items with filters (code, name, store)
pohoda_create_stock
Create a new stock item
pohoda_update_stock
Update a stock item by ID or code
pohoda_delete_stock
Delete a stock item
pohoda_list_stores
List all stores (warehouses)
Warehouse Documents (8)
Tool
Description
pohoda_list_prijemky
Export receiving documents (příjemky)
pohoda_create_prijemka
Create a receiving document
pohoda_list_vydejky
Export dispatch documents (výdejky)
pohoda_create_vydejka
Create a dispatch document
pohoda_list_prodejky
Export sales documents (prodejky)
pohoda_create_prodejka
Create a sales document
pohoda_list_prevodky
Export transfer documents (převodky)
pohoda_create_prevodka
Create a transfer document (items by stock code)
Production & Service (4)
Tool
Description
pohoda_list_vyroba
Export production documents
pohoda_create_vyroba
Create a production document (items by stock code)
npm test # build + unit and end-to-end tests against a fake mServer
npm run check:xsd # validate every tool's XML against the official XSD (needs xmllint and internet on first run)
Belum ada daftar tool. Server remote mendapatkannya setelah pemeriksaan kesehatan pertama.
FAQ
Pertanyaan
Bagaimana cara menginstal Pohoda?
Salin konfigurasi stdio untuk Cursor, Claude Desktop, Claude Code, atau VS Code di halaman ini. Konfigurasi ini memakai instalasi dari penerbit, bukan proxy PlugMCP.
Apakah Pohoda memerlukan kunci API?
Tidak ada variabel lingkungan wajib yang tercantum di catatan ini.
Transport apa yang digunakan Pohoda?
Pohoda berjalan secara lokal melalui stdio.
Kapan Pohoda terakhir diperiksa?
Terakhir diperiksa 2026-10-28. MCP server for POHODA (www.stormware.cz/pohoda/) — invoices, stock, orders, bank, warehouse, accounting (48 tools)