HubSpot MCP
Related Servers
Alternatives to HubSpot MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceMCP server for HubSpot CRM — 33 tools covering contacts, companies, deals, pipelines, lists, marketing emails, forms, workflows, and properties.3014 npmMIT
- AlicenseAqualityDmaintenanceEnables interaction with HubSpot CRM through MCP, providing tools to manage contacts, companies, deals, and search/associations via natural language.18480 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
- 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
- FlicenseCqualityCmaintenanceAn independent MCP server built from HubSpot's OpenAPI specs, offering 106 tools for CRM automation including contacts, companies, deals, invoices, and line items.1001-
- 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
TDQS
Scored across 112 tools
Tools are well-differentiated by resource type (calls, emails, CRM objects, etc.) and action (create, get, update, archive, search), with clear boundaries. Minor ambiguity exists between 'list' and 'search' operations across resources, but descriptions clarify that 'list' retrieves all with optional filtering while 'search' uses specific filters, making them distinguishable.
Naming follows a highly consistent pattern throughout: resource_action (e.g., calls_create, crm_get_company) with batch operations as resource_batch_action (e.g., emails_batch_update). This verb_noun structure is uniformly applied across all 112 tools, making them predictable and easy to parse.
With 112 tools, the count is excessive for a single server, leading to cognitive overload and potential inefficiency. While the tools cover multiple HubSpot domains (CRM, communications, engagements), the sheer volume suggests over-fragmentation, such as having separate batch and single operations for each resource, which could be streamlined.
The tool set provides comprehensive CRUD and lifecycle coverage across all major HubSpot domains (calls, emails, CRM objects, engagements, meetings, notes, products, tasks). Each resource includes create, get, update, archive, list, and search operations, with batch variants for scalability, ensuring no obvious gaps for agent workflows.