Agent MCP Directory

HubSpot: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for HubSpot at mcp.hubspot.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

CompanyHubSpot
Domainhubspot.com
CategoryCRM (Ora leaderboard category)
MCP serverSign-in required (OAuth without client registration)
Tranco rank259 on the list of 4 November 2026
Ora score72, grade B; Ora scanned the domain on 3 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for hubspot.com, a vendor-published score)
Company found throughthe vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard
Last verified4 November 2026

MCP server

Endpointhttps://mcp.hubspot.com
How it was foundlisted in the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:01 UTC
Handshake time742 ms over 1 attempt
Documentationdevelopers.hubspot.com

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:55:53Z https://mcp.hubspot.com sent initialize result auth-required (HTTP 401) 632 ms
  • 20:01:28Z https://mcp.hubspot.com sent initialize result auth-required (HTTP 401) 742 ms

Authentication

Auth typeOAuth without client registration
What the challenge saidBearer resource_metadata="https://mcp.hubspot.com/.well-known/oauth-protected-resource"
Protected resource metadatamcp.hubspot.com
Authorization server metadatamcp.hubspot.com
Auth as listed by a registryAPI Key (a claim, not checked by connecting)

The sign-in route, step by step

  1. Request https://mcp.hubspot.com without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the OAuth metadata at https://mcp.hubspot.com/.well-known/oauth-authorization-server. It lists no registration endpoint.
  3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one.
  4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

Package@hubspot/cli on npm (page)
Existsyes
Latest version8.18.0
Last publish27 October 2026
Command nameshs, hscms
Checked4 November 2026

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileNot found (the crawl got a non-200 answer).
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Not found (the crawl got a non-200 answer).
agents.jsonNot found (the crawl got a non-200 answer).
OAuth authorization server metadataNot found (the crawl got a non-200 answer).
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryNo
GitHub MCP RegistryNo
awesome-remote-mcp-serversYes
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.