MCP Holded
Related Servers
Alternatives to MCP Holded
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for Holded invoicing and treasury management, enabling creation and management of invoices, purchases, estimates, contacts, bank accounts, and cashflow forecasts.MIT
- AlicenseBqualityBmaintenanceMCP server for Holded API v2, enabling listing and querying of contacts, invoices, purchases, products, services, and payments, with low-level access to any endpoint.1547 npm1MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server for SuperFaktura invoicing system. Enables AI assistants to interact with SuperFaktura API for managing invoices, clients, and expenses.Apache 2.0
- AlicenseAqualityDmaintenanceMCP server that connects Claude Code to the Holded API for natural language financial, accounting, and invoicing queries, with built-in Spanish PGC context.132Apache 2.0
- 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.-
- AlicenseBqualityDmaintenanceMCP server for Invoice Ninja v5 API. Enables AI assistants to manage clients, invoices, quotes, payments, and time tracking through natural language.3223 npm2MIT
TDQS
Scored across 119 tools
Many tools are cleanly distinct by resource and action, but several overlap explicitly: list_treasuries vs the bank_account tools, list_ledger_entries vs get_daily_ledger (same endpoint), and get_chart_of_accounts vs list_accounting_accounts (same endpoint). The descriptions helpfully flag these duplications and consolidation plans, which mitigates some misselection risk, but the boundaries remain unclear in practice.
Most tools follow a predictable list_/get_/create_/update_/delete_ + resource pattern (list_contacts, get_product, delete_payment, etc.). Some deviations exist (ship_all_items, clock_in_employee, reconcile_bank_movement, get_taxes plural, and the 'serie'/'series' inconsistency), but they are action verbs that stay readable.
119 tools is very high even for a full ERP surface covering contacts, documents, payroll, accounting, and treasury. Redundant pairs (treasury vs bank accounts, ledger vs daily ledger, chart of accounts vs ledger accounts) show bloat rather than strictly additive scope, with consolidation explicitly deferred to a later release.
Coverage is broad and lifecycle-complete across most domains (contacts, products, documents, payments, treasury, warehouses, payroll, accounting, contact groups, numbering series). A few gaps exist — purchaserefund has no full CRUD, purchase PDFs unsupported — but these are largely upstream API limitations that agents can work around.