HubSpot CRM MCP Server
Related Servers
Alternatives to HubSpot CRM MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables interaction with HubSpot CRM through MCP, providing tools to manage contacts, companies, deals, and search/associations via natural language.18573 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with HubSpot CRM data by creating contacts and companies, retrieving activity and recent conversations, and performing semantic search across previously retrieved records with built-in caching and vector storage.-
- AlicenseAqualityCmaintenanceExposes HubSpot CRM data and actions as tools for AI agents, enabling contact lookup, company search, contact creation, and activity logging via natural language.4573 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with HubSpot CRM data, including creating contacts and companies, retrieving activity and conversations, and performing semantic search over previously retrieved data. It includes vector storage and caching to improve response times and address HubSpot API limitations.-
- AlicenseBqualityDmaintenanceEnables AI models to interact with HubSpot CRM data and operations through a standardized interface, supporting contact and company management.16129MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to author HubSpot automation end-to-end through MCP, including building workflows, setting enrollment criteria, wiring steps, defining goal criteria, and managing contact lists, with every mutation verified by reading state back.MIT
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action: contacts, deals, pipelines, or audit log. Overlapping search/get/list tools are clearly separated with explicit guidance on when to prefer each.
All tools follow a consistent crm_verb_noun pattern with snake_case throughout. The compound verb 'batch_create' fits the convention as cleanly as simple verbs like 'search' or 'list'.
15 tools is right at the upper bound of the ideal 3-15 range. The count matches the server's stated CRM scope: two primary objects (contacts, deals) plus supporting pipelines and audit coverage.
Contacts have full search/list/get/create/update/delete/batch-create coverage. Deals lack a list-all-deals counterpart to crm_list_contacts, though search can approximate it. Pipeline and audit support are adequate. Minor gap only.