e-arveldaja MCP Server
Related Servers
Alternatives to e-arveldaja MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables natural language management of e-conomic accounting, including customers, products, and invoices, with full CRUD and PDF download capabilities.173MIT
- AlicenseNot gradedqualityBmaintenanceExposes ~60 tools for the Merit Aktiva accounting API, covering sales/purchase invoices, payments, customers, vendors, items, general ledger, offers, reference data, and reports with both read and write operations.12 npmMIT
- AlicenseCqualityCmaintenanceEnables AI assistants to manage invoices, contacts, purchases, journal entries, and other accounting operations via the Fiken API.10019 npm2MIT
- 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
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with FreshBooks accounting API for managing clients, invoices, payments, and more through natural language.-
- 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.11 npm4MIT
TDQS
Scored across 130 tools
Many tools have overlapping purposes: create_purchase_invoice_from_pdf vs create_purchase_invoice vs extract_pdf_invoice vs validate_invoice_data; multiple merged entry points (receipt_batch, process_camt053, accounting_inbox, reconcile_bank_transactions, classify_bank_transactions) blur boundaries. Several compute_* tools (compute_trial_balance, compute_profit_and_loss, compute_balance_sheet, compute_account_balance, compute_account_dimension_balances, compute_client_debt) are distinct but similar enough to cause misselection.
Most tools follow verb_noun snake_case (list_clients, create_journal, confirm_sale_invoice), but there are deviations: get_sale_invoice_document vs get_document, compute_* vs calculate-like semantics, and merged entry points with mode parameters (receipt_batch, process_camt053, accounting_inbox) break the pattern. Some names are vague (suggest_booking, recommend_workflow, continue_accounting_workflow).
130 tools is far beyond the well-scoped range and creates an extreme mismatch for an accounting server. Even a complex domain like Estonian accounting does not justify this many entry points; many tools are variations or merged wrappers that could be consolidated.
The domain is well covered: clients, products, invoices (purchase/sale), journals, transactions, bank accounts, series, documents, VAT, reports, year-end close, dividends, Lightyear imports, CAMT, and audit logs. Minor gaps exist (e.g., no explicit sale invoice PDF email resend beyond send_sale_invoice, no direct purchase invoice payment matching beyond reconciliation), but the surface is comprehensive.