Skip to content

HubSpot

Artific Connect · HubSpot gives a key everything HubSpot's own remote MCP server offers this organisation's portal: contacts, deals, tickets and the rest, as one toolset. HubSpot's remote MCP server admits no application the deployment could register once — each organisation creates its own "MCP Auth App" inside its own HubSpot account — so this bundle asks the organisation for that application itself, and each person then signs in with their own HubSpot login through it. It installs from the Marketplace like any other bundle.

What you get

One toolset, hubspot, holding every tool HubSpot's server offers your portal, plus a skill that tells the model that the tool list itself depends on what your MCP Auth App and each person's own HubSpot user were granted. Every call runs as the person the turn is for, through their own HubSpot login — unlike a bundle with a deployment-wide application, nobody signs in here on the organisation's behalf.

What your HubSpot administrator sets up first

In your own HubSpot account, under Development → MCP Auth Apps, create an MCP Auth App and give it this deployment's redirect URI (<your Artific address>/api/v1/oauth/callback). HubSpot does not ask you to list scopes for it: what a signed-in person may do follows the tools the server offers at the time they connect and the permissions their own HubSpot user has, not a fixed list you configure up front.

What you supply at install

  • hubspot_app — the MCP Auth App you just created, as one credential:
{
  "type": "oauth_authorization_code",
  "authorize_url": "<your MCP Auth App's authorize URL>",
  "token_url": "<your MCP Auth App's token URL>",
  "client_id": "<your MCP Auth App's client id>",
  "client_secret": "<your MCP Auth App's client secret, if it is confidential>"
}

This is your organisation's own application, never a login: nobody's HubSpot password or grant travels here. Until it is supplied the subscription waits at needs configuration.

The first time someone uses it

Once installed, each person who calls a HubSpot tool is answered with a sign-in link the first time, through your own MCP Auth App; after that, their own grant is remembered until they revoke it or an administrator removes the application.

Before it works

Your administrator has to allow mcp.hubspot.com in the key's own egress policy — that one host is the whole of what this bundle calls, for both the tool traffic and the sign-in.

Good to know

  • Verified 2026-09-24 on developers.hubspot.com: the server address is https://mcp.hubspot.com, the transport is Streamable HTTP, and there is no static-token alternative for it — every connection goes through an MCP Auth App and a person's own sign-in.
  • Not verified: which region a given organisation's HubSpot portal, and so its data, is hosted in; HubSpot's own MCP documentation does not state one for this endpoint.
  • The mark: this bundle's card still uses Artific's own placeholder. HubSpot's Technology Partner branding guidelines require a design mockup and a 7–10 business day approval before a partner may use the HubSpot logo or sprocket, which this deployment has not sought (checked 2026-09-24).