HubSpot API: 1,000+ endpoints as safety-categorized, hub- and plan-aware MCP tools, stdio or HTTP.
HubSpot is an MCP integration. HubSpot API: 1,000+ endpoints as safety-categorized, hub- and plan-aware MCP tools, stdio or HTTP.
The published oci package is ghcr.io/ohneben/hubspot-mcp:2.0.1. Its declared MCP transport is stdio.
The package declares MCP_TRANSPORT (required): Server transport. Set to 'stdio' for local MCP clients; the image otherwise starts the Streamable HTTP transport.; HUBSPOT_ACCESS_TOKEN (required): HubSpot service key or legacy private app token (pat-...), from Settings -> Integrations. An OAuth access token also works.; HUBSPOT_BASE_URL: API host. Default https://api.hubapi.com; use https://api-eu1.hubapi.com for EU data residency portals.; HUBSPOT_TOOL_MODE: 'discovery' (default) exposes 3 meta-tools that search, inspect and call all 1,076 endpoints; 'all' exposes the ~690 endpoint tools directly.; HUBSPOT_READ_ONLY: Set to 'true' to expose only read-only tools.; HUBSPOT_CAPABILITY_CHECK: Read the token's scopes and probe paid-tier or beta API groups at startup (read-only, up to about 30 API calls). Set to 'false' to skip.; MCP_AUTH_TOKEN: Only for MCP_TRANSPORT=http: bearer token required on /mcp. Without it a non-loopback bind refuses to start..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository · Project website. This profile uses version 2.0.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related productivity & project management MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| MCP_TRANSPORT | Server transport. Set to 'stdio' for local MCP clients; the image otherwise starts the Streamable HTTP transport. | Yes |
| HUBSPOT_ACCESS_TOKEN | HubSpot service key or legacy private app token (pat-...), from Settings -> Integrations. An OAuth access token also works. | Yes |
| HUBSPOT_BASE_URL | API host. Default https://api.hubapi.com; use https://api-eu1.hubapi.com for EU data residency portals. | Optional |
| HUBSPOT_TOOL_MODE | 'discovery' (default) exposes 3 meta-tools that search, inspect and call all 1,076 endpoints; 'all' exposes the ~690 endpoint tools directly. | Optional |
| HUBSPOT_READ_ONLY | Set to 'true' to expose only read-only tools. | Optional |
| HUBSPOT_CAPABILITY_CHECK | Read the token's scopes and probe paid-tier or beta API groups at startup (read-only, up to about 30 API calls). Set to 'false' to skip. | Optional |
| MCP_AUTH_TOKEN | Only for MCP_TRANSPORT=http: bearer token required on /mcp. Without it a non-loopback bind refuses to start. | Optional |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.