> ## 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.

# Notion MCP

> Connect Notion's hosted MCP server so your AI agents can search and update your Notion workspace.

Notion MCP connects Notion's hosted MCP (Model Context Protocol) server to Cargo so [AI agents](/agents/tools-and-actions#mcp-servers) can search and update your Notion workspace. Authorization is browser-based OAuth — no Notion integration token or API key is required.

## How to set up Notion MCP

### Authentication

Notion MCP uses OAuth authorization:

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

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

## Notion MCP tools

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

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

## Best practices

* Grant access only to the Notion workspace (and pages) your agents actually need
* Authorize with a Notion user whose permissions match what you want agents to be able to do
* Re-authorize the connector if access is revoked from Notion's connected-apps settings