By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Microsoft Copilot to HubSpot is the Ryze AI connector. Microsoft's pages show no Copilot chat window with a field for an MCP address, so the connector goes onto an agent: connect your HubSpot account in Ryze AI with a HubSpot sign-in, then on a Copilot Studio agent add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool with OAuth 2.0 and Dynamic discovery, and sign in to Ryze AI. The agent then holds 5 HubSpot tools: 3 that read, 1 that writes and 1 that deletes.
- In Ryze AI open Integrations, click Connect on the HubSpot card, sign in to HubSpot, choose the account and approve the permissions
- In Copilot Studio switch to the classic experience, open your agent, then Tools, Add a tool, New tool, Model Context Protocol
- Enter a name, a description and the URL, pick OAuth 2.0 with Dynamic discovery, then select Create and Next
- Create a new connection, sign in to Ryze AI, select Add to agent and ask for a HubSpot contact search in the test chat
Microsoft Copilot to HubSpot at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector: a hosted MCP server that a Copilot Studio agent takes as a tool. A Microsoft 365 Copilot declarative agent can take it as an action, a route not yet confirmed for Ryze AI |
| Server address | https://connector.get-ryze.ai/mcp, the same for every user |
| Where it goes in Copilot | On an agent. Classic experience: Tools > Add a tool > New tool > Model Context Protocol. New experience: Build tab > Tools > Add > Model Context Protocol (MCP). No chat window has a documented field for it |
| Sign-in | Copilot signs in to Ryze AI with OAuth 2.0 and Dynamic discovery. HubSpot is joined once inside Ryze AI through a HubSpot OAuth sign-in, so no HubSpot key or token is pasted into Copilot |
| HubSpot tools | 5: 3 read, 1 write and 1 delete |
| Can the agent change HubSpot | Yes. hubspot__write creates or updates records and hubspot__delete archives them. HubSpot's recycling bin keeps most deleted CRM records for up to 90 days, and deleted blog posts may not be recoverable |
| Portals per connection | One HubSpot portal per connection. Several portals can sit in one Ryze AI workspace, and the primary one is used unless you name another |
| Copilot plan | Microsoft's MCP pages name none. A trial cannot publish an agent, and the Copilot Studio for Teams plan lacks generative orchestration and Power Platform connectors |
| Ryze AI price | $89 a month for Paid Ads after a 7-day free trial. The connector itself costs nothing to add |
| HubSpot's own option | A HubSpot Agent for Copilot that an admin adds to Microsoft 365 Copilot, and a remote MCP server at https://mcp.hubspot.com. Both are covered in the section on ways to connect |
| Last tested | November 14, 2026: 11 read-only HubSpot calls through the connector from Claude Code. No step inside a Microsoft product was run |
Before you start
- A Copilot Studio agent or a Microsoft 365 Copilot declarative agent. This is a builder task, usually done by an agent maker or admin in a work or school tenant. Microsoft says Copilot Studio is available to all Microsoft 365 users for creating agents and actions. A Copilot Studio trial lets you create and test agents but cannot publish them, and Microsoft asks for a work or school account to sign up for it.
- A Copilot Studio plan that carries MCP. Microsoft documents that MCP access in Copilot Studio relies on Power Platform connectors, and its licensing page marks both Power Platform connectors and generative orchestration as not available in the Copilot Studio for Teams plan. Whether MCP tools run on the Teams plan is not documented, so test before you promise it to anyone.
- A HubSpot user who can install apps. HubSpot says users installing apps must be a Super Admin or have App Marketplace access permissions. The Ryze AI connection is a HubSpot OAuth install, so the person who clicks Connect in Ryze AI needs one of those two. Blog tools also need the HubSpot content scope, which HubSpot offers only to CMS Hub Professional or Enterprise and Marketing Hub Professional or Enterprise accounts.
- 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 Agency is $279 per month. Connecting the connector is free, and the HubSpot tools need an active plan or trial.
How to connect Copilot Studio to HubSpot
Step 1 happens in Ryze AI and HubSpot, steps 2 to 6 in Copilot Studio. The connector URL is the same for every user.
Connect HubSpot in Ryze AI
Create a Ryze AI account or sign in, open Integrations, find the HubSpot card and click Connect. 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. Do this before you add the connector to Copilot, so the tool list is complete the first time.
Open the agent and start a new MCP tool
These steps are for the classic experience (the standard harness). New agents from the Copilot Studio home page run on the Microsoft Copilot harness, so switch first: select the three dots at the bottom of the home page side bar, then Open classic experience, which lasts for the session, or start the agent from Other ways to build. Open your agent and go to its Tools page. Select Add a tool, then New tool, then Model Context Protocol in the Create new section. The MCP onboarding wizard opens, which Microsoft calls the recommended way to add a server.
Fill in the server details
Server name: Ryze AI. Server description: a plain note on what the tools do, for example Searches and reads HubSpot contacts, companies, deals, owners and lists, and creates or updates CRM records. Microsoft says the agent orchestrator uses this description to decide when to call the server. Server URL: https://connector.get-ryze.ai/mcp.
Choose OAuth 2.0 with Dynamic discovery
Set the authentication type to OAuth 2.0 and the OAuth type to Dynamic discovery. The Ryze AI server supports dynamic client registration, so no client ID, secret or callback URL is typed. Microsoft calls Dynamic discovery the simplest of its three OAuth types. Select Create, then Next.
Create the connection and add the tool
On Add tool, select Create a new connection and complete the Ryze AI sign-in, or pick an existing connection. Microsoft's page stops at that button and does not show the sign-in window, and this step was not run for this guide. Then select Add to agent.
Ask a HubSpot question in the test chat
MCP needs generative orchestration, which Microsoft says is on by default. Open the test chat panel and ask: Find the HubSpot contact with a given email address and show their lifecycle stage. If the HubSpot tools do not run, check the errors list below.
The Ryze AI help article for HubSpot covers the HubSpot side of the connection. Microsoft's page on connecting an agent to an existing MCP server covers the Copilot Studio wizard, and its page on switching experiences shows how to open the classic experience. Checked November 14, 2026.
Microsoft 365 Copilot declarative agent
If your colleagues work in Microsoft 365 Copilot and not in Copilot Studio, the same URL can ride in a declarative agent as an MCP action. Microsoft documents this route in its Agents Toolkit walkthrough. HubSpot also publishes its own agent for Microsoft 365 Copilot, described in the section on ways to connect.
- Install Visual Studio Code and Microsoft 365 Agents Toolkit version 6.12.0 or later.
- Select the Agents Toolkit icon in the Activity Bar, then Create a New Agent/App, then Declarative Agent.
- Select Add an Action, then Start with an MCP Server, and enter https://connector.get-ryze.ai/mcp.
- Choose OAuth (with dynamic registration) as the authentication type, then pick a project location and an agent name. Nothing else is asked: no client ID, secret or scopes. Microsoft requires the authorization server to hand back a client secret at registration; whether the Ryze AI server does so for Microsoft was not checked.
- In the Accounts pane sign in to Microsoft 365 and look for Custom App Upload Enabled and Copilot Access Enabled. If either is missing, an admin has to allow custom app upload.
- In the Lifecycle pane select Provision, read the dialog, select Confirm and wait until the toolkit reports that provisioning finished.
- Open m365.cloud.microsoft/chat, find the agent in the Agents section of the sidebar (its name ends in dev), ask a HubSpot question and select the Sign in button that carries the agent's name.
Microsoft says Agents Toolkit sets a new MCP plugin to dynamic tool discovery, so Copilot reads the server's tool list at run time and you add no tools by hand. Sideloading needs Upload custom apps switched on by an admin in the Teams admin center. The first time the agent uses the plugin, Copilot asks the person to allow or cancel. After that, tools that only read do not ask again, and tools that change data do.
Sources: Build a plugin for a declarative agent from an MCP server, dynamic client registration for plugins, Microsoft 365 Copilot extensibility requirements, plugin overview. Checked November 14, 2026.
New experience, admin connector and personal Copilot
Microsoft documents more places that accept an MCP address than the two above. Each changes who does the setup and how sign-in works, so find out which one your tenant uses before you start.
Copilot Studio, new experience
On the Microsoft Copilot harness the server is added from the agent's Build tab: Tools in the components panel on the right, Add beside the search bar, then Model Context Protocol (MCP). The Add MCP server page asks for Name, Description, Server URL and Authentication; select Add, review the tools Copilot Studio lists, then Save. Microsoft labels that how-to page preview, and its Authentication field lists no choices, so the page does not say whether Dynamic discovery is among them. For the HubSpot tools through Ryze AI, the classic steps above are the documented route.
Getting the agent in front of colleagues
People reach a Copilot Studio agent from Teams and Microsoft Copilot after it has been published at least once and connected to the Teams and Microsoft Copilot channels. A trial license cannot publish, so a trial agent with the HubSpot tools lives in the test chat panel only.
Admin route: a custom federated connector
A Global Administrator or AI Administrator can turn an MCP address into a connector in the Microsoft 365 admin center under Copilot > Connectors > Gallery > Create a new connector > Connect to MCP server. People with a Microsoft 365 Copilot license then connect it in Copilot Chat under Settings > Sources. Its sign-in methods are Microsoft Entra SSO, OAuth 2.0 with a client registered by hand in the Teams Developer Portal, or No Auth. Dynamic registration is not listed, and the Ryze AI connector registers clients through its register endpoint, so this route is unconfirmed for Ryze AI.
Copilot with a personal Microsoft account
Copilot on Copilot.com and Copilot Mobile with a personal account has four built-in connectors under Profile > Connectors: OneDrive, Outlook.com, Google Drive, and Gmail with Google Calendar and Contacts. Microsoft's support article does not mention MCP or a way to add your own, and HubSpot is not on the list, so a personal account has no documented place for HubSpot through Ryze AI.
Microsoft Copilot and MCP in one table
| Topic | What Microsoft's pages say |
|---|---|
| Where the address is typed | In an agent or in an admin connector. Copilot Studio: the MCP wizard (classic) or the Add MCP server page (new). Microsoft 365 Copilot: a declarative agent action, a custom federated connector, or a plugin package manifest |
| Config files | None named for Copilot Studio, which is set up in the browser. Agents Toolkit writes ai-plugin.json in the agent project, and m365agents.yml holds isPKCEEnabled |
| Servers on your own computer | No route accepts a start command. Microsoft 365 Copilot must reach the server over the internet, and Microsoft points to a dev tunnel with a public HTTPS address for local work |
| Transport | Copilot Studio takes Streamable and dropped SSE after August 2025. Plugin packages and Cowork expect Streamable HTTP over HTTPS with TLS 1.2 or later |
| Sign-in, Copilot Studio wizard | None, an API key sent in a header or query parameter you name, or OAuth 2.0 as Dynamic discovery, Dynamic or Manual |
| Sign-in, declarative agent | Microsoft Entra SSO, dynamic client registration, the OAuth 2.0 authorization code flow or none. API keys are unsupported for MCP plugins, PKCE is on by default, and dynamic registration needs a client secret from the authorization server |
| Whose account a tool uses | In Copilot Studio a tool uses End user credentials by default, so each person signs in; Maker-provided credentials is the other choice. New-experience connections are saved per agent and per channel |
| Confirmation before a tool runs | Copilot Studio turns on every tool of a new server (Allow all). Declarative agents ask on first use and then before tools that change data. Federated connectors run read tools freely and keep write and delete tools at Needs approval |
| Plan and billing | The MCP how-to pages name no plan. Agents on the new experience are billed in Copilot Credits, charged for model tokens, the harness and tools, MCP servers included |
| Where servers are managed | Classic: select the server on the Tools page for Details, Tools, Resources and an Enabled toggle. New: the tools list on the Build tab. Declarative agents: Teams > Apps > Manage your apps |
| Admin controls | A data policy on Power Platform connectors also covers MCP servers. In the Microsoft 365 admin center, Agents > Tools > Registry can block a server, which turns off every tool it exposes |
Sources: adding an MCP server in the new experience, MCP in Copilot Studio, MCP tools and resources on an agent, agent tools and credentials, managing tools in the new experience, Teams and Microsoft Copilot channels, Copilot Credits, Copilot Studio access and browsers, plugin sign-in types, MCP servers in plugin packages, custom federated connectors, federated connector approvals, admin tool registry, Copilot connectors for personal accounts. Checked November 14, 2026.
Other AI clients
The same connector URL works in other MCP clients. Ryze AI has separate HubSpot guides for them:
HubSpot permissions
Two sign-ins are involved, and each limits what the agent can reach.
- HubSpot install through Ryze AI
- A HubSpot OAuth app install: you sign in to HubSpot, choose the portal and approve the permissions. No API key or private app token is pasted. The installer must be a Super Admin or hold App Marketplace access. Ryze AI also has a listing in the HubSpot Marketplace, which names eight shared data types: contacts, contact properties, companies, deals, deal properties, contact lists, owners and CMS blog posts.
- What the token covers
- HubSpot says an access token reflects the scopes the app requested and not the installing person's record permissions. HubSpot's own example: a user who can view only owned contacts but authorizes the contacts read scope gives the app a token that can view all contacts in the account. Decide who clicks Connect with that in mind.
- Ryze AI sign-in from Copilot
- The Copilot connection signs in to Ryze AI with OAuth 2.0. In Copilot Studio the tool runs on End user credentials unless the maker changes it, so each person who uses the agent makes a connection of their own. The agent reaches the HubSpot portal connected in the chosen Ryze AI workspace, and nothing else.
- Power Platform data policy
- Microsoft notes that a data policy on Power Platform connectors also regulates access to the MCP server and its tools. If a policy blocks the connector, ask your Power Platform admin.
Sources: Microsoft's MCP server and data policies note and the Ryze AI HubSpot integration. Checked November 14, 2026.
HubSpot scopes the install asks for
The Ryze AI facts list the scopes the HubSpot install asks for. The table maps each to HubSpot's own scope name and what HubSpot says it covers. Required scopes must be authorized for the install to succeed. Optional scopes are dropped automatically when the chosen account has no access to that tool.
| Named in the Ryze AI facts | HubSpot scope | What HubSpot says it covers | Which accounts |
|---|---|---|---|
| Contacts read and write | crm.objects.contacts.read, crm.objects.contacts.write | View properties and details about contacts; create, delete and change contacts | All accounts |
| Companies read and write | crm.objects.companies.read, crm.objects.companies.write | View properties and details about companies; create, delete and change companies | All accounts |
| Deals read and write | crm.objects.deals.read, crm.objects.deals.write | View properties and details about deals; create, delete and change deals | All accounts |
| Owners read | crm.objects.owners.read | View details about users assigned to a CRM record | All accounts |
| Contact schema read | crm.schemas.contacts.read | View property settings for contacts | All accounts |
| Deal schema read and write | crm.schemas.deals.read, crm.schemas.deals.write | View property settings for deals; create, delete and change them | All accounts |
| Lists read | crm.lists.read | View details about contact lists | All accounts |
| Content | content | Content APIs, including website pages, landing pages and blog APIs | CMS Hub Professional or Enterprise, or Marketing Hub Professional or Enterprise only |
| Optional: files | files | A legacy scope for the file manager; HubSpot recommends the granular files scopes | All accounts |
| Optional: CMS functions | cms.functions.read, cms.functions.write | View and write Content Hub serverless functions and secrets | Content Hub Enterprise only |
| Optional: knowledge base | cms.knowledge_base.articles.read and related scopes | View knowledge articles through the GraphQL API | Service Hub Professional or Enterprise only |
| Optional: membership | cms.membership.access_groups.read, cms.membership.access_groups.write | View, create, edit and delete membership access groups | Service Hub or Content Hub Professional or Enterprise only |
Which OAuth scopes the Ryze AI connector hands a Copilot connection was not tested. The scopes above belong to the HubSpot install, which is the same whichever AI client calls the tools.
Which tool reaches what
The scopes decide what is possible, and the tool decides how the agent reaches it. These rows show which tool each job needs.
| What you ask the agent to do | Tool it needs |
|---|---|
| Search contacts, companies or deals with filters | hubspot__search |
| Page through records with chosen properties | hubspot__listObjects |
| Read one record, property definitions, owners, a list or blog posts | hubspot__read |
| Create or update a contact, company, deal or blog post, or add an association | hubspot__write |
| Archive a CRM record or a blog post by ID | hubspot__delete |
Every tool takes a workspace argument and an optional connection_id, so a workspace with several HubSpot portals can address one by ID. Without it, the primary portal (marked with a star in Ryze AI) is used.
Out of reach on the default connection: custom objects (the requested scopes include none for them), tickets (a ticket search was refused in the test), editing contact lists (lists are read-only), company property settings, and Sensitive Data properties. CMS source-code file endpoints return raw files and fail through the read tool.
Sources: HubSpot scopes, HubSpot OAuth and app installs, installing and uninstalling apps, Ryze AI in the HubSpot Marketplace, Ryze AI HubSpot integration. Checked November 14, 2026.
Removing access
To take HubSpot away from a Copilot Studio agent, open its Tools page in the classic experience, hover over Ryze AI, select the three dots and Delete; to pause it instead, open the server, switch Enabled off and Save. In the new experience, select the X next to the server on the Build tab and then Remove. A sideloaded declarative agent is managed in Teams under Apps > Manage your apps. To stop Ryze AI reaching HubSpot, click View on the HubSpot card under Integrations in Ryze AI and disconnect the portal with the trash icon. In HubSpot, go to Settings, Integrations, Connected Apps, open Actions on the app, choose Uninstall and type uninstall to confirm.
What Copilot can do in HubSpot
The Ryze AI connector exposes 5 HubSpot tools: 3 read, 1 write and 1 delete. All five names were loaded from the live connector on November 14, 2026 and match the Ryze AI facts. Copilot Studio adds the whole server as one tool and switches every tool on through Allow all; turn Allow all off to switch single tools off.
| 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 any 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. |
Three of the five tools can change HubSpot, depending on what the agent is asked, and whether Copilot stops to ask depends on where the agent runs. In the classic experience, the Allow all switch above is how you keep the agent away from hubspot__delete or hubspot__write. Microsoft describes a per-tool setting, Ask the end user before running, that defaults to No, but it does not say the setting shows for an MCP server, so look for it on the Ryze AI tool. The new-experience pages describe only on and off switches. A Microsoft 365 declarative agent asks on first use and then before tools that change data, with allow once or always allow. The Ryze AI chat has its own Tool approvals picker that starts on Skip all approvals and can be set to Approve write & delete or Manual approve, and scheduled tasks in Ryze AI run without an approval step.
Calls that were run
These are the calls that were run through the Ryze AI connector on November 14, 2026, against a HubSpot portal that was already connected. All were reads, and they ran from Claude Code, not from Copilot. No record content is shown, because none is kept.
| Call | What came back |
|---|---|
| hubspot__search on contacts, filter on email with an impossible value | A valid empty result: {"total":0,"results":[]} |
| hubspot__search on companies, filter on domain with an impossible value | A valid empty result with the same shape |
| hubspot__search on deals, filter on deal name with an impossible value | A valid empty result with the same shape |
| hubspot__listObjects on contacts, limit 1, one chosen property | One result plus a paging block. Each result carried id, properties, createdAt, updatedAt, archived and url, and the paging block carried after and link. HubSpot added the create date and last modified date to the one property asked for |
| hubspot__search on contacts with a filter on a property that does not exist | Refused with Error 400 (see errors and fixes) |
| hubspot__search on contacts with limit 201 | Refused with Error 400 VALIDATION_ERROR (see errors and fixes) |
| hubspot__search on tickets | Refused with status not_allowed (see errors and fixes) |
| hubspot__read of a deal path with ID 0, and of a contact path and two blog post paths with made-up IDs | status not_found each time. The made-up IDs returned an HTML 404 page |
Not confirmed by any call: reading one existing record by ID, reading owners, property definitions or lists, and reading an existing blog post. hubspot__write and hubspot__delete were not run, because they change the portal.
Limits in numbers
Three parties set limits on this route: HubSpot's API, the Ryze AI tools and Copilot. HubSpot counts its limits per account. The tests did not see a rate limit header in any response, so none of the HubSpot figures below was observed in a live answer.
| Limit | Figure or rule | Set by |
|---|---|---|
| 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 says the API limit increase add-on does not raise it. Ryze AI connects with OAuth and has a HubSpot Marketplace listing, so this reads as the rule that applies; that is an inference and was not observed | HubSpot |
| CRM Search API rate | 5 requests per second per account. Search responses carry none of the rate limit headers | HubSpot |
| Search page size | 10 records per page by default, at most 200 per page. A search can reach 10,000 results in total; paging past that returns a 400 error | HubSpot |
| Search filters | At most 5 filter groups with up to 6 filters each, 18 filters in total. Too many returns a VALIDATION_ERROR. A search body can hold at most 3,000 characters | HubSpot |
| Search freshness and defaults | New or updated records may take a few moments to appear in search, and archived records never do. Unless properties are requested, a search returns a fixed set; for contacts that is first name, last name, email, last modified date, object ID and create date | HubSpot |
| List requests | Up to 100 contacts in one list request, paged with the after value. Batch operations are limited to 100 records at a time | HubSpot |
| Associations API | Batch read takes 1,000 inputs per request and batch create 2,000. Burst limits are 100 requests per 10 seconds on Free and Starter and 150 on Professional and Enterprise | HubSpot |
| Access token life | OAuth access tokens expire after 30 minutes and the app refreshes them with the refresh token | HubSpot |
| Rate limit errors | Past a limit HubSpot answers 429. The daily limit resets at midnight in the account's time zone | HubSpot |
| Recycling bin | Deleted records can be restored up to 90 days after deletion. Permanent or GDPR deletions skip the bin and can take up to 30 days to be purged | HubSpot |
| Ryze AI tool inputs | hubspot__listObjects takes a limit up to 100. hubspot__search passes its limit to HubSpot: the tool definition says 200 and HubSpot rejected 201. Path arguments take up to 2,048 characters | Ryze AI |
| Tools on a Copilot Studio agent | Up to 128 with generative orchestration, and Microsoft suggests 25 to 30. The Ryze AI server is added as one tool; Microsoft does not say whether the 5 HubSpot tools inside it count toward 128 | Microsoft, classic experience |
| MCP servers in one conversation | An agent can hold several, but only a capped number run in one conversation and the rest are skipped for that turn. Microsoft gives no figure | Microsoft, new experience |
| Plugins in a declarative agent | Up to 5 plugins always go into the prompt, and answers may get worse above 10 tools in one plugin. The 5 HubSpot tools stay below that | Microsoft 365 Copilot |
| Tool call time in plugin packages | A tool call should finish in under 30 seconds, which matters for a wide search. Microsoft names this for plugin packages and Cowork | Microsoft |
| Tool list after a change | Copilot Studio picks up server changes by itself. After a custom connector is republished, tool changes can take about 12 to 24 hours to show, with no manual refresh | Microsoft |
Sources: HubSpot API usage guidelines, HubSpot CRM search, HubSpot contacts API, HubSpot associations API, HubSpot OAuth tokens, restoring deleted records, Copilot Studio tool limits, MCP servers per conversation, declarative agent plugin limits, Copilot Studio MCP troubleshooting, tool call time in plugin packages, Ryze AI HubSpot integration. Checked November 14, 2026.
First 3 prompts to run
Each answer comes from your own HubSpot portal, so this page describes what comes back and shows no sample numbers. Add the prompts to the agent's instructions or paste them into the test chat.
1. Find a contact by email address
Search HubSpot contacts for the email address I give you and show their first name, last name, lifecycle stage and create date.
Tools used: hubspot__search
What comes back: A list with the matching contacts and the properties you named, or an empty result when nothing matches.
2. Deals created in the last 30 days
Search HubSpot deals created in the last 30 days and show the deal name, amount and stage for each, sorted by create date.
Tools used: hubspot__search
What comes back: One row per matching deal with the three properties you asked for.
3. A company and its contacts
Find the HubSpot company with the domain I give you, then list the contacts associated with it.
Tools used: hubspot__search, then hubspot__listObjects
What comes back: The company record, then its associated contacts, using the IDs of associated records that the list call can return.
Ryze AI has not tested this connection in Copilot Studio or Microsoft 365 Copilot. The HubSpot calls behind these prompts were run from Claude Code on November 14, 2026, and the Copilot steps follow Microsoft's documentation and the connector's OAuth metadata, which supports dynamic client registration. Report anything that differs to Ryze AI support.
10 jobs to hand to a Copilot agent
Nine jobs a Copilot agent with the Ryze AI tool can take on, each matched to its tool. The last column says whether the default connection covers it and what was run. None was run from Copilot.
| Job | Ask the agent | Tool | Works on the default connection |
|---|---|---|---|
| Contact lookup | Find the contact with this email address and show the properties I name. | hubspot__search | Yes. A contacts search ran on November 14, 2026 |
| Recent deals | List deals created in the last 30 days with name, amount and stage. | hubspot__search | Yes. A deals search ran |
| Stale deals with owners | Find open deals with no change in 30 days and show the owner of each. | hubspot__search, then hubspot__read on the owners path | Yes. The owners read was not run |
| Company and its people | Find the company by domain and list its associated contacts and deals. | hubspot__search, then hubspot__listObjects | Yes. A companies search ran; associations were not requested in the test |
| Paged contact export | Page through contacts with chosen properties, such as lifecycle stage and create date. | hubspot__listObjects | Yes. A listing with limit 1 returned a paging cursor |
| Property check | Show which contact and deal properties exist before building a filter. | hubspot__read on the properties paths | Yes. Not run in the test |
| Contact list read | Read a contact list and its details. | hubspot__read on the lists path | Yes, as a read. Lists cannot be edited. Not run |
| Record update | Update the deal stage or a contact property for the record I name. | hubspot__write | Yes, with the contacts, companies and deals write scopes. Not run |
| Clean-up | Archive the old test contact I name. | hubspot__delete | Yes. Most CRM deletes go to HubSpot's recycling bin. Not run |
6 ways to connect Microsoft Copilot to HubSpot
Six ways can bring HubSpot into a Microsoft Copilot setup. This guide uses the Ryze AI connector as the main way: Copilot Studio's wizard takes its address with Dynamic discovery, HubSpot is signed in once inside Ryze AI, and nothing secret is pasted into Copilot. HubSpot's own agent for Microsoft 365 Copilot is the closest alternative and needs no Copilot Studio work. None of the six was run inside Copilot for this guide.
| Way | Runs where | Setup in Copilot | What it reaches in HubSpot | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI at one address for every user | Copilot Studio: MCP wizard with the connector URL and OAuth 2.0 Dynamic discovery, then Create a new connection. Microsoft 365 Copilot: a declarative agent action with OAuth (with dynamic registration), not confirmed for Ryze AI | 5 tools: search and listing of contacts, companies and deals, reads of owners, property definitions, lists and blog posts, writes to records and blog posts, and a delete tool. One portal per connection | Paid Ads $89 a month after a 7-day free trial; SEO Starter $129 a month; Agency $279 a month |
| HubSpot Agent for Microsoft 365 Copilot | Hosted; used in Microsoft 365 Copilot on web, desktop and mobile, and in Copilot in Teams | A Microsoft 365 admin adds the HubSpot Agent in the admin center under Agents, All agents. People then open HubSpot under Agents in Copilot Chat and sign in to HubSpot. No Copilot Studio agent is built | Read and write on contacts, companies, deals, tickets, line items, products and engagements (calls, meetings, notes, tasks). Read-only on users, quotes, invoices, orders, carts, subscriptions and segments | HubSpot states no price (all products and plans). It needs a Microsoft 365 Copilot license, or the Copilot Chat add-on license with an eligible Microsoft 365 license |
| HubSpot remote MCP server | Hosted by HubSpot at https://mcp.hubspot.com, tested by HubSpot with the Streamable HTTP transport | In HubSpot, Development, MCP Connectors, Create MCP connector with a name and a redirect URL, which gives a client ID and secret. A client that supports OAuth with PKCE then points at the server. Copilot Studio's Manual OAuth type takes a client ID and secret, but whether it completes against this server, and what redirect URL to register, were not checked. HubSpot's page names no Microsoft Copilot product as a client | 36 tools in HubSpot's list on November 14, 2026, covering CRM search, reads and writes, segments, properties, pipelines, campaigns, content analytics, landing pages, website pages and blog posts, and more. No delete tool in the list. Blog, website page and render tools are limited to select AI clients, named as Claude, ChatGPT and Gemini | HubSpot states no price; generally available to all HubSpot accounts since April 13, 2026 |
| Windsor.ai (Windsor MCP) | Hosted by Windsor.ai; HubSpot is a data source | HubSpot is joined as a data source in Windsor.ai, and Windsor's pages list a setup guide for Copilot Agent. That guide was not opened for this page | Reporting access to HubSpot data through a connector with 1,141 fields (287 metrics and 854 dimensions). Whether Windsor MCP can write to HubSpot is not stated | Free forever: 1 user, 1 data source, 1 account. Basic is $23 per month, or $19 per month under the annual column |
| Coupler.io | Hosted; HubSpot data loaded by a data flow you set up | Coupler.io's pricing page lists Copilot among its AI integrations. A personal access token from Coupler.io is used, and that pairing was not tried | Read-only analysis of datasets your data flows load, such as contacts, companies, deals, quotes, line items and tickets. The AI gets aggregated data and not individual records | Free $0; Starter $32 per month ($24 billed yearly). Which plan includes the MCP server is stated differently on two Coupler.io pages |
| Composio | Hosted by Composio at https://connect.composio.dev/mcp over Streamable HTTP, the transport Copilot Studio accepts | Add the address, then authenticate and authorize HubSpot through Composio's managed OAuth app. Composio's pages name Claude, Cursor and ChatGPT, not Microsoft Copilot, so the Copilot route was not checked | A HubSpot toolkit listed with 354 tools and 2 triggers, read and write, including batch create, update and archive | Free $0 with $2 in credits once and app tool calls stopping at 10,000 a month. Standard is $18 per seat per month |
With a hosted third-party way your HubSpot data passes through that vendor, and Microsoft says you are responsible for the tools and resources you reach through a non-Microsoft MCP server in Copilot Studio. Composio's toolkit page also quotes a free allowance of 100,000 tool calls a month that its pricing page does not match; the pricing page figure is used here.
Options that do not fit a Copilot agent
- Zapier MCP. Zapier's HubSpot page lists triggers, write actions and search actions by name, and the version of the page that was read printed no totals. Each successful tool call uses 2 tasks from your Zapier plan, and failed calls use none. Zapier's pages name Claude, ChatGPT, Cursor, Codex, Gemini Enterprise, Grok, VS Code and Windsurf, and no Copilot product, so it is left out of the table.
- baryhuang/mcp-hubspot. An open source server you run in a Docker container with a HubSpot access token. It lists 7 tools for contacts, companies and engagement data and none for deals. Copilot Studio has no field for a start command, so it does not reach a Copilot agent without hosting it yourself.
- HubSpot's local servers and CLI. The @hubspot/mcp-server npm package (version 0.4.0, published June 18, 2025, 21 tools) runs on your computer with a private app token. The Developer MCP server has 23 tools for building apps and CMS assets and no CRM record tools. The Agent CLI is a command-line tool for coding agents. None of them can be added to a Copilot Studio agent.
- A custom federated connector pointed at Ryze AI. This is the admin route in the section on other Copilot surfaces. None of its three sign-in methods is dynamic registration, which is how the Ryze AI connector signs clients up, so it stays unconfirmed for Ryze AI.
Which one to pick
Pick the Ryze AI connector when one Copilot Studio agent should search and edit HubSpot contacts, companies and deals, and your team already works in Ryze AI. The caveats are that the route has not been run inside Copilot, that it needs a Ryze AI plan once the trial ends, that it reaches one portal per connection and that tickets and custom objects are out of reach. Pick HubSpot's own agent when your tenant has Microsoft 365 Copilot licenses and people only need to chat with HubSpot data in Copilot Chat, because an admin can add it without building an agent. Pick the remote MCP server when you need tools that Ryze AI does not carry, such as campaigns or landing pages, and can register a HubSpot MCP connector and test the sign-in yourself. Windsor.ai and Coupler.io fit reporting on HubSpot data, and Composio is a hosted option whose Copilot route is untested.
Sources: HubSpot Agent for Copilot, HubSpot AI tools, HubSpot remote MCP server, HubSpot remote MCP overview, baryhuang/mcp-hubspot, @hubspot/mcp-server on npm, HubSpot Developer MCP tools, Windsor MCP, Windsor.ai HubSpot fields, Windsor.ai pricing, Coupler.io MCP for HubSpot, Coupler.io pricing, Composio HubSpot toolkit, Composio pricing, Zapier MCP for HubSpot, Copilot Studio MCP guide, third-party MCP servers in Copilot Studio, custom federated connectors, Ryze AI HubSpot integration. Checked November 14, 2026.
Copilot, HubSpot and MCP: dates that matter
| Date | What happened |
|---|---|
| March 19, 2025 | Microsoft announced MCP support in Copilot Studio. The first release used the SSE transport. |
| May 29, 2025 | MCP in Copilot Studio reached general availability, with the tool list on the server settings page and streamable transport. |
| August 2025 | Copilot Studio stopped supporting SSE for MCP; Streamable is the only supported transport. Microsoft gives no exact day. |
| September 1, 2025 | HubSpot's remote MCP server entered public beta across all hubs and tiers. |
| December 15, 2025 | Microsoft announced general availability of MCP in declarative agents for Microsoft 365 Copilot, built in Agents Toolkit with Add Action, Start with an MCP server. |
| April 13, 2026 | HubSpot's remote MCP server became generally available to all HubSpot accounts, with write access added and OAuth with PKCE required. |
| June 15, 2026 | HubSpot's knowledge base article for the HubSpot Agent for Copilot was first published; it was last updated November 12, 2026. |
| September 2, 2026 | A Microsoft Copilot blog post announced general availability of the GitHub Copilot harness in Copilot Studio, since renamed the Microsoft Copilot harness, with MCP servers as tools. Microsoft's how-to page for adding a server on that harness still carries a preview label. |
| September 15, 2026 | HubSpot's Fall 2026 Spotlight added custom objects, Leads and read-only conversations to its remote MCP server and Claude connector. The same day HubSpot announced that API versions v1 to v3 and legacy apps reach end of support, with v4 ending on March 30, 2027 and enforcement for the rest in September 2027. Ryze AI has not said how its tools will handle this. |
| October 27, 2026 | The Microsoft 365 Copilot release notes list, under this date, admins creating custom MCP connectors in the Microsoft 365 admin center. Microsoft's roadmap item gives an earlier availability month, February 2026. |
| October 30, 2026 | HubSpot put AI connector access to Sensitive Data in public beta for its ChatGPT, Claude and Copilot connectors, when a Super Admin allows it. |
| December 4, 2026 | HubSpot's Pipelines API V1 stops responding after this date. |
Sources: Microsoft Copilot blog, March 19, 2025, Microsoft Copilot blog, May 29, 2025, SSE support ended after August 2025, Microsoft 365 Developer Blog, December 15, 2025, Microsoft Copilot blog, September 2, 2026, adding an MCP server in the new experience, Microsoft 365 Copilot release notes, Microsoft 365 roadmap item 501585, HubSpot changelog, remote MCP server beta, HubSpot changelog, April 13, 2026, HubSpot Agent for Copilot article, HubSpot Fall 2026 Spotlight, HubSpot legacy API and app support, HubSpot October 2026 rollup, HubSpot Pipelines API V1 sunset. Checked November 14, 2026.
How this guide was tested
The Ryze AI connector's HubSpot tools were called on November 14, 2026, from Claude Code, through a HubSpot portal that was already connected in a Ryze AI workspace. That is 11 HubSpot calls, all reads: 6 hubspot__search, 4 hubspot__read and 1 hubspot__listObjects. The calls are listed in the section on what Copilot can do in HubSpot. Everything about Microsoft products was read from Microsoft's pages on the same day.
| What was run | What came back |
|---|---|
| The five HubSpot tool names | Loaded by name from the live connector. All five definitions came back and match the Ryze AI facts. |
| Searches on contacts, companies and deals | Each returned a valid empty result for a filter that cannot match. |
| A contacts listing with limit 1 | Returned one result and a paging cursor. |
| Five calls that were refused | A search on a missing property, a search with limit 201, a ticket search and two reads of IDs that do not exist. The exact messages are in errors and fixes. |
| Microsoft's Copilot Studio and Microsoft 365 Copilot pages | Read on the same day for every setup step, limit, plan note and date used here. |
| HubSpot's knowledge base, developer docs and changelog pages | Read on the same day for every HubSpot scope, limit, date and the details of HubSpot's own options. |
| Vendor pages for Windsor.ai, Coupler.io, Composio and Zapier | Read on the same day for the comparison. Their tool counts and prices are as the pages printed them. |
Not run for this guide: anything inside a Microsoft product and anything that changes HubSpot. No Copilot Studio agent was created, no MCP tool was added, no Agents Toolkit project was built, no admin center connector was set up, and no Ryze AI sign-in happened from Copilot. hubspot__write and hubspot__delete were not called. No record was read by ID, and no owners, lists, property definitions or existing blog posts were read. The Copilot steps follow Microsoft's and Ryze AI's documentation as read on November 14, 2026.
Errors and fixes
The first five messages below came back from the Ryze AI connector in the tests on November 14, 2026, with the IDs and correlation numbers left out. The next entries come from Microsoft's documentation or from the Ryze AI facts and say so.
- limit must be in range [0..200] (actual value: 201)
- Returned as Error 400 with category VALIDATION_ERROR when hubspot__search was called with limit 201. The CRM search API returns at most 200 records per page. Ask for 200 or fewer and page on with the after value.
- There was a problem with the request.
- Returned as Error 400 when a contacts search used a property name that does not exist. HubSpot does not say which property is wrong. Read the property definitions for contacts first and use the internal property name.
- The scope needed for this API call isn't available for public use.
- Returned with status not_allowed when tickets were searched. The default Ryze AI connection could not search tickets on the test portal. Use contacts, companies and deals through Ryze AI, and use HubSpot's own agent or MCP server for tickets.
- Object not found. objectId is usually positive.
- Returned with status not_found when a deal path used ID 0. No record has that ID. Search for the record first and use the id it returns.
- provider returned text/html (status 404) Error 404 Not Found
- Returned with status not_found for a contact path and for blog post paths with IDs that do not exist. HubSpot answered with an HTML page, and the read tool reports the 404. Check the ID, search for the contact by email, or list blog posts and use an ID from the list. These calls do not show whether blog reads work on a given portal.
- There is no place to paste the URL in Copilot chat
- Microsoft's pages show no field for an MCP address in a Copilot chat window. Add the URL as a tool on a Copilot Studio agent or build a declarative agent in Agents Toolkit. An admin can also create a custom federated connector in the Microsoft 365 admin center, but that route was not confirmed for Ryze AI.
- The Tools page or the New tool button is missing
- The agent runs on the new experience, where tools sit on the Build tab. Open the classic experience from the three dots at the bottom of the home page side bar, or create the agent with Other ways to build.
- I cannot publish the agent
- A Copilot Studio trial lets you create and test agents but not publish them. Use the test chat panel, or move to a plan that can publish.
- Model Context Protocol or connectors are missing on the Teams plan
- The Copilot Studio for Teams plan does not include Power Platform connectors or generative orchestration, and MCP access relies on connectors. Ask your admin about a standalone Copilot Studio subscription.
- The connector is blocked
- A Power Platform data policy that regulates connectors also regulates the MCP server, and a blocked tool shows as disabled in the Add tool panel. Ask your Power Platform admin to allow it.
- Agents Toolkit says Custom App Upload is not enabled
- Sideloading needs Upload custom apps turned on by an admin in the Teams admin center. Ask your admin, then reload the Accounts pane.
- The declarative agent sign-in fails
- Microsoft's dynamic registration for declarative agents needs the authorization server to issue a client secret, and registration without one is not supported yet. This was not checked for the Ryze AI server, so use the Copilot Studio route if the sign-in does not complete.
- HubSpot will not let me connect
- From HubSpot's documentation: the person installing must be a Super Admin or hold App Marketplace access. Ask a Super Admin to click Connect, or to grant the permission.
- The agent never calls the HubSpot tools
- Microsoft says the orchestrator uses the server description to decide whether to call the server. Rewrite the description to say what the tools do, such as searching HubSpot contacts and deals, and check that generative orchestration is on.
- The tools return a subscription message or no data
- The HubSpot tools need an active Ryze AI plan or free trial, and HubSpot must show as connected under Integrations in Ryze AI. If the connector was added before HubSpot was connected, remove it from the agent, add it again and start a new test chat.
- Blog tools are refused
- The content scope is available only on CMS Hub Professional or Enterprise and Marketing Hub Professional or Enterprise accounts, according to HubSpot. Whether a given portal's blog reads work was not confirmed by the tests.
- I need a second portal
- Each connection is one HubSpot portal. In Ryze AI, click View on the HubSpot card and add one more account; the primary portal is used unless the prompt names another.
Sources: HubSpot CRM search, HubSpot app installs, HubSpot scopes, Copilot Studio MCP troubleshooting. Checked November 14, 2026.
Terms on this page
- MCP (Model Context Protocol)
- An open standard through which an AI model reaches outside data and applications. Copilot Studio adds an MCP server to an agent as a tool, and HubSpot runs its own MCP server too.
- Classic and new experience
- The two ways Copilot Studio builds agents. Microsoft's pages call the classic one the standard harness and the new one the Microsoft Copilot harness. The setup steps in this guide use the classic one.
- Dynamic discovery
- A Copilot Studio OAuth 2.0 option for servers that support dynamic client registration: Copilot Studio finds the sign-in endpoints and registers itself, so nobody types a client ID.
- Declarative agent
- A Microsoft 365 Copilot agent built from a manifest, here in Agents Toolkit, that can carry an MCP server as an action.
- Portal
- A HubSpot account. Each Ryze AI connection to HubSpot is one portal, and a workspace can hold several.
- Super Admin and App Marketplace access
- The two HubSpot user permissions that allow installing an app. Everyone else needs a Super Admin.
- Filter group
- A block of filters in a CRM search. Filters inside a group are joined with AND and groups are joined with OR. HubSpot allows 5 groups of 6 filters, 18 filters in total.
- Scope
- A permission an app asks for at install time. Each one opens a set of HubSpot API endpoints and the data behind them.
Sources: HubSpot remote MCP server, Copilot Studio experiences, Dynamic discovery, declarative agents with MCP, scopes, installing apps, filter groups. Checked November 14, 2026.
Frequently asked questions
How to connect Copilot to HubSpot?
Ryze AI is the best way to connect Microsoft Copilot to HubSpot for an agent that should search and edit contacts, companies and deals, though it has not been run inside Copilot and needs a Ryze AI plan or trial. Connect HubSpot in Ryze AI, then add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool on your Copilot Studio agent with OAuth 2.0 and Dynamic discovery, select Create and Next, and create the connection.
Is there a HubSpot connector for Copilot?
Yes. HubSpot publishes a HubSpot Agent for Microsoft 365 Copilot that a Microsoft 365 admin adds in the admin center, and it needs a Microsoft 365 Copilot license. HubSpot's marketing page also lists a connector for Microsoft Copilot. For a Copilot Studio agent, the Ryze AI connector is a hosted server you add as an MCP tool.
Is there a Copilot HubSpot MCP server I can use?
Yes, two hosted ones can be tried. The Ryze AI connector at https://connector.get-ryze.ai/mcp gives an agent 5 HubSpot tools. HubSpot's own remote server at https://mcp.hubspot.com lists 36 tools and needs an MCP connector created in HubSpot for its client ID and secret, but HubSpot's page names no Microsoft Copilot product as a client. Neither was run inside Copilot for this guide.
Can I add a HubSpot connector in Microsoft 365 Copilot without Copilot Studio?
Yes, through HubSpot's own agent, which an admin adds in the Microsoft 365 admin center. Microsoft also documents a declarative agent built with Agents Toolkit and a custom federated connector, but the first needs a client secret from dynamic registration, which was not checked for Ryze AI, and the second lists no dynamic registration. Neither is confirmed for the Ryze AI connector.
Can I paste an MCP URL into the Copilot chat app?
No. None of Microsoft's pages shows a Copilot chat window that takes an MCP address. The URL goes in Copilot Studio on an agent's Tools page or Build tab, in a declarative agent built with Microsoft 365 Agents Toolkit, or in an admin's custom federated connector that people then turn on under Settings > Sources.
Which Copilot plan do I need?
Microsoft says Copilot Studio is available to all Microsoft 365 users for creating agents and actions. A trial can create and test but not publish. The Teams plan lacks Power Platform connectors, which MCP access relies on, so plan for a standalone Copilot Studio subscription. For Microsoft 365 Copilot declarative agents an admin must allow custom app upload.
What HubSpot permissions do I need?
A HubSpot user who is a Super Admin or has App Marketplace access, to install the connection from Ryze AI. The install asks for contacts, companies and deals read and write, owners read, contact schema read, deal schema read and write, lists read and the content scope. HubSpot offers the content scope only on CMS Hub or Marketing Hub Professional and Enterprise accounts.
Can Copilot change my HubSpot data or delete things?
Through Ryze AI, yes. hubspot__write creates or updates records and blog posts, and hubspot__delete archives a record or blog post by ID. Most CRM deletes go to HubSpot's recycling bin, which keeps records up to 90 days, but deleted blog posts may not be recoverable. In Copilot Studio, switch Allow all off to keep the agent away from the write and delete tools.
Does the Ryze AI connector work with Copilot Studio?
The connector is a remote MCP server with OAuth that supports dynamic client registration, which matches Microsoft's Dynamic discovery option. Ryze AI has not tested it in Copilot Studio or Microsoft 365 Copilot, so try it on a portal where a mistake is cheap to undo.
Can I connect more than one HubSpot portal?
Yes. A Ryze AI workspace can hold several HubSpot portals: click View on the HubSpot card and add one more account. One is the primary, marked with a star, and is used unless you name another. How a Copilot connection picks a workspace was not tested.
Can Copilot read HubSpot tickets or custom objects through Ryze AI?
No. A ticket search on the default connection was refused with status not_allowed in the tests on November 14, 2026, and the scopes the install requests include none for custom objects. HubSpot's own agent for Microsoft 365 Copilot lists tickets as readable and writable.
Which transport does Copilot Studio support?
Microsoft says Copilot Studio supports the Streamable transport for MCP and no longer supports SSE after August 2025.
How much does it cost?
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 and Agency is $279 per month. Annual billing takes 30% off the first year. Copilot Studio licensing is set by Microsoft, and HubSpot's own plans apply to your account.
How do I disconnect HubSpot from Copilot?
Remove the Ryze AI tool from the agent in Copilot Studio. To cut Ryze AI off from HubSpot, click View on the HubSpot card under Integrations in Ryze AI and disconnect with the trash icon, then uninstall the app in HubSpot under Settings, Integrations, Connected Apps.