accelo-mcp
Related Servers
Alternatives to accelo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage a fully customizable CRM, including contacts, companies, sales pipelines, custom objects and fields, file uploads, and data relationships via MCP over HTTP.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage GoHighLevel CRM data including contacts, conversations, opportunities, calendars, and forms through MCP tools and resources.52AGPL 3.0
- AlicenseBqualityCmaintenanceEnables AI assistants to manage RogerRoger CRM data including people, organizations, lists, tags, and tasks through standardized MCP tools.226 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and write CRM data—companies, contacts, opportunities, tasks, and interactions—through MCP, with OAuth and provenance tracking for every value.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible LLMs to interact with the MOCO ERP API, providing full read/write access to time tracking, projects, invoices, contacts, and other endpoints.6 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read and write GestãoClick ERP data—customers, suppliers, products, quotes, sales, service orders, purchases, invoices, and finance—through the official API, using 127 tools via any MCP-compatible client.1MIT
TDQS
Scored across 219 tools
Tools follow a strict list/count/get/create/update/delete pattern per resource, so most are clearly distinct. However, the sheer volume and close concepts like profile fields vs extension fields, list_filters vs list_object_filters, and object_budget_templates vs object_budgets create some selection ambiguity. Descriptions help, but the 219-tool surface is hard to navigate.
The accelo_verb_noun convention is applied consistently across nearly all tools, e.g., list_companies, get_company, create_company, update_company. Minor deviations like get_current_staff, rate_limit_status, describe_object, and progress_task_to_start/done are exceptions but do not undermine the overall predictable pattern.
219 tools is an extreme count, far beyond the 3-15 well-scoped range and well above the 50+ threshold for extreme mismatch. Even for a broad PSA platform, this creates a massive selection surface for agents. Each tool may have a purpose, but the set is impractical as a coherent unit.
The server covers a very wide range of Accelo objects with read/list/count for most and create/update/delete for many core entities. However, major resources like milestones, contracts, invoices, payments, purchases, and assets lack full CRUD (e.g., no create_milestone, no create_contract, no create_invoice, no delete_task). This leaves notable dead ends for lifecycle workflows.