Skip to main content
Glama
dennismenken

BuchhaltungsButler MCP-Server

by dennismenken

Related Servers

Alternatives to BuchhaltungsButler MCP-Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      A
      maintenance
      Enables AI assistants to manage BuchhaltungsButler bookkeeping through all 48 API endpoints, with safety-categorized tools for read, write, and destructive operations.
      54
      6 npm
      4
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      23
      6 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      10
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing BuchhaltungsButler API tools for accounting, invoicing, and receipt management with curated, token-efficient endpoints.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Integrates 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.
      36 npm
      6
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables connecting AI assistants to Exact Online through its official REST API with OAuth2 authentication and automatic token refresh. Provides curated tools for reading and, optionally, writing common accounting entities such as accounts, contacts, items, journal entries and sales/purchase invoices, plus generic GET/POST/PUT/DELETE tools for any other endpoint, over local stdio or hosted HTTP transports.
      -

    TDQS

    A3.9/5.0

    Scored across 59 tools

    Disambiguation3/5

    Tools have clearly distinct purposes overall, but several high-level tools (bb_masterdata_search, bb_records_collect, bb_assignments_get, bb_balances_get) explicitly replace or overlap with specific base tools, which can confuse tool selection. Descriptions help, but the functional overlap is real.

    Naming Consistency3/5

    Naming uses a consistent bb_ prefix and verb_noun pattern, but the convention is mixed with noun-first names like bb_payment_accounts_list, bb_postingaccounts_search, bb_receipts_create, and verb-first names like bb_transactions_assign_receipt, bb_postings_create_for_receipt, making the pattern less predictable.

    Tool Count2/5

    59 tools is very large for an accounting API wrapper, and the count is inflated by many near-duplicate operations (single vs batch, per-entity unconfirm, separate search/list tools). This heavy surface increases the risk of confusion and misselection.

    Completeness3/5

    Core CRUD for receipts, postings, master data, reports, and transactions is mostly covered, but there are notable gaps: no read/update/delete for invoices, no comments retrieval/deletion, no attachment handling for existing receipts, and some tools are read-only where write would be expected. These gaps are acknowledged in descriptions and may cause dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues