HubSpot MCP
Related Servers
Alternatives to HubSpot MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive HubSpot CRM integration through the Model Context Protocol with 15+ tools for managing contacts, companies, and deals. Supports multiple transport protocols (HTTP, SSE, STDIO) with session management and real-time access to CRM data.3MIT
- 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.100MIT
- AlicenseNot gradedqualityDmaintenanceEnables advanced HubSpot CRM operations including unlimited record extraction, duplicate detection and merging, property drift analysis, and bulk upserts, surpassing official API limits.MIT
- 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.1001MIT
- 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.100MIT
- AlicenseAqualityCmaintenanceExposes HubSpot CRM data and actions as tools for AI agents, enabling contact lookup, company search, contact creation, and activity logging via natural language.4MIT
TDQS
Scored across 6 tools
The search → get_endpoint → invoke_endpoint pipeline has clearly staged, non-overlapping purposes, and capabilities/graphql are distinct. The main fuzziness is between hubspot_invoke_endpoint, hubspot_graphql_query and hubspot_api_request, which are all ways to execute calls; descriptions mitigate this by recommending the dedicated path and marking api_request as an escape hatch, but an agent could still pick the wrong one.
All six tools share the hubspot_ prefix and snake_case, and four follow a clean verb_noun pattern (search_endpoints, get_endpoint, invoke_endpoint, get_capabilities). The two exceptions, hubspot_graphql_query and hubspot_api_request, are noun phrases rather than verb-first, a minor deviation that remains readable.
Six tools is exactly right for a gateway that fronts 687 underlying endpoints — a small, well-earned surface that avoids flooding the agent with individual tools. Each tool has a distinct role in the discovery, inspection, invocation or capability-checking workflow.
The set covers the full lifecycle: discovery (search), schema inspection (get_endpoint), execution (invoke_endpoint), access/permission reporting (get_capabilities), plus GraphQL for multi-object reads and a raw HTTP escape hatch for unregistered or beta endpoints. No obvious dead ends remain for reaching any HubSpot API capability.