e-conomic MCP Server
Related Servers
Alternatives to e-conomic MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables interaction with the Estonian e-arveldaja (RIK e-Financials) REST API to manage financial records like invoices and journal entries using natural language. It supports automating purchase invoice entry from PDFs, reconciling bank transactions, and generating financial reports.130234 npm34Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides comprehensive CRUD operations for 29 QuickBooks Online entity types and 11 financial reports, enabling full accounting management through natural language.Apache 2.0
- AlicenseBqualityDmaintenanceEnables AI agents to manage invoices, customers, suppliers, accounting entries, orders, and more through Fortnox's cloud accounting platform via natural language.2027 npm1MIT
- AlicenseCqualityCmaintenanceEnables AI assistants to manage invoices, contacts, purchases, journal entries, and other accounting operations via the Fiken API.10013 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the SuperFaktura invoicing system for managing invoices, clients, and expenses via natural language.1Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage e-invoices through natural language, supporting EU compliance formats like ZUGFeRD and XRechnung, as well as US plain PDF invoices.7-
TDQS
Scored across 17 tools
Each tool targets a distinct resource-action pair: customers, products, invoice drafts, booked invoices, and reference data. List vs. get operations are clearly separated, and even the 'hello' tool is unambiguous.
Tools consistently use verb_noun snake_case (list_, get_, create_, update_, book_, download_, upsert_). The only outlier is 'hello', which breaks the pattern but is a trivial helper.
At 17 tools, this is slightly above the typical 3-15 range, but the count is justified by covering customers, products, invoices, and reference data. No tool feels redundant.
The invoice workflow is well covered from draft creation through booking to PDF download. However, customers lack a create operation and products lack a single get operation, leaving minor gaps.