bokio-mcp
Related Servers
Alternatives to bokio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables MCP clients to read invoices, supplier invoices, vouchers, financial reports, and AR/AP ageing from a Swedish accounting system, with optional draft-only write tools for customers, offers, orders, and unsent invoice drafts after confirmation. It also exposes many other read endpoints through a safety allowlist.261MIT

epago MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP-capable clients to read and write directly in epago accounting, including chart of accounts, transactions, invoices, payments, receipts, and tax reports.MIT- AlicenseAqualityBmaintenanceEnables MCP clients to query and manage UOL Účetnictví bookkeeping through the UOL REST API, including invoices, receivables, VAT, bank balances, documents, and contacts. It is read-only by default, with opt-in tools for creating or updating records and uploading documents.181,814 npmMIT
- AlicenseAqualityBmaintenanceEnables interaction with the Bokio accounting API for managing journal entries, invoices, customers, items, and more, with read-only mode by default for safety.3785 npm3MIT
- FlicenseNot gradedqualityBmaintenanceExposes Visma e-conomic REST API as 73 MCP tools for managing customers, suppliers, products, invoices, quotes, orders, accounting, and reference data, with secure authentication, allowlist, read-only mode, and audit logging.-
- AlicenseBqualityBmaintenanceEnables MCP clients such as Claude and Cursor to read and, when writes are enabled, modify accounting data—including invoices, bills, contacts, expenses, bank accounts and reports—through the FreeAgent API.91MIT
TDQS
Scored across 40 tools
Each tool targets a distinct entity or action (list vs get vs download) with clear hierarchical relationships (e.g., invoice → payments/settlements/attachments). No overlapping purposes that would cause misselection.
All domain tools follow a strict 'bokio_verb_noun' pattern (list/get/download), with utility tools (ping, get_connection_status) clearly separated. The naming is highly predictable and consistent.
With 40 tools, the count is on the heavier side but justified by the breadth of accounting entities (invoices, customers, journal entries, items, uploads, etc.). Each tool serves a specific resource, though some consolidation could reduce redundancy.
The tool surface comprehensively covers read operations across all major accounting entities, including downloads and SIE export. However, it lacks any create/update/delete tools, so the lifecycle is incomplete unless the server is intentionally read-only.