BoondManager MCP Server
Related Servers
Alternatives to BoondManager MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the BoondManager API, enabling Claude to search, create, and modify records across 36 domains with 158 tools.2182152 npm20Apache 2.0
- AlicenseBqualityBmaintenanceMCP server that connects AI assistants to the Conexa business management system, enabling CRUD operations on sales, customers, plans, contracts, charges, and more via 83 tools.83121 npm1MIT
- FlicenseAqualityCmaintenanceMCP server that provides an AI assistant with access to Odoo business data, enabling read operations and human-approved record creation.3-
- AlicenseAqualityCmaintenanceMCP server connecting AI assistants to official France Travail APIs for real-time job offers, ROME code prediction, and hiring company search.747 npm1MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to interact with Odoo ERP, allowing natural language queries, record creation, updates, and deletions.LGPL 3.0
- FlicenseNot gradedqualityCmaintenanceA single MCP server that exposes safe, permission-checked tools for AI assistants to reach file systems, databases, APIs, Git, cloud services, and business applications.-
TDQS
Scored across 95 tools
Every tool follows a clear entity-action pattern, and the entity names (candidates, resources, contracts, etc.) are distinct enough that an agent can reliably select the correct tool. The few broader verbs like 'search' or 'get' are scoped by entity, so there is no meaningful overlap.
All tools use the consistent boond_<plural_entity>_<verb> convention with snake_case throughout. Verbs such as search, get, create, update, delete, send, and certify are used consistently across entities.
95 tools is an extreme count that exceeds the 3-15 well-scoped range by a wide margin. Even though BoondManager covers a broad ERP domain, this MCP surface is too large and will create a heavy tool-selection burden for agents.
The tool set covers search/get/create/update for most core business objects and includes specialized lifecycle actions like sending quotations, certifying expenses, and installing apps. The main gap is the near-total absence of delete operations, but for many ERP records deletion is intentionally restricted, so this is a minor limitation rather than a fatal gap.