@t4dhg/mcp-holded
Related Servers
Alternatives to @t4dhg/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
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server for the Holded Invoice API. This server allows AI assistants like Claude to interact with Holded's invoicing, contacts, products, and more.7845 npm19MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Holded — invoicing, accounting, CRM, projects, and team77 npm1MIT
- FlicenseNot gradedqualityDmaintenanceAn open-source MCP server for the Holded API that enables natural language management of invoicing, CRM, projects, team, and accounting.-
- AlicenseNot gradedqualityDmaintenanceMCP server for the Billingo V3 Hungarian invoicing API. Manage invoices, partners, products, spendings, and bank accounts from any MCP client.7 npm1MIT
- 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
TDQS
Scored across 15 tools
Each top-level tool maps to a distinct Holded domain, so the primary purposes are clear. A few action names recur across domains (e.g., list_accounts in accounting vs. treasury, task actions in CRM vs. projects), which could cause occasional misselection without careful attention to the tool context.
All tools follow the same `holded_<domain>` snake_case pattern, and actions within each tool use consistent lowercase snake_case verbs and nouns. The meta tools holded_discover and holded_request also fit the prefix convention cleanly.
15 tools is at the upper end of the ideal range but appropriate for a broad ERP suite covering contacts, sales, purchases, payments, treasury, accounting, catalog, team, CRM, projects, calendar, inbox, and webhooks. Each domain tool earns its place, and the discover and request tools provide useful navigation and escape-hatch roles.
The domain tools provide broad lifecycle coverage: create, read, update, delete, list, and domain-specific actions like approve, send, reconcile, and attach. The low-level holded_request tool also covers the remaining ~350 v2 operations, so there are no dead ends and the set is effectively complete for the stated API surface.