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.2311 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.5963 npmMIT
- AlicenseNot gradedqualityBmaintenanceIntegrates 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.41 npm6MIT
- AlicenseBqualityBmaintenanceEnables 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.10MIT
- AlicenseCqualityDmaintenanceProvides comprehensive AI-agnostic access to all Firefly III personal finance features via 66 tools, enabling natural language management of accounts, transactions, budgets, and more.661 npm23MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.10 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.2313 npm3MIT
TDQS
Scored across 46 tools
Tools are grouped by resource with clear descriptions separating pairs like accounts vs postingaccounts, creditors vs debtors, and receipts vs transactions. Minor overlap exists between postings_list and reports_get_sums_ledger (both expose postings for an account), so one or two choices could be ambiguous, but most tools are sharply distinct.
All tool names follow a consistent `resource_action` snake_case pattern (e.g. accounts_list, creditors_create, cost_locations_update, receipts_restore). Compound actions like transactions_assign_receipts and postings_unconfirm_for_receipt remain readable and within the same convention.
46 tools is a very large surface for an agent to navigate, well beyond the 'borderline heavy' 16-25 range. Although each endpoint maps to a real API operation, the set is not tightly scoped and would benefit from consolidating related variants.
Several resources are create-only or lack full lifecycle support: invoices cannot be listed, edited, or cancelled after creation; comments cannot be read; accounts/transactions have no update or delete; receipts have no update. These gaps leave agents with dead ends (e.g., issuing an invoice with no way to retrieve or cancel it).