Skip to main content
Glama
contabridge-mcp

contabridge-mcp

by ArceeDev

Related Servers

Alternatives to contabridge-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to parse and validate Spanish Norma 43 bank statement files, convert them to CSV, and reconcile bank movements against invoices with confidence scoring and evidence. It also validates IBAN, CCC, NIF/NIE/CIF, and SEPA creditor identifiers while supporting credit-based hosted or local usage.
      7
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with a double-entry ledger, offering tools for account management, balanced journal entries, balance queries, trial balance, and penny-perfect allocation. Built with safety by construction: no update/delete tools, idempotent posting, and an append-only journal.
      7
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to interact with Quipu accounting data via natural language, including invoicing, expenses, contacts, and Spanish VAT reporting.
      18
      77 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to read and write Cynco accounting data, including querying books, creating invoices, reconciling transactions, and generating financial reports.
      9 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to issue, correct, and register legally compliant Spanish electronic invoices with AEAT VeriFactu, supporting F1/F2 types, R1–R5 correctives, and NIF validation from Claude, ChatGPT, Cursor, or VS Code.
      136
      293 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to propose and book bank transactions, split card collections, link receipts, and learn from approved bookings through an accounting web app's API.
      MIT

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct stage of the workflow: detection, conversion, validation, bank-statement import, composition, and account resizing, with billing utilities clearly separate. There is minor overlap between convert_journal (auto-detects source) and detect_format, and between convert_journal and build_journal, but descriptions make the boundaries clear.

    Naming Consistency4/5

    Seven of eight tools follow a clear verb_noun snake_case pattern (convert_journal, validate_journal, bank_to_journal, detect_format, build_journal, resize_account). The two exceptions, pricing and credits_balance, are noun-only but are clearly non-domain utility tools, so consistency remains readable.

    Tool Count4/5

    Eight tools is well-scoped for a journal-conversion server, with each domain tool earning its place. Two of the eight are billing/licensing utilities rather than accounting operations, which is slightly over-inclusive but reasonable.

    Completeness4/5

    The surface covers the full lifecycle: detect format, convert between formats, validate before import, build journals from scratch, and handle bank statements, plus account resizing. A dedicated parse/read tool returning full structured entries (rather than the first 50 via validate) is a minor gap agents can work around via csv output.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing