HubSpot MCP
Related Servers
Alternatives to HubSpot MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceProvides comprehensive access to HubSpot's CRM API, enabling management of contacts, companies, deals, engagements, and associations with support for batch operations and advanced search capabilities.10062 npmMIT
- AlicenseCqualityDmaintenanceProvides comprehensive access to HubSpot CRM API for managing contacts, companies, deals, engagements, and associations. Supports batch operations, advanced search, and complete CRUD functionality across all standard CRM objects.10062 npmMIT
- AlicenseCqualityDmaintenanceProvides standardized access to HubSpot's CRM API for managing contacts, companies, deals, engagements, and other CRM data through comprehensive CRUD operations, batch processing, and advanced search capabilities.10062 npm1MIT
- AlicenseCqualityDmaintenanceProvides standardized access to HubSpot CRM API for managing contacts, companies, deals, leads, engagements, and associations with support for batch operations and advanced search capabilities.10062 npmMIT
- AlicenseCqualityCmaintenanceEnables interaction with HubSpot CRM through a standardized API interface. Supports managing contacts, companies, deals, engagements, products, and associations with batch operations and advanced search capabilities.10062 npmMIT
- AlicenseBqualityFmaintenanceEnables AI models to interact with HubSpot CRM data and operations through a standardized interface, supporting contact and company management.16129MIT
TDQS
Scored across 111 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource type (e.g., calls, crm, emails) and operation (e.g., create, get, update, search), making it easy for an agent to select the correct one. The batch vs. single-operation variants are clearly differentiated by naming and descriptions.
Tool names follow a highly consistent pattern throughout: resource_action (e.g., calls_create, crm_get_company) or resource_batch_action (e.g., emails_batch_update). Minor deviations like 'products_read' vs. 'products_list' are minimal and don't break the overall consistency. The naming is predictable and systematic.
With 111 tools, the count is excessive for typical MCP server purposes, making it overwhelming and difficult to navigate. While the server covers a broad CRM domain, the sheer number of tools (including many batch variants) feels heavy and could hinder agent efficiency, suggesting a need for consolidation or better scoping.
The tool set provides complete CRUD/lifecycle coverage for all major HubSpot resources (calls, communications, CRM objects, emails, engagements, meetings, notes, products, tasks). Each resource type includes create, read, update, delete, list, and search operations, with batch variants for scalability, leaving no obvious gaps for agent workflows.