Aikount MCP
Related Servers
Alternatives to Aikount MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceThe first fiscal MCP server for Spain, connecting AI agents to live IAE, CNAE 2025, AEAT tax-form, and RETA data from official sources.MIT
- AlicenseBqualityCmaintenanceMCP server to interact with the Cuéntica accounting API, allowing users to manage invoices, expenses, income, clients, providers, and bank accounts via natural language.592MIT
- FlicenseBqualityDmaintenanceMCP server for DACH accounting automation. Connect AI assistants to sevDesk and Lexoffice — create invoices, manage contacts, handle bookings and vouchers for German-speaking businesses.1527 npm-
- AlicenseNot gradedqualityDmaintenanceMCP server for integrating VeriFactu (AEAT) with Claude Code and Cursor, enabling generation, chaining, and sending of electronic invoicing records via natural language.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for agent-first double-entry bookkeeping for Dutch SMEs, supporting VAT, Peppol BIS 3.0 e-invoicing, and local-first SQLite storage with full audit logging and deterministic JSON output.1Apache 2.0
- AlicenseAqualityBmaintenanceMCP server for VoxFactura enabling AI assistants to query business data (invoices, expenses, project margins, clients, VAT) and create draft quotes or mark invoices paid via a scoped API, with no direct client sends.11MIT
TDQS
Scored across 23 tools
Each tool targets a distinct operation or resource. The generic `api_request` is explicitly for uncovered endpoints, avoiding overlap. Tools like `modelo_303_csv` and `modelo_303_summary` differ clearly in output format. No ambiguity among dedicated tools.
Most tools follow a consistent `verb_noun` pattern (e.g., `create_contact`, `list_invoices`). A few deviate like `reconciliation_board`, `ledger`, and `api_request`, but the overall pattern is predictable and readable.
With 23 tools, the set is well-scoped for an accounting/invoicing server. It covers contacts, invoices, purchases, bank movements, reconciliation, tax models, accounts, and products without being overly bloated or sparse.
Core workflows (create/issue invoices, list/manage contacts, reconcile, generate tax reports) are covered. Missing CRUD for some entities (e.g., update/delete contact, create product) but the generic `api_request` tool fills these gaps, making the surface largely adequate.