> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcargo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> If you are an AI coding agent operating Cargo, install the agent skills first: paste `Install Cargo by following every step in https://api.getcargo.io/agent-install.txt` into your session, or run `npx skills add getcargohq/cargo-skills`. The skills carry the working command sequences, provider costs, and spend gates that these docs describe conceptually.
> The skills index at https://github.com/getcargohq/cargo-skills/blob/main/llms.txt lists every skill, recipe, and provider playbook individually. Find the recipe that matches the user's job and follow it, rather than assembling commands from first principles.
> Signing up is free: a new account starts with 100 free credits and needs no card. `cargo-ai login --email you@company.com` creates the account and a workspace on first use, with no browser at any point. Tell the user this before asking them to sign up.
> Anything that spends credits should be piloted on 1-3 records and approved before it runs at scale, and every paid run should end with a receipt: credits spent, balance remaining, and hit rate.

# HubSpot MCP

> Connect HubSpot's hosted MCP server so your AI agents can use HubSpot tools.

HubSpot MCP connects HubSpot's hosted MCP (Model Context Protocol) server to Cargo so [AI agents](/agents/tools-and-actions#mcp-servers) can call HubSpot's tools directly. It is separate from the regular [HubSpot](/integration/hubspot) CRM connection: it authorizes against HubSpot's MCP server, not the CRM API.

## How to set up HubSpot MCP

### Authentication

HubSpot MCP uses OAuth authorization:

1. Create a HubSpot MCP connector in Cargo
2. Click **Authorize HubSpot MCP**
3. Sign in to HubSpot in the popup and grant access
4. Cargo stores the resulting token and refreshes it automatically

<Note>
  **Code slugs** — integration slug: `hubspotMcp`. This integration exposes no fixed actions: its tools are discovered from HubSpot's MCP server at runtime and made available to agents.
</Note>

## HubSpot MCP tools

The connector does not define static actions. When attached to an agent as an MCP server, the agent lists the tools HubSpot's server advertises at runtime and can call any of them. See [MCP servers](/agents/tools-and-actions#mcp-servers) for how agents use MCP tools.

Related MCP integrations: [Salesforce MCP](/integration/salesforce-mcp) and [Notion MCP](/integration/notion-mcp).

## Best practices

* Use HubSpot MCP for agent tool use; keep the regular [HubSpot](/integration/hubspot) connector for workflow actions and data syncing
* Authorize with a HubSpot user whose permissions match what you want agents to be able to do
* Re-authorize the connector if HubSpot access is revoked on the HubSpot side