# HubSpot MCP connector

HubSpot brings AI tools to Elaichi for contacts, companies, deals and tickets. Connect the portal once, then Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client works the CRM inside the permissions each person already has.

Source: https://elaichi.ai/connectors/hubspot/

## Facts

| | |
| --- | --- |
| Application | HubSpot |
| Category | CRM |
| AI tools | 284 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once HubSpot is connected

- List HubSpot companies created this week with no owner.
- Which HubSpot contacts at Acme have no recent activity?
- Merge the duplicate HubSpot contacts for Northwind Trading.

## Connect HubSpot in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick HubSpot.
2. Optionally set Share with, then press Connect.
3. Supply your own HubSpot app, then approve. HubSpot needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which HubSpot tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## HubSpot MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## HubSpot MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## HubSpot MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## HubSpot MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## HubSpot MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect HubSpot to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a HubSpot tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with HubSpot through Elaichi

### Ask pipeline questions in plain language

Sales. Which companies came in this week with no owner, which contacts have gone quiet, what is closing this month. Every answer is scoped to what that person can already see in HubSpot.

### Clean up duplicates without a spreadsheet

Revenue Operations. Ask for the duplicates, then merge them. Merging is not something you can step back from, so most teams keep it to the people who own data quality and leave it off everyone else.

### Log the call from wherever it happened

Sales. Notes, tasks and calls written back without anyone opening a browser tab. Who ran it and which record it touched are both recorded.

### Give Support customer context without CRM seats

Support. Who this customer is and what they have open, for people who need the background but were never going to work deals.

### Keep Finance read-only on closed deals

Finance. Finance can look at anything they need and change none of it. Two layers do that: the tools they are given, and a rule that holds whatever anyone builds later.

### Take mass deletion off the table

Revenue Operations. HubSpot can delete records in bulk, and it does not ask twice. Make that unavailable and a persuasive prompt has nothing to reach for.

## Elaichi vs Zapier MCP vs Composio for HubSpot

All three can connect HubSpot to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over HubSpot tools | Allow or restrict single HubSpot tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per HubSpot call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect HubSpot to Claude?

Two steps. In Elaichi, add HubSpot and sign in to your portal, picking the portal on HubSpot's own screen if you have more than one. Then in Claude open Customize, then Connectors, press Add, and paste https://api.elaichi.ai/mcp as the MCP server URL. You do not need your own HubSpot app, a client ID or a secret.

### Does HubSpot work with ChatGPT and Cursor as well as Claude?

Yes. The same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. Connect HubSpot once in Elaichi and each person reaches it from whichever client they already use.

### What can an AI agent actually do with my HubSpot data?

Look up and update HubSpot contacts, companies, deals and tickets, log notes, calls and meetings, work through lists, and merge duplicate records. Teams mostly use it to catch up a deal after a call, prepare for a meeting from the record, or clean up data that has drifted.

### Can I stop an agent from deleting or mass-changing CRM records?

Yes. Restrictions work per action, so the HubSpot delete and batch-delete tools can be restricted on every role except the ones that should have them. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but only the people you allowed can run it, however persuasive the prompt.

### Can Sales and Support share one HubSpot connection but see different tools?

Yes. One HubSpot connection can be shared with several teams, and each team gets its own set of tools. Sales might get deals and contacts with writes; Support might get tickets read-only. Both run on the same connection and both are logged against the person, not the connection.

### Why does my AI client stop showing the HubSpot tool names?

Connected tools are never listed one by one, however few there are: clients get a search-and-run pair instead, even for a connector as large as HubSpot. Nothing is lost, but the client now finds tools by searching, and that search matches words rather than meaning. Short, concrete asks like "create deal" or "list open tickets" work; a long sentence about what you are trying to achieve does not.

### What happens to a HubSpot connection when the person who set it up leaves?

Offboard them in Elaichi and their own access ends at once. A connection they shared with a team keeps working, so the CRM does not go dark mid-quarter. Disconnecting HubSpot in Elaichi removes it from every client for everyone, in one action.

### Does the HubSpot MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. HubSpot is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for HubSpot?

Yes. Both let Claude, ChatGPT or Cursor use HubSpot. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every HubSpot call.

### How is Elaichi different from Composio for HubSpot?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to HubSpot: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 284 HubSpot tools

