By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect OpenClaw to HubSpot is the Ryze AI connector. Connect your portal in Ryze AI by signing in to HubSpot and approving the permissions, then save https://connector.get-ryze.ai/mcp in OpenClaw as a streamable-http server with auth set to oauth, using the CLI, Settings > MCP in the Control UI or openclaw.json. Sign in once and OpenClaw can list 5 HubSpot tools: three that read, one that writes and one that deletes.
- In Ryze AI open Integrations, click Connect on the HubSpot card, choose your portal and approve the permissions
- Save the Ryze AI server in OpenClaw with openclaw mcp set, the Control UI or openclaw.json
- Run openclaw mcp login ryze and click Allow connection
- Ask about your contacts, companies or deals
OpenClaw to HubSpot at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, saved in OpenClaw as one remote MCP server named ryze |
| Server address | https://connector.get-ryze.ai/mcp, with transport set to streamable-http |
| Sign-in | OAuth to Ryze AI with openclaw mcp login ryze, or Sign in under Settings > MCP for an administrator. A Ryze AI API key in a bearer header is the other route |
| HubSpot tools | 5: hubspot__listObjects, hubspot__search, hubspot__read, hubspot__write and hubspot__delete |
| Can it change HubSpot | Yes, through the write and delete tools. OpenClaw's docs describe no per-call prompt for its built-in runtime, so limit the tools yourself (see the approvals note below) |
| Other data in the same chat | Tools for the other platforms you connected to the same Ryze AI workspace come through the same server address |
| OpenClaw plan needed | None to buy. OpenClaw is MIT licensed and self-hosted, and its docs say it has no paid tier |
| Ryze AI price | Paid Ads is $89 per month with a 7-day free trial. Adding the connector is free |
| HubSpot's own option for OpenClaw | HubSpot's remote MCP server at https://mcp.hubspot.com. No HubSpot page opened names OpenClaw as a client, and the pairing was not run |
| HubSpot access of the default connection | 12 required scopes for contacts, companies, deals, owners, contact and deal schemas, lists and content. Tickets, custom objects and list editing are not included |
| Last tested | 11 read-only HubSpot calls through the connector on November 14, 2026. No step inside OpenClaw was run |
Before you start
- OpenClaw. It is an open-source project under the MIT license that you host yourself. You need a running Gateway and one of three things: the openclaw command on the Gateway machine, administrator access to the Control UI, or write access to the Gateway's openclaw.json.
- A HubSpot user who can install apps. HubSpot lets a Super Admin or a user with App Marketplace access install an app. Everyone else needs a Super Admin to do it. You choose the portal during the sign-in, and each connection is one portal.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial; SEO Starter is $129 per month with a 3-day free trial and covers Content Plan articles published to a HubSpot blog. Adding the connector is free, but the HubSpot tools need an active plan or trial.
- A note on testing. Ryze AI has no help-center page for OpenClaw and the OpenClaw steps were not run for this page. They follow OpenClaw's own documentation for remote servers that use OAuth, as read on November 15, 2026.
How to connect OpenClaw to HubSpot
The first two steps happen in Ryze AI and HubSpot, the next three in OpenClaw, and the last is your first prompt. The connector URL is the same for every user.
Connect your portal in Ryze AI
Create a Ryze AI account or sign in, open Integrations, find the HubSpot card and click Connect. You can also start from the Ryze AI listing in the HubSpot Marketplace.
Sign in to HubSpot and approve the permissions
Sign in to HubSpot, choose the account (portal) and click Choose Account, then approve the requested permissions. HubSpot returns you to Ryze AI with the connection saved. No API key or private app token is pasted.
Save the Ryze AI server in OpenClaw
Stop the Gateway with openclaw gateway stop, because OpenClaw 2026.10.10 (November 3, 2026) holds back CLI changes to MCP settings while a Gateway runs. Then run: openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}'. The same entry can go under mcp.servers in ~/.openclaw/openclaw.json, or be added with Add server under Settings > MCP in the Control UI while the Gateway runs.
openclaw gateway stop openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}' openclaw mcp login ryzeSign in to Ryze AI from OpenClaw
Run: openclaw mcp login ryze. A browser opens on the Ryze AI page. Sign in if asked, choose the workspace that holds HubSpot and click Allow connection, then start the Gateway again. An administrator can instead click Sign in for the ryze server under Settings > MCP.
Finish the sign-in on another machine if needed
If the browser is not on the machine that runs OpenClaw, approve the sign-in there and hand the code it returns to openclaw mcp login with the --code option.
Ask your first question
Once credentials exist, OpenClaw adds the server to the agent runtime. If you saved the connector before HubSpot was connected in Ryze AI, remove the entry and save it again so the tool list refreshes. Then ask: Search HubSpot deals created in the last 30 days and list the deal name, amount and stage.
The Ryze AI help center page for HubSpot covers the HubSpot side of the connection. OpenClaw does not have its own Ryze AI help page; the Ryze AI developers page covers the MCP URL for other clients.
Sources: OpenClaw MCP documentation, OpenClaw MCP transports, Ryze AI HubSpot guide. OpenClaw pages checked November 15, 2026.
CLI, Control UI, openclaw.json and API key
OpenClaw CLI
set writes the server definition and login runs the OAuth flow; the credentials stay on the Gateway host. Start the Gateway again afterwards. To see what is saved, openclaw mcp show ryze, list and status print it, and they keep working while the Gateway runs.
openclaw gateway stop
openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login ryzeControl UI: Settings > MCP
Open the MCP page of the Control UI (/settings/mcp, with /mcp as an alias), choose Add server under Configured servers, name it ryze, pick Streamable HTTP and paste the URL. OpenClaw's docs put the OAuth settings in the scoped config editor on that page, so set auth: "oauth" there and click Sign in. Adding a server needs administrator access. Inside a chat, + > Plugins > Add MCP server saves a server too.
openclaw.json
Edit ~/.openclaw/openclaw.json, which is JSON5, so comments and trailing commas are allowed. The Gateway watches the file and applies the change. Then sign in with openclaw mcp login ryze on a stopped Gateway, or use Sign in under Settings > MCP.
{
mcp: {
servers: {
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
auth: "oauth",
},
},
},
}A Ryze AI API key instead of OAuth
If you want a Ryze AI API key in place of the browser sign-in, leave out auth: "oauth" and send the key as a bearer header. OpenClaw ignores static Authorization headers while auth: "oauth" is on. Keep the key in an environment variable: a ${RYZE_API_KEY} reference does not trigger the literal-value warning of openclaw doctor when the variable is set.
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
headers: { Authorization: "Bearer ${RYZE_API_KEY}" },
}A remote entry takes the transport streamable-http or sse, and OpenClaw reads an entry with no transport as sse, so set streamable-http for this address. A request times out after 60 seconds by default, and listing the tools at session start gets 10 seconds when requestTimeoutMs is not set.
OpenClaw and MCP: the facts in one table
| Topic | What OpenClaw's documentation says |
|---|---|
| Where a server is added | Settings > MCP > Add server in the Control UI, + > Plugins > Add MCP server in a chat, openclaw mcp add or set in a terminal, or mcp.servers in ~/.openclaw/openclaw.json |
| Config file | ~/.openclaw/openclaw.json in JSON5, applied by the Gateway when the file changes |
| Transports | stdio for local commands, plus SSE and Streamable HTTP for addresses |
| Sign-in | auth: "oauth" on an HTTP entry, then openclaw mcp login with the Gateway stopped, or Sign in under Settings > MCP for an administrator |
| Whose account | One shared credential that the operator manages by default. Per-requester sign-in needs oauth.identity set to per-requester and gateway.publicOrigin set to an HTTPS origin |
| Approval | MCP tools follow OpenClaw's tool profiles and tool policy. Per-call prompts are documented for Codex runs only |
| Tool names | The agent sees <server>__<tool>, so a Ryze AI tool such as hubspot__search can carry the server name as a prefix. Run openclaw mcp doctor ryze --probe to see the exact names |
| Plan | No paid tier; MIT licensed and self-hosted |
| Admin controls | Adding a server from a chat and signing in from Settings need administrator access. enabled: false keeps an entry and hides its tools |
Sources: OpenClaw MCP documentation, OpenClaw config extensions, OpenClaw MCP registry commands. Checked November 15, 2026.
Other clients
The same URL works in other MCP clients. HubSpot is connected once in Ryze AI, so nothing changes on the HubSpot side.
Claude Code
Claude Code registers the same URL with one claude mcp add command. How to connect Claude Code to HubSpot.
Codex
Codex takes the connector URL through its own MCP settings. How to connect Codex to HubSpot.
Claude and ChatGPT
Both add https://connector.get-ryze.ai/mcp as a custom connector. In ChatGPT it is an app under Settings > Apps. If the connector was added before HubSpot was connected in Ryze AI, remove and re-add it so the tool list refreshes.
HubSpot access and scopes
Four things decide what OpenClaw can reach in your HubSpot portal.
- Which portal
- The portal you connected in Ryze AI. Several portals can sit in one workspace. One is the primary, marked with a star, and the agent uses it unless you name another. The tools accept an optional connection_id.
- What the scopes allow
- HubSpot's access token carries the scopes the app asked for. It does not mirror the installing user's own record permissions, so the scopes in the table below decide the reach.
- One shared sign-in
- By default OpenClaw's OAuth credential is shared and operator-managed, so everyone who talks to that agent works through the one Ryze AI sign-in behind it. Per-requester sign-in needs gateway.publicOrigin set to an HTTPS origin.
- What stands in front of a change
- No prompt is documented for each call in OpenClaw's built-in runtime. The controls are your tool policy and a toolFilter, described under the tools table below.
Access behind each action
What the HubSpot tools can do depends on the scopes granted during the sign-in. The table lists what Ryze AI documents for the connection.
| Action in Ryze AI | HubSpot access |
|---|---|
| Read and edit contacts, companies and deals | Default HubSpot connection |
| Filter and query records with the CRM Search API | Default HubSpot connection |
| Read contact lists and look up account owners | Default HubSpot connection |
| Read and edit CMS blog content | Default connection, on portals whose plan includes the content scope |
| Delete records or blog posts when asked | Default connection, through the separate delete tool |
| Tickets, custom objects and list editing | Not available on the default connection |
The 12 required HubSpot scopes of the default connection
The default connection asks HubSpot for 12 required scopes. Required scopes must be granted for the install to succeed. Here is each one with what HubSpot says it covers.
| Scope | What HubSpot says it covers | With Ryze AI |
|---|---|---|
| crm.objects.contacts.read, crm.objects.contacts.write | View contact properties and details; create, delete and change contacts | Read and edit |
| crm.objects.companies.read, crm.objects.companies.write | View company properties and details; create, delete and change companies | Read and edit |
| crm.objects.deals.read, crm.objects.deals.write | View deal properties and details; create, delete and change deals | Read and edit |
| crm.objects.owners.read | View details about the users assigned to a CRM record | Read only |
| crm.schemas.contacts.read | View property settings for contacts | Read only |
| crm.schemas.deals.read, crm.schemas.deals.write | View, create and change property settings for deals | Read and edit |
| crm.lists.read | View details about contact lists | Read only |
| content | Access to the content APIs, including website pages, landing pages and blog APIs. HubSpot offers it to CMS Hub Professional or Enterprise and Marketing Hub Professional or Enterprise accounts only | Blog content, read and edit |
Optional scopes for files, CMS functions, knowledge base and membership are dropped automatically when the chosen account has no access to that tool. Left out of the list: custom object scopes, list editing (crm.lists.write), company property settings and the Sensitive Data scopes. A ticket search on the default connection was refused in the test. So tickets, custom objects and list editing are outside the default connection.
Source: HubSpot scopes, HubSpot OAuth guide, HubSpot app install permissions. Checked November 14, 2026.
Removing access
To cut OpenClaw off, stop the Gateway and run openclaw mcp logout ryze to delete the saved credentials, or openclaw mcp unset ryze to remove the entry. Setting enabled: false on the entry hides its tools and keeps the entry. To end the portal access itself, click View on the HubSpot card in Ryze AI and disconnect the portal, or uninstall the app in HubSpot under Settings, Integrations, Connected Apps.
What OpenClaw can do in HubSpot
The Ryze AI connector exposes 5 HubSpot tools: three read, one writes and one deletes. Writes and deletes are separate tools, so a filter can treat them differently. Every tool takes the workspace and an optional connection_id.
| Tool | Type | What it does |
|---|---|---|
| hubspot__listObjects | Read | Lists CRM records of one object type page by page, with the properties you choose and the IDs of associated records. |
| hubspot__search | Read | Searches CRM records through the HubSpot CRM Search API with filter groups, sorts, a text query and chosen properties. |
| hubspot__read | Read | Sends a GET request to a HubSpot JSON API resource, such as a record, property definitions, owners, a list or blog posts. |
| hubspot__write | Write | Creates or updates a HubSpot resource, such as a contact, company, deal or blog post, and adds associations between records. |
| hubspot__delete | Delete | Deletes (archives) a HubSpot resource by ID, such as a CRM record or blog post. |
Some limits apply to every client, OpenClaw included. HubSpot returns a default subset of properties unless specific fields are requested, each connection is one portal, and CMS source-code file endpoints return raw files and fail through the read tool. Deleted blog posts may not be recoverable.
Approvals and keeping the agent read-only
OpenClaw's docs describe prompts before each MCP call for Codex runs only. In the built-in runtime, MCP tools follow the usual tool profiles and tool policy: the coding and messaging profiles include them, the minimal profile hides them, and tools.deny with bundle-mcp switches them all off. Inside a chat, + > Plugins > Tool access lets you turn off single tools for that session. The Ryze AI chat has its own Tool approvals picker that starts on Skip all approvals, and in Claude the write and delete tools can be set to Needs approval; neither applies inside OpenClaw. HubSpot's own connectors for Claude and ChatGPT carry the same advice to set write tools to Needs Approval.
To keep the agent from changing HubSpot, hide the write and delete tools with a toolFilter on the entry. Names are exact or simple * globs. Run openclaw mcp doctor ryze --probe first to see the names OpenClaw reports.
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
auth: "oauth",
toolFilter: {
exclude: ["*hubspot__write", "*hubspot__delete"],
},
}This entry hides the two tools that change HubSpot, so only the three read tools stay. The pattern hides these two names only; tools for other connected platforms stay visible.
Limits in numbers
| Limit | Number |
|---|---|
| Burst limit for Marketplace OAuth apps | 110 requests every 10 seconds for each HubSpot account that installs the app, not counting the CRM Search API. HubSpot's rule names apps distributed through its Marketplace, and Ryze AI has a Marketplace listing, so it reads as the rule that applies. No response in the test carried a rate limit header. |
| CRM Search API rate | 5 requests per second per account. |
| Search page size | 10 records by default, at most 200 per page. |
| Search result cap | 10,000 total results for any query. Paging past 10,000 returns a 400 error. |
| Search filters | At most 5 filter groups of up to 6 filters each, 18 filters in total. |
| Search query length | At most 3,000 characters. |
| Search delay | New or updated records can take a few moments to appear in search. Archived records never do. |
| Default properties | Contacts return firstname, lastname, email, lastmodifieddate, hs_object_id and createdate unless you ask for others. Companies and deals have their own short defaults. |
| List page size | Up to 100 contacts in one list request, then page on with the after value. The tool definition caps hubspot__listObjects at 100. |
| Batch operations | 100 records at a time in the HubSpot API. |
| Path length | Up to 2,048 characters on the read, write and delete tools, from the tool definitions. |
| Rate limit error | Past a limit HubSpot answers 429 for later calls. The daily limit resets at midnight in the account's time zone. |
| Access token life | OAuth access tokens expire after 30 minutes, and the app refreshes them with the refresh token. |
| Deleted records | Deleted CRM records can be restored from the recycling bin for up to 90 days. Permanent or GDPR deletions skip it. |
| OpenClaw request time | 60 seconds per MCP request by default, and 10 seconds to list tools at session start when requestTimeoutMs is not set. |
Sources: HubSpot API usage guidelines, HubSpot CRM search guide, HubSpot contacts guide, HubSpot restore deleted records, HubSpot OAuth tokens. Checked November 14, 2026.
What the default connection returned, tested
Each row is one call through the default connection to a HubSpot portal on November 14, 2026, made from Claude Code. All 11 HubSpot calls were reads. Nothing about the portal or its records is kept here, and the search filters matched nothing on purpose.
| What was asked | What came back |
|---|---|
| hubspot__search on contacts, filter email equal to a random 20-letter string | Worked. An empty result in the shape {"total":0,"results":[]} |
| hubspot__search on companies, filter domain equal to a random string | Worked. {"total":0,"results":[]} |
| hubspot__search on deals, filter dealname equal to a random string | Worked. {"total":0,"results":[]} |
| hubspot__listObjects on contacts, limit 1, property hs_object_id | Worked. One result and a paging block with an after value and a link. HubSpot added createdate and lastmodifieddate to the one property asked for |
| hubspot__search on contacts with a filter on a property that does not exist | Refused with Error 400 |
| hubspot__search on contacts with limit 201 | Refused with Error 400 VALIDATION_ERROR |
| hubspot__search on tickets | Refused with status not_allowed |
| hubspot__read of a deal with ID 0, and of two made-up contact and blog post IDs | status not_found each time. HubSpot answered with an HTML 404 page for the made-up IDs |
First 3 prompts to run
1. Find a contact by email
Search HubSpot contacts for the email name@example.com and show the first name, last name, lifecycle stage and create date.
Tools used: hubspot__search
What comes back: A search by email. The test ran this kind of search with a filter that matched nothing and got an empty result, so a match depends on your portal. Nothing is changed.
2. List recent deals
Search HubSpot deals created in the last 30 days and list the deal name, amount and stage.
Tools used: hubspot__search
What comes back: A search over deals with the properties you named. A deals search ran in the test and returned a valid result. Nothing is changed.
3. Find stalled deals and their owners
Find open deals with no change in 30 days and show the owner of each.
Tools used: hubspot__search, then hubspot__read on crm/v3/owners
What comes back: A search for the deals, then an owners lookup. The owners read was not run in the test, so this page shows no result for it. Nothing is changed.
The first two prompts use a search shape that was run in the test. The third relies on an owners read that was not run. Replace the email and the 30-day window with your own values.
What the tools return
Two response shapes were seen in the test on November 14, 2026. They help you recognize what the tools return before the agent summarizes it.
A search with no matches comes back as this exact shape:
{"total":0,"results":[]}A list call returns records plus a cursor. The keys of each record and of the paging block were:
results[]: id, properties, createdAt, updatedAt, archived, url
paging.next: after, linkThe search tool's definition names 12 filter operators: EQ, NEQ, GT, GTE, LT, LTE, BETWEEN, IN, NOT_IN, HAS_PROPERTY, NOT_HAS_PROPERTY and CONTAINS_TOKEN. Filters inside one group are joined with AND, and groups are joined with OR.
10 jobs to hand to OpenClaw
Ten jobs to give an OpenClaw agent, each with its Ryze AI tool. The searches and the listing were run in the test. The jobs that change HubSpot were not.
| Job | Ask OpenClaw | Tool | Works on the default connection |
|---|---|---|---|
| Contact lookup | Find the contact with this email and show the properties I name. | hubspot__search | Yes |
| Recent deals | List deals created in the last 30 days with name, amount and stage. | hubspot__search | Yes |
| Stalled deals | Find open deals with no change in 30 days and show the owner of each. | hubspot__search, then hubspot__read on crm/v3/owners | Yes |
| Company and its records | Find the company with this domain and list its associated contacts and deals. | hubspot__search, then hubspot__listObjects | Yes |
| Contact paging | Page through contacts with lifecycle stage and create date. | hubspot__listObjects | Yes |
| Property check | Show which contact and deal properties exist before building a filter. | hubspot__read on crm/v3/properties/contacts | Yes |
| Contact list | Read this contact list and its details. | hubspot__read on crm/v3/lists/{listId} | Yes, read only |
| Create a deal | Create a deal and associate it with a company and a contact. | hubspot__write | Yes, unless you filtered the tool out |
| Update a property | Update a property on a contact, company or deal. | hubspot__write | Yes, unless you filtered the tool out |
| Delete a duplicate | Delete this duplicate contact by ID. | hubspot__delete | Yes, unless you filtered the tool out |
Blog posts can be read and written through hubspot__read and hubspot__write when the portal's plan includes the content scope. The two blog reads in the test used made-up IDs, so blog access on a real portal is not confirmed here. Not available on the default connection: searching or editing tickets, custom object records, adding contacts to a list, and reading CMS theme or template code files.
6 ways to connect OpenClaw to HubSpot
There are six ways to give an OpenClaw agent access to HubSpot. This guide treats the first, the Ryze AI connector, as the main way: it is a hosted address, so you run no extra process, create no HubSpot app of your own and paste no token. You approve the portal once and save one address. The other five were checked on the dates in the sources and are listed with what each one needs. None of them was run inside OpenClaw.
| Way | Runs where | Setup in OpenClaw | What it reaches in HubSpot | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted. One address for every user | openclaw mcp set, the Control UI or openclaw.json, then openclaw mcp login ryze | Contacts, companies and deals to read and edit, owners and lists to read, blog content, deletes through a separate tool. 5 tools | Paid Ads is $89 per month with a 7-day free trial |
| HubSpot remote MCP server | Hosted by HubSpot at https://mcp.hubspot.com | Create an MCP connector in HubSpot under Development, MCP Connectors for a client ID and secret, then point an OAuth client with PKCE at the address. HubSpot's page gives no OpenClaw steps and OpenClaw's docs do not say how a pre-set client ID and secret are entered, so the pairing is unverified | 36 documented tools for CRM records, activities, pages, blog posts, campaigns and more. No delete tool in the list | HubSpot states no price. It is generally available to all HubSpot accounts |
| Composio | Hosted | Remote MCP address https://connect.composio.dev/mcp saved as a remote server in OpenClaw. Composio's pages document other clients, so the OpenClaw entry is the same address in OpenClaw's format | 354 HubSpot tools and 2 triggers, read and write | The free plan stops at 10,000 tool calls a month. Standard is $18 per seat per month |
| Zapier MCP | Hosted | Zapier gives you an MCP server tied to your Zapier account. Its quickstart names other clients, so the OpenClaw entry is a remote server you save yourself | The HubSpot actions you enable in your Zapier account | Each successful tool call uses 2 tasks from your Zapier plan |
| Coupler.io MCP | Hosted | Set up a data flow in Coupler.io that connects HubSpot, then follow its MCP Server page. Access uses a personal access token from the Coupler.io web app. Its pricing page lists OpenClaw among AI integrations | Read-only analysis of datasets your data flows load. Coupler.io says the AI gets aggregated data, not individual records | Free plan at $0; paid plans from $32 per month, or $24 billed annually |
| baryhuang/mcp-hubspot, open source | A Docker container you run | A stdio entry that runs the Docker image with a HubSpot access token, since OpenClaw supports stdio servers. The README documents Claude Desktop, so the OpenClaw entry was not run | 7 tools for contacts, companies and engagement data. No deals tools in the README list | Free, MIT licence. 129 GitHub stars, last push November 11, 2025 |
Options that do not fit this job
- HubSpot's connectors for assistants. HubSpot's own connectors cover ChatGPT, Claude, Gemini and Microsoft Copilot. HubSpot's AI tools page names no OpenClaw connector.
- HubSpot Developer MCP server. It runs on your computer and gives a coding agent HubSpot's developer docs and project tools for building apps. It has no CRM record tools, so it cannot answer questions about contacts or deals.
- HubSpot Agent CLI (beta). A command-line tool that works on CRM records under your own permissions after a browser login. HubSpot's guide names Claude Code, Claude Cowork and OpenAI Codex, not OpenClaw, and it is an install on the machine rather than an MCP address.
- @hubspot/mcp-server on npm. HubSpot's earlier local server, in beta, with 21 tools and a private app access token. Version 0.4.0 from June 18, 2025 was still the latest on November 14, 2026, and HubSpot announced that creating legacy private apps is being turned off.
- ClawHub. OpenClaw's public plugin registry has no Ryze AI plugin, so the connector is saved by address as in the steps above.
Which one to pick
Ryze AI is the best way to connect OpenClaw to HubSpot for contact, company and deal work with one sign-in, with one caveat: it has 5 tools, leaves out tickets, custom objects and list editing, and needs a Ryze AI plan. HubSpot's remote MCP server has 36 documented tools and needs no Ryze AI plan, but you create and manage a connector with client credentials and HubSpot gives no OpenClaw steps. Pick Composio or Zapier when your team already runs one of them for other apps. Pick Coupler.io for read-only reporting on aggregated data. Choose the open-source Docker server when you want to run the code yourself and can live with 7 tools.
Sources: HubSpot remote MCP server, HubSpot AI tools, HubSpot Developer MCP server, HubSpot Agent CLI, @hubspot/mcp-server on npm, Composio HubSpot toolkit page, Composio pricing, Zapier MCP for HubSpot, Zapier MCP usage, Coupler.io HubSpot MCP, Coupler.io pricing, baryhuang/mcp-hubspot, OpenClaw ClawHub, Ryze AI HubSpot guide. HubSpot and vendor pages checked November 14, 2026.
OpenClaw, HubSpot and MCP: dates that matter
| Date | What happened |
|---|---|
| March 31, 2026 | OpenClaw 2026.3.31 added remote HTTP and SSE servers by URL under mcp.servers, with auth headers and an optional streamable-http transport. |
| April 13, 2026 | HubSpot's remote MCP server became generally available to all HubSpot accounts, with write access added. OAuth 2.1 with PKCE is required. |
| August 31, 2026 | OpenClaw 2026.8.1, also called OpenClaw 2.0, added servers from the chat composer and per-requester OAuth for shared MCP servers. |
| September 15, 2026 | HubSpot announced the end of support for API versions v1 to v3 and legacy apps, with enforcement in September 2027, and for v4 on March 30, 2027. This page makes no claim about what Ryze AI will do. |
| September 23, 2026 | OpenClaw 2026.9.6 let administrators sign in to MCP connectors from Settings. |
| October 30, 2026 | HubSpot put AI connector access to Sensitive Data in public beta, when a Super Admin allows it. |
| November 3, 2026 | OpenClaw 2026.10.10 began protecting MCP configuration while the Gateway runs. The commands openclaw mcp set and login now need the Gateway stopped. |
| November 10, 2026 | OpenClaw 2026.11.3 came out. On November 15, 2026 it was the newest stable release, and its notes list no MCP change. |
| December 4, 2026 | HubSpot's Pipelines API V1 stops responding after this date. |
Sources: HubSpot changelog, April 13, 2026, HubSpot changelog, September 15, 2026, HubSpot October 2026 rollup, HubSpot Pipelines API V1 sunset, OpenClaw releases, OpenClaw 2026.3.31 changelog, OpenClaw 2026.10.10 release notes. Checked November 15, 2026 and November 14, 2026.
How this guide was tested
Two sets of checks stand behind this guide: the connector and a HubSpot portal on November 14, 2026, and OpenClaw's documentation on November 15, 2026. The table lists what was run and what came back.
| What was run | What came back |
|---|---|
| The tool list through a signed-in MCP client | All five HubSpot tools loaded by name, under the names in the tools table above. |
| Tool definitions | They name contacts, companies and deals as the object types, 12 search operators, the CREATE and UPDATE write methods and a 2,048-character path limit. |
| Three searches that match nothing | Contacts, companies and deals each returned {"total":0,"results":[]}. |
| hubspot__listObjects on contacts with limit 1 | One result and a paging block. |
| Calls made to fail on purpose | A property that does not exist, a limit of 201, a tickets search and three reads of IDs that do not exist. Their messages are in the errors table below. |
| Total | 11 HubSpot calls: 6 hubspot__search, 4 hubspot__read and 1 hubspot__listObjects. |
Not run for this page: every step inside OpenClaw. No Gateway was installed or started, no server was saved and no sign-in was attempted. The OpenClaw steps follow its documentation and changelog as read on November 15, 2026. The signed-in client for the tool list and the reads was Claude Code, which reaches the same server and the same five tools. The write and delete tools were not run, because they change HubSpot. No record was read by ID, and no owners, lists, property definitions or blog posts were listed.
OpenClaw and HubSpot errors and fixes
Exact error messages
These are the exact messages HubSpot and the connector returned in the test on November 14, 2026, plus one OpenClaw message taken from its documentation, which was not seen in a run.
| Message | What it means | What to do |
|---|---|---|
| authentication refused (401) | OpenClaw's docs say this appears in the startup log and catalog diagnostic when a Streamable HTTP server answers initialization with HTTP 401, which is how a server asks for a sign-in. | Run openclaw mcp login ryze with the Gateway stopped, or click Sign in under Settings > MCP. |
| limit must be in range [0..200] (actual value: 201) | The CRM search returns at most 200 records per page. It came back as Error 400 with the category VALIDATION_ERROR. | Ask for 200 or fewer per page and page on with the after value. |
| There was a problem with the request. | HubSpot rejected a search body that filtered on a property name that does not exist, and did not say which one. | Read the property definitions first (crm/v3/properties/contacts) and use the internal property name. |
| The scope needed for this API call isn't available for public use. If you have questions, contact support or post in our developer forum. | The default connection could not search tickets. The status was not_allowed. | Use contacts, companies and deals through Ryze AI. For tickets use one of HubSpot's own options. |
| Object not found. objectId is usually positive. | No record has that ID. The status was not_found. | Search for the record first and use the id it returns. |
| provider returned text/html (status 404) "Error 404 Not Found" | HubSpot answered a read of an ID that does not exist with an HTML 404 page. The read tool only parses JSON and reports the 404. The same form came back for two made-up blog post IDs. | Check the ID. Search for the contact by email instead, or list blog posts and use an ID from the list. |
Other problems
- The HubSpot tools do not appear in OpenClaw
- Until shared credentials exist, OpenClaw leaves the server out of the agent runtime instead of failing the turn. Run openclaw mcp login ryze with the Gateway stopped, then check with openclaw mcp status or openclaw mcp doctor ryze --probe. If you saved the connector before HubSpot was connected in Ryze AI, remove the entry and save it again.
- The tool list is empty or times out
- The tool list at session start gets 10 seconds when requestTimeoutMs is not set. Raise requestTimeoutMs on the entry, and confirm transport is streamable-http, because OpenClaw reads a missing transport as sse.
- The sign-in page opens on the wrong machine
- Approve it in the browser, then give the code it returns to openclaw mcp login ryze with --code.
- The API key is ignored
- Static Authorization headers are ignored while auth: "oauth" is on. Remove auth for the key route, or remove the header and use OAuth.
- An openclaw mcp command holds back
- Since OpenClaw 2026.10.10 (November 3, 2026), commands that change saved servers, and login, need the Gateway stopped. Stop it, run the command and start it again, or edit openclaw.json, or use Settings > MCP.
- HubSpot will not let you approve the app
- HubSpot lets a Super Admin or a user with App Marketplace access install apps. Ask a Super Admin to do it or to grant the permission.
- A search returns nothing for a record you just created
- New or updated records can take a few moments to appear in search, and archived records never do.
- Blog posts cannot be read or written
- The content scope is offered by HubSpot to CMS Hub or Marketing Hub accounts on the Professional or Enterprise tier. On other portals the optional blog access is dropped.
- Properties you asked about are missing
- HubSpot returns a default subset of properties unless specific fields are requested. Name the properties in the prompt.
- The agent reports HTTP 429
- HubSpot limits requests per account. Wait for the window to pass and ask for smaller pages.
- Tickets or custom objects fail
- They are outside the default connection. Use HubSpot's own connector or MCP server for those.
- The tools reply that a subscription is required
- The HubSpot tools need an active Ryze AI plan or free trial. Start the trial, then retry.
Terms on this page
- MCP
- The Model Context Protocol, an open standard for connecting AI applications to outside systems. OpenClaw, Claude and ChatGPT support it.
- Gateway
- The OpenClaw process that runs your agents and keeps their settings, MCP servers and saved sign-ins.
- openclaw.json
- The JSON5 settings file at ~/.openclaw/openclaw.json. MCP servers live under mcp.servers.
- Scope
- A permission an app asks for at install time. Each one opens a set of HubSpot API endpoints and the data behind them.
- Portal
- A HubSpot account. Each Ryze AI connection to HubSpot is one portal.
- Filter group
- A block of filters in a CRM search. Filters inside a group are joined with AND, groups with OR.
- Recycling bin
- Where deleted CRM records go. HubSpot can restore them for up to 90 days.
Source for MCP: modelcontextprotocol.io. Checked November 15, 2026.
Frequently asked questions
How do I connect OpenClaw to HubSpot?
The main way is the Ryze AI connector. Connect your portal in Ryze AI under Integrations by signing in to HubSpot and approving the permissions. Then save https://connector.get-ryze.ai/mcp in OpenClaw as a streamable-http server with auth set to oauth, using openclaw mcp set, Settings > MCP or openclaw.json, and sign in with openclaw mcp login ryze.
Is there a HubSpot MCP server for OpenClaw?
Yes. The Ryze AI connector is one: its address is https://connector.get-ryze.ai/mcp and it has 5 HubSpot tools. HubSpot also runs its own remote MCP server at https://mcp.hubspot.com with 36 documented tools, though no HubSpot page opened names OpenClaw as a client.
What is the HubSpot MCP server URL for OpenClaw?
For the Ryze AI connector the address is https://connector.get-ryze.ai/mcp, the same for every user. HubSpot's own remote server is at https://mcp.hubspot.com and needs a client ID and secret from an MCP connector you create in HubSpot under Development, MCP Connectors.
Does HubSpot have an official MCP server?
Yes, two. The remote server at https://mcp.hubspot.com reaches CRM records over OAuth with PKCE and became generally available on April 13, 2026. The Developer MCP server runs on your computer and serves developer docs and project tools, with no CRM record tools. HubSpot also has connectors for ChatGPT, Claude, Gemini and Microsoft Copilot.
Does HubSpot's own connector work with OpenClaw?
No HubSpot page opened on November 14, 2026 names OpenClaw. HubSpot's connectors cover ChatGPT, Claude, Gemini and Microsoft Copilot, and its remote MCP server accepts any MCP client that supports OAuth with PKCE. Whether OpenClaw can complete that sign-in with a pre-set client ID and secret was not run.
Can OpenClaw edit my HubSpot contacts and deals?
Yes. Through Ryze AI, an OpenClaw agent can create and update contacts, companies and deals with the write tool and add associations between records. It cannot touch tickets, custom objects or list membership on the default connection.
Can OpenClaw delete HubSpot records?
Only through the separate hubspot__delete tool, when you ask for it by ID. Most CRM deletes go to HubSpot's recycling bin, where records can be restored for up to 90 days. A toolFilter with an exclude list on the ryze entry hides the delete tool from the agent.
Does OpenClaw ask before it changes HubSpot?
OpenClaw's docs describe per-call prompts for Codex runs only. In the built-in runtime, MCP tools follow tool profiles and policy. To require a pause before changes, hide the write and delete tools with a toolFilter and enable them only when you want a change made.
Which OpenClaw plan do I need?
None. OpenClaw is MIT licensed and self-hosted, and its docs say it has no paid tier. The model provider your agent uses has its own costs, which are outside this guide.
Which HubSpot permissions do I need to connect?
A HubSpot Super Admin or a user with App Marketplace access can install the app. Other users need a Super Admin to do it. The app asks for 12 required scopes, including content, which HubSpot offers only to CMS Hub or Marketing Hub Professional and Enterprise accounts.
Can I connect more than one HubSpot portal?
Yes. Several portals can be connected to one workspace under View > Add one more account on the HubSpot card. One is the primary and is used unless you name another, and the tools accept an optional connection_id.
Why do the HubSpot tools not show up in OpenClaw?
Until shared credentials exist, OpenClaw leaves the server out of the agent runtime. Run openclaw mcp login ryze with the Gateway stopped. If you connected HubSpot in Ryze AI after saving the server, remove the ryze entry and save it again so the tool list refreshes.
How many records can one HubSpot search return?
At most 200 per page and 10,000 in total for a query. A request for 201 came back as Error 400 in the test. The tool definition caps hubspot__listObjects at 100 per page.
How much does it cost to connect OpenClaw to HubSpot?
Adding the connector costs nothing, but the HubSpot tools need an active Ryze AI plan or free trial. Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial, Agency is $279 per month and Shopify CRO is $1,499 per month. Annual billing takes 30% off the first year.
How do I disconnect HubSpot from OpenClaw?
Stop the Gateway and run openclaw mcp logout ryze to delete the saved credentials, or openclaw mcp unset ryze to remove the entry. To end the portal access, disconnect the portal on the HubSpot card in Ryze AI or uninstall the app in HubSpot under Settings, Integrations, Connected Apps.