--- title: "HubSpot Deals MCP server for AI agents - actionlake" description: "Give Claude 153 HubSpot Deals actions through one MCP server: engagements, metadata, deals. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/hubspot-deals updated: 2026-10-10 --- Connectors · CRM & sales # HubSpot Deals MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to HubSpot Deals and the rest of your systems. It gives your agent 153 HubSpot Deals actions (53 reads, 68 writes and 32 that wait for a confirmation) and holds the HubSpot Deals credential itself, so the agent never does. It paces HubSpot Deals's limits and records every call. Connecting HubSpot Deals needs your own HubSpot Deals OAuth app and one admin sign-in. [Connect HubSpot Deals free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "hubspot_deals.deals.list", intent: "check which HubSpot Deals account is connected" } # List HubSpot deals · read · 1 upstream call ``` - 153 actions in one signed file - 53 read look, never change - 68 write create and update - 32 wait for a yes destructive, confirmed first Set up ## Connect HubSpot Deals in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect HubSpot Deals. OAuth 2.0, authorization code with PKCE. You register your own OAuth app with HubSpot Deals, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key. Before the first sign-in, HubSpot Deals needs an OAuth app of your own, registered in its developer portal. actionlake has no HubSpot Deals app to lend you. - `access_token` Access token from one sign-in with your own OAuth app - `refresh_token` Refresh token from the same sign-in; the access token is renewed from it - `client_id` HubSpot app client id - `client_secret` HubSpot app client secret ``` account { op: "connections.requirements", service: "hubspot_deals" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "hubspot_deals.deals.list" } # list hubspot deals · read · 1 upstream call check { action: "hubspot_deals.deals.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` HubSpot Deals at a glance **Sign-in** OAuth 2.0, authorization code with PKCE. You register your own OAuth app with HubSpot Deals, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. **You provide** `access_token` `refresh_token` `client_id` `client_secret` **Limits we pace to** 110 calls per 10 seconds and 5 a second, per connection **API covered** HubSpot Deals API v3`api.hubapi.com` **Built from** HubSpot Deals's documentation, read 15 September 2026[api.hubspot.com](https://api.hubspot.com/public/api/spec/v1/specs) [developers.hubspot.com](https://developers.hubspot.com/docs/reference/api/crm/objects/deals) **Service file** Version 2.0.0, signed (Ed25519) **Cached reads** 51 of 53 reads, for up to an hour; a write clears what it affects **Ready-made plans** 8 in the store **Shared entities** 6, so ask can line HubSpot Deals up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in HubSpot Deals. 153 actions in 6 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **53** read look, never change - **68** write create and update - **32** destructive wait for a confirmation 1. ### Engagements 70 20 read · 35 write · 15 destructive List HubSpot notes · List HubSpot meetings · List HubSpot calls · List HubSpot tasks 2. ### Metadata 29 13 read · 11 write · 5 destructive List HubSpot owners · List HubSpot deal pipelines · List the stages of a HubSpot deal pipeline · Get one HubSpot owner 3. ### Deals 16 5 read · 8 write · 3 destructive List HubSpot deals · Create a batch of HubSpot deals · Create a HubSpot deal · Get one HubSpot deal 4. ### Line items 14 4 read · 7 write · 3 destructive List HubSpot line items · Create a batch of HubSpot line items · Read a batch of HubSpot line items · Create a HubSpot line item 5. ### Associations 13 3 read · 6 write · 4 destructive Read associations for a batch of deals · List a deal's associations · List the association labels available from deals · Remove associations for a batch of deals 6. ### Bulk 11 8 read · 1 write · 2 destructive Inspect a HubSpot refresh token · Inspect a HubSpot access token · List HubSpot object schemas · List HubSpot import jobs HubSpot's own MCP server ## HubSpot's MCP server, or actionlake? HubSpot runs a remote MCP server for CRM data, deals included, at mcp.hubspot.com, signed in with OAuth, and a separate local developer MCP server in its CLI. Use HubSpot's server when one person wants to work in HubSpot Deals from their own AI client. Use actionlake when you also want HubSpot Deals behind the same endpoint as your other systems: a key per agent with allowed actions and a spending cap, a named person's approval before destructive actions, a sealed record of every call, and one ask across HubSpot Deals and another system. Source: [HubSpot's documentation](https://developers.hubspot.com/mcp), checked 22 October 2026. Top actions ## The HubSpot Deals API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 92 of HubSpot Deals's 94 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `hubspot_deals.deals.list` List HubSpot deals | Page through every deal in the portal, newest ids first. | read | `crm.deal.list` 43 connectors | | `hubspot_deals.notes.list` List HubSpot notes | Page through every note in the portal, newest ids first. | read | `crm.contact_note.list` 29 connectors | | `hubspot_deals.meetings.list` List HubSpot meetings | Page through every meeting in the portal, newest ids first. | read | `comm.event.list` 61 connectors | | `hubspot_deals.calls.list` List HubSpot calls | Page through every call in the portal, newest ids first. | read | `comm.call.list` 44 connectors | | `hubspot_deals.tasks.list` List HubSpot tasks | Page through every task in the portal, newest ids first. | read | `work.task.list` 122 connectors | | `hubspot_deals.emails.list` List HubSpot emails | Page through every email in the portal, newest ids first. | read | `comm.email.list` 28 connectors | | `hubspot_deals.deals.create` Create a HubSpot deal | Create one deal, optionally associating it to existing records as it is made. | write | `crm.deal.create` 43 connectors | | `hubspot_deals.deals.batch_create` Create a batch of HubSpot deals | Create up to 100 deals in one call. | write | `crm.deal.create` 43 connectors | | `hubspot_deals.line_items.list` List HubSpot line items | Page through every line item in the portal, newest ids first. | read | `crm.deal_line.list` 5 connectors | | `hubspot_deals.notes.batch_read` Read a batch of HubSpot notes | Fetch up to 100 notes in one call, by HubSpot id or by a unique property. | read | `crm.contact_note.list` 29 connectors | | `hubspot_deals.deals.archive` Archive a HubSpot deal | Move one deal to the recycling bin. Recoverable in the UI for 90 days. | destructive | `crm.deal.delete` 38 connectors | | `hubspot_deals.tasks.create` Create a HubSpot task | Create one task, optionally associating it to existing records as it is made. | write | `work.task.create` 127 connectors | Try it ## Prompts to paste into Claude. Each one names the HubSpot Deals actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which HubSpot Deals deals are due to close this month, and what are they worth in total? calls `hubspot_deals.deals.list` 2. Plan write Mark a deal won and hand it to delivery in HubSpot Deals. Ask me before anything is sent or changed. calls `hubspot_deals.deals.get` `hubspot_deals.associations.list` `hubspot_deals.deals.update` `hubspot_deals.notes.create` `hubspot_deals.tasks.create` 3. Plan write Report open deal coverage by stage and owner in HubSpot Deals. calls `hubspot_deals.pipelines.get` `hubspot_deals.pipeline_stages.list` `hubspot_deals.owners.list` `hubspot_deals.deals.search` `hubspot_deals.notes.create` 4. Write write Create a HubSpot deal in HubSpot Deals. Show me exactly what you will send before you save it. calls `hubspot_deals.deals.create` The plan store ## Ready-made plans for HubSpot Deals. 8 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design. 1. ### Create follow-up tasks for stale open deals Use it when A rep or manager wants every quiet open deal to get a follow-up task created automatically. **Effect** write **Steps** 3 · loops **Needs** due at, owner id and stage **Install** `hubspot_deals-stale-deal-followup-tasks` 2. ### Open a deal and attach its line items Use it when A rep wants a new deal opened together with its priced line items in one step. **Effect** write **Steps** 5 · loops **Needs** amount, line items, name, pipeline id and stage **Install** `hubspot_deals-new-deal-with-line-items` 3. ### Mark a deal won and hand it to delivery Use it when A rep is closing a deal as won and delivery needs the handoff logged in one pass. A person decides Close _dealname_ as won at _amount_ and hand it to delivery. **Effect** write **Steps** 6 **Needs** delivery owner id, kickoff at, record id and won stage **Install** `hubspot_deals-close-won-handoff` 4. ### Export deals and wait for the file Use it when Someone needs a deal export kicked off and confirmed finished rather than fired and forgotten. **Effect** write **Steps** 6 **Needs** export type, format and export name **Install** `hubspot_deals-export-deals-and-wait` 5. ### Report open deal coverage by stage and owner Use it when A manager asks for a written snapshot of what is currently sitting in a pipeline. **Effect** write **Steps** 6 **Needs** pipeline id **Install** `hubspot_deals-pipeline-health-report` 6. ### Reassign a departing owner's open deals Use it when A rep is leaving or changing patch and their open deals must move to someone else. A person decides Move _move count_ open deals from _email_ to _email_. **Effect** write **Steps** 6 · loops **Needs** from owner id, to owner id and reason **Install** `hubspot_deals-reassign-owner-deals` 7. ### Archive abandoned test deals after sign-off Use it when Someone wants to clean test or junk deals out of a pipeline with a human signing off first. A person decides Archive _junk count_ deals matching '_query_'. This hides them from every pipeline view. **Effect** destructive **Steps** 5 **Needs** approver and query **Install** `hubspot_deals-archive-junk-deals` 8. ### Merge a duplicate deal into the surviving record Use it when Two deals describe the same opportunity and one must be folded into the other. A person decides Merge '_dealname_' into '_dealname_'. The merged deal cannot be recovered. **Effect** destructive **Steps** 6 **Needs** merge id and primary id **Install** `hubspot_deals-merge-duplicate-deals` install a plan ``` account { op: "plans.install", slug: "hubspot_deals-stale-deal-followup-tasks" } # then ask for it by name; a schedule can run it on a timetable ``` Governance for HubSpot Deals ## Destructive actions wait for a yes. 32 HubSpot Deals actions are destructive. The first 10: - Archive a HubSpot deal `hubspot_deals.deals.archive` - Archive a batch of HubSpot deals `hubspot_deals.deals.batch_archive` - Archive a HubSpot note `hubspot_deals.notes.archive` - Archive a batch of HubSpot notes `hubspot_deals.notes.batch_archive` - Archive a HubSpot meeting `hubspot_deals.meetings.archive` - Archive a batch of HubSpot meetings `hubspot_deals.meetings.batch_archive` - Archive a HubSpot task `hubspot_deals.tasks.archive` - Archive a batch of HubSpot tasks `hubspot_deals.tasks.batch_archive` - Archive a HubSpot line item `hubspot_deals.line_items.archive` - Archive a batch of HubSpot line items `hubspot_deals.line_items.batch_archive` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do hubspot_deals.deals.archive confirm_policy: **human** Archive a HubSpot deal? **intent:** the user asked me to archive a HubSpot deal run suspended · waiting for a named person · key _hubspot-deals-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "hubspot-deals-agent", allowed_actions: ["hubspot_deals.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "hubspot_deals.deals.archive", approver: "lead@example.com" }, { match: "hubspot_deals.deals.batch_archive", approver: "lead@example.com" }, { match: "hubspot_deals.notes.archive", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to HubSpot Deals only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What HubSpot Deals costs on actionlake. Every HubSpot Deals action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call HubSpot Deals refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 153 HubSpot Deals actions - 26 actions page each page of a long list is one call - 51 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every HubSpot Deals action. 153 actions by area: the id your agent calls, what it does, and its effect. **Engagements 70** - `hubspot_deals.calls.archive` Archive a HubSpot call destructive - `hubspot_deals.calls.batch_archive` Archive a batch of HubSpot calls destructive - `hubspot_deals.calls.batch_create` Create a batch of HubSpot calls write - `hubspot_deals.calls.batch_read` Read a batch of HubSpot calls read - `hubspot_deals.calls.batch_update` Update a batch of HubSpot calls write - `hubspot_deals.calls.batch_upsert` Create or update a batch of HubSpot calls write - `hubspot_deals.calls.create` Create a HubSpot call write - `hubspot_deals.calls.create_raw` Create a HubSpot call from a raw property map write - `hubspot_deals.calls.get` Get one HubSpot call read - `hubspot_deals.calls.list` List HubSpot calls read - `hubspot_deals.calls.merge` Merge two HubSpot calls destructive - `hubspot_deals.calls.search` Search HubSpot calls read - `hubspot_deals.calls.update` Update a HubSpot call write - `hubspot_deals.calls.update_raw` Update a HubSpot call from a raw property map write - `hubspot_deals.emails.archive` Archive a HubSpot email destructive - `hubspot_deals.emails.batch_archive` Archive a batch of HubSpot emails destructive - `hubspot_deals.emails.batch_create` Create a batch of HubSpot emails write - `hubspot_deals.emails.batch_read` Read a batch of HubSpot emails read - `hubspot_deals.emails.batch_update` Update a batch of HubSpot emails write - `hubspot_deals.emails.batch_upsert` Create or update a batch of HubSpot emails write - `hubspot_deals.emails.create` Create a HubSpot email write - `hubspot_deals.emails.create_raw` Create a HubSpot email from a raw property map write - `hubspot_deals.emails.get` Get one HubSpot email read - `hubspot_deals.emails.list` List HubSpot emails read - `hubspot_deals.emails.merge` Merge two HubSpot emails destructive - `hubspot_deals.emails.search` Search HubSpot emails read - `hubspot_deals.emails.update` Update a HubSpot email write - `hubspot_deals.emails.update_raw` Update a HubSpot email from a raw property map write - `hubspot_deals.meetings.archive` Archive a HubSpot meeting destructive - `hubspot_deals.meetings.batch_archive` Archive a batch of HubSpot meetings destructive - `hubspot_deals.meetings.batch_create` Create a batch of HubSpot meetings write - `hubspot_deals.meetings.batch_read` Read a batch of HubSpot meetings read - `hubspot_deals.meetings.batch_update` Update a batch of HubSpot meetings write - `hubspot_deals.meetings.batch_upsert` Create or update a batch of HubSpot meetings write - `hubspot_deals.meetings.create` Create a HubSpot meeting write - `hubspot_deals.meetings.create_raw` Create a HubSpot meeting from a raw property map write - `hubspot_deals.meetings.get` Get one HubSpot meeting read - `hubspot_deals.meetings.list` List HubSpot meetings read - `hubspot_deals.meetings.merge` Merge two HubSpot meetings destructive - `hubspot_deals.meetings.search` Search HubSpot meetings read - `hubspot_deals.meetings.update` Update a HubSpot meeting write - `hubspot_deals.meetings.update_raw` Update a HubSpot meeting from a raw property map write - `hubspot_deals.notes.archive` Archive a HubSpot note destructive - `hubspot_deals.notes.batch_archive` Archive a batch of HubSpot notes destructive - `hubspot_deals.notes.batch_create` Create a batch of HubSpot notes write - `hubspot_deals.notes.batch_read` Read a batch of HubSpot notes read - `hubspot_deals.notes.batch_update` Update a batch of HubSpot notes write - `hubspot_deals.notes.batch_upsert` Create or update a batch of HubSpot notes write - `hubspot_deals.notes.create` Create a HubSpot note write - `hubspot_deals.notes.create_raw` Create a HubSpot note from a raw property map write - `hubspot_deals.notes.get` Get one HubSpot note read - `hubspot_deals.notes.list` List HubSpot notes read - `hubspot_deals.notes.merge` Merge two HubSpot notes destructive - `hubspot_deals.notes.search` Search HubSpot notes read - `hubspot_deals.notes.update` Update a HubSpot note write - `hubspot_deals.notes.update_raw` Update a HubSpot note from a raw property map write - `hubspot_deals.tasks.archive` Archive a HubSpot task destructive - `hubspot_deals.tasks.batch_archive` Archive a batch of HubSpot tasks destructive - `hubspot_deals.tasks.batch_create` Create a batch of HubSpot tasks write - `hubspot_deals.tasks.batch_read` Read a batch of HubSpot tasks read - `hubspot_deals.tasks.batch_update` Update a batch of HubSpot tasks write - `hubspot_deals.tasks.batch_upsert` Create or update a batch of HubSpot tasks write - `hubspot_deals.tasks.create` Create a HubSpot task write - `hubspot_deals.tasks.create_raw` Create a HubSpot task from a raw property map write - `hubspot_deals.tasks.get` Get one HubSpot task read - `hubspot_deals.tasks.list` List HubSpot tasks read - `hubspot_deals.tasks.merge` Merge two HubSpot tasks destructive - `hubspot_deals.tasks.search` Search HubSpot tasks read - `hubspot_deals.tasks.update` Update a HubSpot task write - `hubspot_deals.tasks.update_raw` Update a HubSpot task from a raw property map write **Metadata 29** - `hubspot_deals.owners.get` Get one HubSpot owner read - `hubspot_deals.owners.list` List HubSpot owners read - `hubspot_deals.pipeline_stages.archive` Archive a stage in a HubSpot deal pipeline destructive - `hubspot_deals.pipeline_stages.audit` Read a HubSpot deal pipeline stage's audit trail read - `hubspot_deals.pipeline_stages.create` Create a stage in a HubSpot deal pipeline write - `hubspot_deals.pipeline_stages.get` Get one HubSpot deal pipeline stage read - `hubspot_deals.pipeline_stages.list` List the stages of a HubSpot deal pipeline read - `hubspot_deals.pipeline_stages.replace` Replace a stage in a HubSpot deal pipeline write - `hubspot_deals.pipeline_stages.update` Update a stage in a HubSpot deal pipeline write - `hubspot_deals.pipelines.archive` Archive a HubSpot deal pipeline destructive - `hubspot_deals.pipelines.audit` Read a HubSpot deal pipeline's audit trail read - `hubspot_deals.pipelines.create` Create a HubSpot deal pipeline write - `hubspot_deals.pipelines.get` Get one HubSpot deal pipeline read - `hubspot_deals.pipelines.list` List HubSpot deal pipelines read - `hubspot_deals.pipelines.replace` Replace a HubSpot deal pipeline write - `hubspot_deals.pipelines.update` Update a HubSpot deal pipeline write - `hubspot_deals.properties.archive` Archive a HubSpot deal property destructive - `hubspot_deals.properties.batch_archive` Archive a batch of HubSpot deal properties destructive - `hubspot_deals.properties.batch_create` Create a batch of HubSpot deal properties write - `hubspot_deals.properties.batch_read` Read a batch of HubSpot deal property definitions read - `hubspot_deals.properties.create` Create a HubSpot deal property write - `hubspot_deals.properties.get` Get one HubSpot deal property definition read - `hubspot_deals.properties.list` List the properties a HubSpot deal carries read - `hubspot_deals.properties.update` Update a HubSpot deal property write - `hubspot_deals.property_groups.archive` Archive a HubSpot deal property group destructive - `hubspot_deals.property_groups.create` Create a HubSpot deal property group write - `hubspot_deals.property_groups.get` Get one HubSpot deal property group read - `hubspot_deals.property_groups.list` List HubSpot deal property groups read - `hubspot_deals.property_groups.update` Update a HubSpot deal property group write **Deals 16** - `hubspot_deals.deal_splits.batch_read` Read the splits on a batch of HubSpot deals read - `hubspot_deals.deal_splits.batch_upsert` Set the splits on a batch of HubSpot deals write - `hubspot_deals.deals.archive` Archive a HubSpot deal destructive - `hubspot_deals.deals.batch_archive` Archive a batch of HubSpot deals destructive - `hubspot_deals.deals.batch_create` Create a batch of HubSpot deals write - `hubspot_deals.deals.batch_read` Read a batch of HubSpot deals read - `hubspot_deals.deals.batch_update` Update a batch of HubSpot deals write - `hubspot_deals.deals.batch_upsert` Create or update a batch of HubSpot deals write - `hubspot_deals.deals.create` Create a HubSpot deal write - `hubspot_deals.deals.create_raw` Create a HubSpot deal from a raw property map write - `hubspot_deals.deals.get` Get one HubSpot deal read - `hubspot_deals.deals.list` List HubSpot deals read - `hubspot_deals.deals.merge` Merge two HubSpot deals destructive - `hubspot_deals.deals.search` Search HubSpot deals read - `hubspot_deals.deals.update` Update a HubSpot deal write - `hubspot_deals.deals.update_raw` Update a HubSpot deal from a raw property map write **Line items 14** - `hubspot_deals.line_items.archive` Archive a HubSpot line item destructive - `hubspot_deals.line_items.batch_archive` Archive a batch of HubSpot line items destructive - `hubspot_deals.line_items.batch_create` Create a batch of HubSpot line items write - `hubspot_deals.line_items.batch_read` Read a batch of HubSpot line items read - `hubspot_deals.line_items.batch_update` Update a batch of HubSpot line items write - `hubspot_deals.line_items.batch_upsert` Create or update a batch of HubSpot line items write - `hubspot_deals.line_items.create` Create a HubSpot line item write - `hubspot_deals.line_items.create_raw` Create a HubSpot line item from a raw property map write - `hubspot_deals.line_items.get` Get one HubSpot line item read - `hubspot_deals.line_items.list` List HubSpot line items read - `hubspot_deals.line_items.merge` Merge two HubSpot line items destructive - `hubspot_deals.line_items.search` Search HubSpot line items read - `hubspot_deals.line_items.update` Update a HubSpot line item write - `hubspot_deals.line_items.update_raw` Update a HubSpot line item from a raw property map write **Associations 13** - `hubspot_deals.association_labels.create` Create an association label from deals write - `hubspot_deals.association_labels.delete` Delete an association label from deals destructive - `hubspot_deals.association_labels.list` List the association labels available from deals read - `hubspot_deals.association_labels.update` Rename an association label from deals write - `hubspot_deals.associations.batch_archive` Remove associations for a batch of deals destructive - `hubspot_deals.associations.batch_archive_labels` Remove specific association labels for a batch of deals destructive - `hubspot_deals.associations.batch_create` Associate a batch of deals using labels write - `hubspot_deals.associations.batch_create_default` Associate a batch of deals using default labels write - `hubspot_deals.associations.batch_read` Read associations for a batch of deals read - `hubspot_deals.associations.create_default` Associate a deal with another record write - `hubspot_deals.associations.create_labelled` Associate a deal with another record using a label write - `hubspot_deals.associations.delete` Remove every association between a deal and a record destructive - `hubspot_deals.associations.list` List a deal's associations read **Bulk 11** - `hubspot_deals.exports.create` Start a HubSpot CRM export write - `hubspot_deals.exports.status` Check a HubSpot export job read - `hubspot_deals.imports.cancel` Cancel a HubSpot import job destructive - `hubspot_deals.imports.errors` List the errors of a HubSpot import job read - `hubspot_deals.imports.get` Get one HubSpot import job read - `hubspot_deals.imports.list` List HubSpot import jobs read - `hubspot_deals.oauth.refresh_token_info` Inspect a HubSpot refresh token read - `hubspot_deals.oauth.revoke_refresh_token` Revoke a HubSpot refresh token destructive - `hubspot_deals.oauth.token_info` Inspect a HubSpot access token read - `hubspot_deals.object_schemas.get` Get one HubSpot object schema read - `hubspot_deals.object_schemas.list` List HubSpot object schemas read Questions ## The HubSpot Deals MCP server, answered. **Is there a HubSpot Deals MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 153 HubSpot Deals actions across engagements, metadata, deals and line items, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by HubSpot. **Does HubSpot have its own MCP server?** HubSpot runs a remote MCP server for CRM data, deals included, at mcp.hubspot.com, signed in with OAuth, and a separate local developer MCP server in its CLI. (HubSpot's documentation, checked 22 October 2026.) Use HubSpot's server when one person wants to work in HubSpot Deals from their own AI client. Use actionlake when you also want HubSpot Deals behind the same endpoint as your other systems: a key per agent with allowed actions and a spending cap, a named person's approval before destructive actions, a sealed record of every call, and one ask across HubSpot Deals and another system. **What do I need to connect HubSpot Deals?** Your own HubSpot Deals OAuth app, registered with HubSpot Deals (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no HubSpot Deals app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "hubspot_deals" } lists exactly what to paste. **Can an AI agent delete or change things in HubSpot Deals?** Only if its key allows it, and only with an explicit confirmation. 32 HubSpot Deals actions are destructive, including archive a HubSpot deal, archive a batch of HubSpot deals and archive a HubSpot note. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my HubSpot Deals API limit?** actionlake paces every call to the limits in the HubSpot Deals service file: 110 calls per 10 seconds and 5 a second per connection. Repeated reads are answered from cache (51 HubSpot Deals actions can be), which never reaches HubSpot Deals. **What does a HubSpot Deals action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (26 HubSpot Deals actions page). Cache hits, searches, dry runs and calls HubSpot Deals refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which HubSpot Deals API does it cover?** The HubSpot Deals API v3 at api.hubapi.com. It is built from HubSpot Deals's documentation as read on 15 September 2026. 153 actions in 6 areas, each one in the signed service file (version 2.0.0). **Does actionlake keep my HubSpot Deals data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your HubSpot Deals credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like HubSpot Deals Shares the most action names with - [HubSpot CRM 89](https://actionlake.com/connectors/hubspot-crm) - [Zoho CRM 46](https://actionlake.com/connectors/zoho-crm) - [Pipedrive 46](https://actionlake.com/connectors/pipedrive) - [Close 46](https://actionlake.com/connectors/close) - [Follow Up Boss 43](https://actionlake.com/connectors/follow-up-boss) - [Streak CRM for Gmail 20](https://actionlake.com/connectors/streak-crm-for-gmail) Joins with, on shared entities - [Unified.to 3](https://actionlake.com/connectors/unified-to) - [ERPNext (Frappe) 3](https://actionlake.com/connectors/erpnext-frappe) - [ScalePad 3](https://actionlake.com/connectors/scalepad) - [HaloPSA 2](https://actionlake.com/connectors/halopsa) - [Acumatica Cloud ERP 2](https://actionlake.com/connectors/acumatica-cloud-erp) - [Odoo 2](https://actionlake.com/connectors/odoo) Browse - [All CRM & sales connectors](https://actionlake.com/connectors/category/crm-and-sales) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by HubSpot; the name is the vendor's own. Counts are from the HubSpot Deals service file, version 2.0.0. ## Give your agent HubSpot Deals today. [Connect HubSpot Deals free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/hubspot-deals More: https://actionlake.com/llms.txt