Ploomes MCP Server
Related Servers
Alternatives to Ploomes MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceConnects AI assistants to the Ploomes CRM, exposing 153 tools for CRUD operations on entities, pipeline and field configuration, CPQ proposal models, automations, and webhooks.-
- FlicenseCqualityCmaintenanceExposes 153 tools to connect AI assistants to the Ploomes CRM, enabling CRUD operations, funnel configuration, CPQ, automations, and webhooks.1001-
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server for the Ploomes CRM API, providing 49 tools to query contacts, deals, products, and other business data using natural language.9MIT
- AlicenseBqualityAmaintenanceProvides comprehensive access to Pipedrive CRM with 100+ tools for managing deals, contacts, organizations, activities, and sales workflows through natural language conversations with Claude.1002512MIT
- AlicenseNot gradedqualityDmaintenanceProvides full CRUD access to Pipedrive CRM API, enabling Claude and other LLM applications to manage deals, persons, organizations, activities, notes, and leads with advanced filtering and fuzzy search capabilities.9576MIT
- FlicenseBqualityDmaintenanceEnables AI assistants to autonomously interact with Kommo CRM, providing tools for managing pipelines, leads, contacts, and custom fields via the Kommo API v4.271-
TDQS
Scored across 56 tools
Each tool targets a distinct entity and action, with clear prefixes and suffixes. Even the many reference list tools (e.g., ploomes_contacts_types_list vs ploomes_contacts_status_list) are unambiguously differentiated by their entity and purpose.
All tools follow a consistent ploomes_{entity}_{action} pattern in lowercase snake_case. Actions are standard CRUD verbs (create, delete, get, list, update) plus specific actions (win, lose, reopen, finish). No mixing of conventions.
With 56 tools, the server covers multiple CRM entities (contacts, deals, tasks, products, orders, quotes, etc.) and their reference data. Each tool has a clear purpose, and the count reflects the complexity of a full CRM API without being bloated.
Core CRUD operations are covered for main entities, and reference data is well-supported. However, there are notable gaps: no tools for managing line items within orders/quotes, attachments, or pipeline creation/update, which limits the ability to perform complete CRM workflows.