Fortnox MCP Server
Related Servers
Alternatives to Fortnox MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for the FreeAgent accounting API, enabling LLMs to securely access and manage accounting data including contacts, invoices, bills, bank transactions, and more.5 npm1MIT
- AlicenseBqualityDmaintenanceAn MCP server for Danish accounting via Billy.dk API, enabling natural-language control over invoices, bank lines, reports, and more, with a write-guard for safety.651MIT
- FlicenseNot gradedqualityBmaintenanceMulti-tenant MCP server connecting accounting software to AI assistants via ~87 tools. Supports Bokio (Swedish accounting) with mock mode for development.-
- FlicenseNot gradedqualityDmaintenanceHosted MCP server that enables AI assistants to manage clients, invoices, and expenses via the Invox API, supporting actions like drafting, sending, cancelling, and marking invoices as paid, as well as logging expenses and updating client information.-
- AlicenseAqualityBmaintenanceMCP server for the Elorus invoicing and accounting platform, enabling AI assistants to create invoices, manage contacts, and query financial data through natural language.434MIT
- AlicenseBqualityCmaintenanceMCP server that provides 76 tools for the FreeAgent accounting API, enabling management of invoices, expenses, contacts, projects, timeslips, banking, bills, estimates, credit notes, and accounting reports through natural language.7612 npm5MIT
TDQS
Scored across 51 tools
The CRUD tools for customers, suppliers, invoices, and accounts are clearly distinct, but the large set of analytical tools creates ambiguity. Tools like period_comparison vs yearly_comparison, customer_growth vs period_comparison, and several 'LIMITED' tools that all defer to account_activity have overlapping or unclear boundaries.
All tools share the fortnox_ prefix and consistently use lowercase with underscores. However, the pattern is not strictly verb_noun: CRUD tools use list_/get_/create_/update_/delete_, while analytics use noun-based names like invoice_summary, order_pipeline, and cash_flow_forecast. The style is predictable but not uniform.
With 51 tools, the server is heavily oversized. Many analytics overlap or are stubs (e.g., five 'LIMITED' tools that just point to account_activity), suggesting the tool count could be reduced significantly without losing functionality. This exceeds the 25+ threshold for 'too many'.
Core financial entities (customers, suppliers, invoices, accounts, vouchers) have solid lifecycle coverage, but there are notable gaps: order and offer tools are list-only with no create/get/update/delete, supplier invoices lack creation/update, and several analytics return only metadata or structure rather than actual data, causing dead ends.