Every tool below is callable through https://api.elaichi.ai/mcp once HubSpot is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all HubSpot contacts** (List). List HubSpot contacts with control over which properties and associations are returned. Returns each contact with id, properties, createdAt, updatedAt, archived, associations, and leadid. Max 100 per page.
- **Get single HubSpot contact by ID** (Get). Get a single HubSpot contact by id. Returns the contact object including id, properties, createdAt, updatedAt, archived, and associations. Required: id.
- **Create a HubSpot contact** (Create). Create a new contact in HubSpot with the given properties and optional associations. Returns: id, properties, createdAt, updatedAt, archived. Required: properties.
- **Update a HubSpot contact by ID** (Update). Update a HubSpot contact by id with a partial set of property values. Provided values are overwritten; read-only and non-existent properties are ignored; pass an empty string to clear a property. Returns: id, properties, createdAt, updatedAt, archived. Required: id, properties.
- **Delete a HubSpot contact by ID** (Delete). Archive a HubSpot contact by moving it to the recycling bin. Returns an empty 204 response on success. Required: id.
- **HubSpot contacts merge** (Merge). Merge two HubSpot contacts by specifying a primary contact and a secondary contact to merge into it. Returns the resulting merged contact object including id, properties, createdAt, and updatedAt. Required: primaryId, idToMerge.
- **HubSpot contacts batch delete** (Delete). Archive (delete) a batch of HubSpot contacts by their IDs in a single request. Returns an empty 204 response on success. Required: inputs.
- **List all HubSpot companies** (List). List HubSpot companies with control over which properties and associations are returned. Returns: id, properties, createdAt, updatedAt, archived, associations.
- **Get single HubSpot company by ID** (Get). Get a single HubSpot company by id, or by a unique property value when idProperty is specified. Returns: id, properties, createdAt, updatedAt, archived, associations, status, message, errorType, correlationId, policyName, requestId. Required: id.
- **HubSpot companies search** (Search). Search HubSpot companies by filtering on properties, searching through associations, and sorting results. Returns: id, properties, createdAt, updatedAt, archived. Requires a search request body.
- **Update a HubSpot company by ID** (Update). Update a HubSpot company by id with provided property values. Returns: id, properties, createdAt, updatedAt, archived, status, message, errorType, correlationId, policyName, requestId. Required: id. Read-only and non-existent properties cause errors; pass an empty string to clear a value.
- **Create a HubSpot company** (Create). Create a single HubSpot company with property values and optional associations to other CRM records. Returns: id, properties, createdAt, updatedAt, archived, status, message, errorType, correlationId, policyName, requestId. Required: properties.
- **Delete a HubSpot company by ID** (Delete). Delete a HubSpot company by id. Deleted companies can be restored within 90 days of deletion. Returns an empty 204 response on success. Required: id.
- **HubSpot companies merge** (Merge). Merge two HubSpot company records by specifying a primary company and a second company to merge into it. Returns the resulting merged company object including id, properties, createdAt, and updatedAt. Required: primaryObjectId, objectIdToMerge.
- **HubSpot companies batch delete** (Delete). Archive (delete) a batch of HubSpot companies by ID. Returns an empty 204 response on success. Required: inputs (an array of company ID objects). Deleted companies can be restored within 90 days of deletion.
- **List all HubSpot users** (List). List HubSpot account users from the Settings v3 user provisioning API. Returns each user's id, email, firstName, lastName, roleId, superAdmin, primaryTeamId, secondaryTeamIds, createdAt, and updatedAt. No required parameters; pagination is handled automatically.
- **Get single HubSpot user by ID** (Get). Get a single HubSpot user by id. The id refers to the user's ID by default. Returns: id, email. Required: id.
- **Delete a HubSpot user by ID** (Delete). Delete a HubSpot user by id. The id refers to the user's ID by default, or optionally the user's email address when idProperty is set to EMAIL. Returns an empty 204 response on success. Required: id.
- **Update a HubSpot user by ID** (Update). Update a HubSpot user by id. The id defaults to the user's ID but can specify an email address when id_property is set to EMAIL. Returns: id, email. Required: id.
- **Create a HubSpot user** (Create). Create a new user in a HubSpot account, including role and team assignments. Returns the created user object including id, email, first name, last name, and role assignment. Required: email.
- **List all HubSpot deals** (List). List HubSpot deals, controlling which properties and associations are returned. Returns each deal with id, properties, createdAt, updatedAt, archived, and associations. Using propertiesWithHistory reduces the maximum number of objects returned per page.
- **Get single HubSpot deal by ID** (Get). Get a single HubSpot deal by id, optionally using idProperty to identify the deal by a unique property instead of the internal ID. Returns the deal object including id, properties, createdAt, updatedAt, archived, and associations. Required: id.
- **Create a HubSpot deal** (Create). Create a new HubSpot deal with the given properties and optional associations. Returns the created deal object including id, properties, createdAt, updatedAt, and archived. Required: properties.
- **Update a HubSpot deal by ID** (Update). Partially update a HubSpot deal by id, overwriting provided property values. Read-only and non-existent properties cause an error; pass an empty string to clear a value. Returns the updated deal including id, properties, createdAt, updatedAt, and archived. Required: id, properties.
- **Delete a HubSpot deal by ID** (Delete). Archive a HubSpot deal by id, moving it to the recycling bin. Returns an empty 204 response on success. Required: id.
- **List all HubSpot owners** (List). List HubSpot CRM owners, optionally filtered by email address. Returns: id, email, userId, archived, createdAt, updatedAt. Set archived to true to include only archived owners.
- **Get single HubSpot owner by ID** (Get). Get a specific HubSpot CRM owner by their owner id or userId. Returns: id, userId, email, archived. Required: id.
- **List all HubSpot notes** (List). List HubSpot CRM notes. Returns each note with id, properties, createdAt, updatedAt, archived, and associations. Use the properties and associations query parameters to control which fields are returned.
- **Get single HubSpot note by ID** (Get). Get a single HubSpot CRM note by id. Returns: id, properties, createdAt, updatedAt, archived, associations. Required: id.
- **Create a HubSpot note** (Create). Create a HubSpot CRM note with the given properties and optional associations to other CRM records. Returns: id, properties, createdAt, updatedAt, archived. Required: properties.
- **Update a HubSpot note by ID** (Update). Update a HubSpot CRM note by id with new property values. Property values can be cleared by passing an empty string; read-only and non-existent properties will result in an error. Returns: id, properties, createdAt, updatedAt, archived. Required: id, properties.
- **HubSpot notes get for contact** (Get). Search for HubSpot CRM notes associated with a specific contact. Returns each note with id, properties, createdAt, updatedAt, and archived. Required: contact_id.
- **HubSpot notes get for deal** (Get). Search for HubSpot notes associated with a specific deal by deal ID. Returns an array of note objects including id, properties, createdAt, updatedAt, and associations. Required: deal_id.
- **Delete a HubSpot note by ID** (Delete). Archive a HubSpot note by moving it to the recycling bin. Returns an empty 204 response on success. Required: id.
- **List all HubSpot tasks** (List). List HubSpot CRM tasks, controlling which properties are returned in the response. Returns each task with id, properties, createdAt, updatedAt, archived, and associations.
- **Get single HubSpot task by ID** (Get). Get a single HubSpot CRM task by id. The id refers to the internal object ID by default, or optionally a unique property value when idProperty is supplied. Returns: id, properties, createdAt, updatedAt, archived, associations. Required: id.
- **Create a HubSpot task** (Create). Create a task in HubSpot CRM with the given properties and optional associations. Returns the created task object including id, properties, createdAt, updatedAt, and archived. Required: properties.
- **Update a HubSpot task by ID** (Update). Update a HubSpot CRM task by id with a partial set of property values. Returns: id, properties, createdAt, updatedAt, archived. Required: id. Read-only and non-existent properties will cause an error; clear a value by passing an empty string.
- **HubSpot tasks get for contact** (Get). Search HubSpot CRM tasks associated with a specific contact. Returns: id, properties, createdAt, updatedAt, archived. Required: contact_id.
- **Delete a HubSpot task by ID** (Delete). Delete a HubSpot task by id. The task moves to the recycling bin. Returns an empty response on success.
- **List all HubSpot calls** (List). List a page of HubSpot CRM calls. Control which properties and associations are returned via query parameters. Returns: id, properties, createdAt, updatedAt, archived, associations.
- **Get single HubSpot call by ID** (Get). Get a single HubSpot CRM call by its internal object id. Control which properties are returned via the properties query param. Returns: id, properties, createdAt, updatedAt, archived, associations. Required: id.
- **Create a HubSpot call** (Create). Create a HubSpot CRM call with the given properties and optional associations. Returns: id, properties, createdAt, updatedAt, archived. Required: properties.
- **Update a HubSpot call by ID** (Update). Partially update a HubSpot CRM call identified by id. Provided property values are overwritten; read-only and non-existent properties cause errors; pass an empty string to clear a value. Returns: id, properties, createdAt, updatedAt, archived. Required: id.
- **HubSpot calls batch read** (Action). Read a batch of HubSpot CRM calls by their internal object IDs in a single request. Returns: id, properties, createdAt, updatedAt, archived. Required: inputs.
- **HubSpot calls search** (Search). Search for HubSpot calls by filtering on properties, searching through associations, and sorting results. Returns matching call records including id, properties, createdAt, and updatedAt. Required: a search request body with filter groups and/or sorting criteria.
- **List all HubSpot emails** (List). Read a page of emails in HubSpot. Returns fields including id, createdAt, updatedAt, archived status, properties, propertiesWithHistory, and associations.
- **Get single HubSpot email by ID** (Get). Get information about a specific email in HubSpot by id. Returns email properties, associations, and archived status as specified.
- **Create a HubSpot email** (Create). Create an email in HubSpot with given properties. Returns the created email's id, createdAt, updatedAt, archived status, properties, and propertiesWithHistory.
- **Update a HubSpot email by ID** (Update). Update an email object identified by id in HubSpot. Provide properties to overwrite existing values. Read-only and non-existent properties will cause errors. Properties can be cleared by passing an empty string.
- ...and 234 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
