@kemosoft/mcp-heymax-crm
Related Servers
Alternatives to @kemosoft/mcp-heymax-crm
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA read-only MCP server providing structured access to CRM data (companies, contacts, deals, activities) backed by SQLite. It enables LLMs to search contacts and deals, view full company accounts, find stale deals, and get pipeline summaries.-
- AlicenseAqualityDmaintenanceA read-only MCP server that exposes HubSpot CRM data (contacts, deals, companies, quotes) to AI agents, enabling natural language queries.9MIT
- FlicenseNot gradedqualityCmaintenanceMCP server to query Microsoft Dynamics 365 CRM records and support workflows using streamable HTTP transport.-
- FlicenseNot gradedqualityCmaintenanceRead-only MCP foundation server for NewCrm CRM, exposing a single /mcp endpoint and currently supporting GET /api/leads via the existing backend API without direct MongoDB access.-
- AlicenseNot gradedqualityDmaintenanceUniversal MCP server for Pipedrive, enabling interaction with Pipedrive's tools and services through a standardized API.1MIT
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server that exposes the Poli Júnior Pipedrive CRM to Claude as composable tools.-
TDQS
Scored across 10 tools
Each tool targets a distinct action or resource, but two tools retrieve pipeline data (list_active_pipelines vs get_pipeline_flow) and two fetch service status by different keys, which could cause slight confusion. The descriptions help differentiate them, so the overlap is minor.
All tools share the 'heymax_crm_' prefix and follow a consistent snake_case verb_noun pattern (e.g., list_, get_, find_, validate_). The verb variations are appropriate to each action, maintaining predictable naming throughout.
With 10 tools, the set is well-scoped for a CRM integration, covering metadata listing, validation, lookup, and status retrieval without bloat. Each tool appears to earn its place.
The surface is largely read-only: it can list metadata, validate phone numbers, search addresses, and fetch service status, but lacks operations to create, update, or delete service records, tags, or pipelines. This leaves notable gaps for a CRM integration, though core read workflows are covered.