Buchhaltungsbutler MCP
Related Servers
Alternatives to Buchhaltungsbutler MCP
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with the BuchhaltungsButler accounting API via MCP, providing tools for managing receipts, transactions, invoices, postings, and master data directly from Claude Desktop and other MCP-compatible clients.2320 npmMIT
Related Servers
- AlicenseAqualityAmaintenanceConnects an AI assistant to a BuchhaltungsButler tenant through 59 German-language tools — 54 endpoint tools (one per API v1 endpoint) plus 5 bundle tools — covering documents, payments, invoices, postings, master data, cost centers, and reports, of which 19 are read-only. Runs locally, so credentials go only to BuchhaltungsButler itself, and lets users control in their client which tools the assistant may call.5910 npm1MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates with the sevdesk German accounting API, providing 76 tools for full CRUD operations across contacts, invoices, vouchers, orders, credit notes, bank accounts, transactions, parts, tags, addresses, and communication ways.222 npm6MIT
- 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.3025 PyPI1AGPL 3.0
- AlicenseCqualityBmaintenanceProvides comprehensive AI-agnostic access to all Firefly III personal finance features via 66 tools, enabling natural language management of accounts, transactions, budgets, and more.667 npm24MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with QuickFile UK accounting software, providing access to invoicing, client management, purchases, banking, and financial reporting through 40+ tools covering the complete QuickFile API.19 npm4MIT
- AlicenseAqualityBmaintenanceEnables LLMs to interact with Billforward's billing and subscription management API, providing tools for accounts, subscriptions, invoices, payments, and more with read-only safety by default.2346 npm3MIT
TDQS
Scored across 46 tools
Tools are largely differentiated by resource and action, and descriptions explicitly distinguish easily confused pairs such as accounts vs postingaccounts, debtors vs creditors, and receipt/transaction/free postings. The main remaining risk is cognitive load from many near-parallel variants like postings_create_for_transaction, postings_create_for_receipt, and postings_create_free, which require description reading to choose correctly.
Names consistently follow an entity_action snake_case convention: debtors_create, receipts_list, postings_unconfirm_for_receipt, reports_get_sums_ledger, etc. Although the pattern is noun-first rather than verb-first, it is applied predictably across the entire set.
With 46 tools, the surface is very heavy for agent selection and exceeds the practical range for reliable tool choice. The breadth reflects a substantial accounting domain, but the many analogous create/unconfirm/assign variants make the set cumbersome.
Coverage is broad across master data, receipts, transactions, postings, and reports, with useful cross-references and workaround guidance. However, lifecycle gaps are notable: invoices cannot be listed or retrieved after creation, transactions lack update/delete, several master-data resources lack delete, and comments are write-only.