BuchhaltungsButler MCP-Server
Related Servers
Alternatives to BuchhaltungsButler MCP-Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI assistants to manage BuchhaltungsButler bookkeeping through all 48 API endpoints, with safety-categorized tools for read, write, and destructive operations.4624 npm7MIT
- 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.2324 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.30AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceMCP server exposing BuchhaltungsButler API tools for accounting, invoicing, and receipt management with curated, token-efficient endpoints.-
- 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.82 npm6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and draft accounting documents such as invoices, vouchers, contacts, and articles via the Lexware Office API, including PDF rendering and receipt uploads. Supports OAuth and static token authentication for secure access.MIT
TDQS
Scored across 59 tools
Most tools are clearly distinct with detailed descriptions that explicitly reference alternative tools, especially for similar operations like postings creation and report retrieval. However, the sheer number of tools (59) and the presence of batch variants and convenience wrappers (bb_reports_run vs. create/get, bb_assignments_get vs. get+list) introduce some ambiguity, though descriptions mitigate it well.
All tool names follow a highly consistent 'bb_<resource>_<verb>_<qualifier>' pattern, e.g., bb_receipts_create, bb_transactions_assign_receipt, bb_postings_unconfirm_free. No mixed naming conventions (camelCase, hyphenated, etc.) are present; the only minor deviations are unique verbs like 'collect' and 'run', but they still fit the established resource-verb structure.
With 59 tools, the server far exceeds the 50+ threshold defined as an extreme mismatch. Many tools are batch or type-specific variants (e.g., bb_postings_create_for_receipt vs. bb_postings_create_for_receipt_batch) or convenience wrappers (bb_reports_run, bb_assignments_get) that could be consolidated, resulting in an overly large and hard-to-navigate toolset for the domain.
The toolset has significant gaps in the accounting lifecycle. Invoices can be created (including drafts and e-invoices) but cannot be read, searched, updated, or deleted via the API; comments are write-only with no read or delete endpoint; payment accounts lack an update operation. These omissions will cause agent failures when verifying created documents or maintaining account data, indicating an incomplete surface for a comprehensive accounting server.