bokio-mcp
Related Servers
Alternatives to bokio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to read and write Bokio accounting data for one company through 85 tools covering invoices, customers, suppliers, journal entries, chart of accounts, fiscal years, items, tags, uploads, SIE export, and bank payments.40MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with the sevDesk accounting API for managing contacts, invoices, credit notes, orders, vouchers, transactions, and parts.18 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to read and write Cynco accounting data, including querying books, creating invoices, reconciling transactions, and generating financial reports.13 npm1MIT
- AlicenseAqualityDmaintenanceConnects AI assistants to the Danish accounting platform Billy (billy.dk) for managing invoices, journal entries, balances, and receipts, with built-in human approval for all write operations.4039 npm1MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to interact with the nula.bg accounting platform — invoices, purchases with OCR, customers, inventory, and bank feeds — through an API key, with read-only mode by default.1332 npmMIT
- AlicenseBqualityAmaintenanceEnables AI assistants to query and manage self-hosted accounting data—invoices, balances, and books—through natural language, with read-only tools by default and optional scoped write operations.3077 PyPIAGPL 3.0
TDQS
Scored across 6 tools
Each tool targets a distinct entity or operation: fiscal years (list/get), chart of accounts, customer (get), items (list/get). No overlapping purposes; list/get pairs are clearly distinguished.
Most tools follow a consistent 'bokio_verb_noun' pattern (e.g., list_fiscal_years, get_item). The exception is 'bokio_chart_of_accounts', which lacks a verb, but still clearly conveys its purpose. Overall pattern is mostly predictable.
6 tools is a reasonable size for a focused accounting integration. The set covers core read operations without being too sparse or bloated. Slightly on the low side but appropriate for a read-only subset.
The tool surface is heavily read-only, missing common write operations like creating/updating customers, items, transactions, or generating reports. For a full accounting MCP, these gaps would cause agent failures in most workflows.