By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect VS Code to HubSpot is the Ryze AI connector. Approve HubSpot once inside Ryze AI with HubSpot's own sign-in. Then, with Copilot as the session target, run Chat: Open Customizations, select MCP Servers and add an HTTP server with https://connector.get-ryze.ai/mcp and the server ID ryze. Trust it and finish the Ryze AI sign-in in your browser. Copilot Chat then has 5 HubSpot tools for contacts, companies, deals, owners, contact lists and blog posts.
- In Ryze AI open Integrations, find HubSpot and click Connect
- Sign in to HubSpot, choose the account (portal) and approve the permissions
- In VS Code run Chat: Open Customizations, select MCP Servers and add an HTTP server with the connector URL
- Trust the server, sign in to Ryze AI and ask Copilot Chat about your contacts, companies or deals
VS Code to HubSpot at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, kept in VS Code as one HTTP MCP server called ryze |
| Server address | https://connector.get-ryze.ai/mcp, the same for every user |
| Where it goes in VS Code | Chat: Open Customizations > MCP Servers > Add Server (+), or the MCP: Add Server command. A personal entry lands in Copilot Global, ~/.copilot/mcp-config.json |
| Sign-in from VS Code | OAuth in the browser, run by VS Code. No HubSpot token, key or client secret is typed into VS Code |
| Sign-in to HubSpot | HubSpot's OAuth screen, opened once from Ryze AI. A Super Admin or a user with App Marketplace access picks the portal and approves the permissions |
| HubSpot tools | 5: hubspot__listObjects, hubspot__search and hubspot__read look things up, hubspot__write creates or updates, hubspot__delete archives |
| Can Copilot change HubSpot | Yes, through the write and delete tools. A new VS Code session starts on Manual permissions, which show a call that is not auto-approved before it runs |
| Copilot plan | GitHub lists MCP in every Copilot plan. Business and Enterprise seats also need the MCP servers in Copilot policy, which ships off |
| 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 VS Code | The local Developer MCP server lists VS Code as a client, with 23 developer tools and no CRM records. HubSpot's remote server at https://mcp.hubspot.com reaches CRM data but its page does not name VS Code |
| Last tested | 11 read-only HubSpot calls through the connector on November 14, 2026. No step inside VS Code was run |
Before you start
- GitHub Copilot in a current VS Code. GitHub's MCP article asks for Copilot access and VS Code 1.99 or later. The steps below save the server to Copilot Global, which came with VS Code 1.140, so update an older install first. A GitHub account that is eligible but has no plan is enrolled in Copilot Free when it signs in to VS Code.
- The MCP policy, when Copilot comes from an organization. On Copilot Business or Copilot Enterprise through an organization or enterprise, the MCP servers in Copilot policy must be on. GitHub ships it off, so an administrator has to enable it. Copilot Free, Pro, Pro+ and Max are outside that policy.
- A local folder, with Copilot as the session target. Microsoft's walkthrough wants AI features switched on, a local folder open and Copilot picked in the Session Target dropdown before a server is added.
- Permission to install apps in HubSpot. A Super Admin, or a user with App Marketplace access, can approve an app such as Ryze AI. If your HubSpot user has neither, ask a Super Admin to connect the account. HubSpot's OAuth guide says a token follows the scopes the app requested, so the approving user's own record limits do not narrow it.
- 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 publishing Content Plan articles to a HubSpot blog. Adding the connector is free, but the HubSpot tools need an active plan or trial.
How to connect VS Code to HubSpot with the Customizations editor
The first two steps happen in HubSpot and Ryze AI, the other four in VS Code. 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. Ryze AI sends you to HubSpot to authorize.
Choose the account and approve the permissions
Sign in to HubSpot, choose the account (portal) and click Choose Account. HubSpot lists what Ryze AI asks for. Approve it and HubSpot returns you to Ryze AI with the connection saved.
Open the MCP Servers list in VS Code
Open a local project folder and pick Copilot in the Session Target dropdown, because the editor shows the servers of the selected harness. Run Chat: Open Customizations from the Command Palette, select MCP Servers and choose Add Server (+) in the User group.
Add the HTTP server
Choose HTTP (HTTP or Server-Sent Events) and enter https://connector.get-ryze.ai/mcp. Type ryze as the server ID. For a personal setup select Global, then Copilot Global. There is no client ID or secret to enter.
Trust the server and sign in
Read the trust prompt before you accept it, then finish the Ryze AI sign-in in the browser. If no sign-in page opens, use the ellipsis (...) beside ryze in MCP Servers and choose Authenticate. On the Ryze AI page pick the workspace that holds your HubSpot connection and click Allow connection.
Ask your first question in Copilot Chat
Open Copilot Chat and ask: List the HubSpot deals I own that are still open, with deal name, amount and stage. Approve the tool call if VS Code asks, then expand it in the conversation to confirm the ryze server answered. Microsoft's docs point out that a reply with no tool call does not prove the connection works.
The Ryze AI help center page for HubSpot covers the HubSpot side of the connection, and the VS Code MCP servers documentation covers the editor side.
Sources: VS Code MCP servers, GitHub: extend Copilot Chat with MCP, GitHub Copilot plans, HubSpot: install apps, Ryze AI help center page for HubSpot. Checked November 14, 2026.
Command Palette and config files
The Customizations editor, the guided command and the config files all end in the same server entry. Choose by how you manage VS Code, not by what HubSpot needs: nothing changes on the HubSpot side.
Guided flow
Run MCP: Add Server from the Command Palette and answer the prompts with the same URL and the server ID ryze. It skips the Customizations editor.
Portable config file
To write the entry yourself, use the portable format that the Copilot harness reads. It lives in ~/.copilot/mcp-config.json for you alone ($COPILOT_HOME/mcp-config.json when that variable is set) or in .mcp.json at the workspace root, and both start with mcpServers. Microsoft's portable HTTP examples all include a tools field, so this one does too:
{
"mcpServers": {
"ryze": {
"type": "http",
"url": "https://connector.get-ryze.ai/mcp",
"tools": ["*"]
}
}
}Older VS Code format
The earlier format uses the key servers in .vscode/mcp.json or the profile mcp.json. It serves the Local harness, which VS Code 1.146 deprecated on November 11, 2026, with removal announced for February 2027. Copilot harness sessions do not read these files directly, and Microsoft's MCP developer guide calls them deprecated destinations in the guided flow. Many older tutorials still show this shape:
{
"servers": {
"ryze": {
"type": "http",
"url": "https://connector.get-ryze.ai/mcp"
}
}
}In the portable entry, ["*"] makes every tool of the server available and leaves approvals in place. Portable files do not support VS Code input variables, envFile or SecretStorage. A workspace .mcp.json is meant to be committed for a team, and with this connector it holds only the address. HubSpot access sits in Ryze AI, and the connector asks for a sign-in instead of a stored token.
Limits of VS Code to know
- The type field sets the transport: http for Streamable HTTP, stdio for a local command and sse for older endpoints that Microsoft labels legacy. The ryze entry uses http.
- Trusting a server lets it start, signing in gives it access, and approving covers single tool calls. VS Code treats the three as separate steps.
- Old-format entries that rely on ${input:...} or ${command:...} prompts are not forwarded to Copilot harness sessions.
- Copilot Global does not sync to your other machines, and a remote host or Dev Container does not read the local file. Add the server on the machine where the session runs.
- Microsoft's MCP developer guide says VS Code signs in to providers other than GitHub and Microsoft Entra through Dynamic Client Registration or a pre-registered OAuth client, and the connector publishes a register endpoint. Ryze AI was not tried inside VS Code for this guide. If the sign-in does not start, email Ryze AI support with the link at the end of the page.
VS Code, Copilot and MCP in one table
| Topic | What Microsoft and GitHub document |
|---|---|
| Screen for adding a server | Chat: Open Customizations opens the Agent Customizations editor. Its MCP Servers page has Add Server (+), and the Chat title bar and the Agents window sidebar lead to the same editor |
| Files the Copilot harness reads | ~/.copilot/mcp-config.json (Copilot Global) for one person, and .mcp.json at the workspace root for a shared setup, each with a top-level mcpServers object |
| Legacy files | .vscode/mcp.json and the profile mcp.json with a servers object, kept for the deprecated Local harness |
| Transports | stdio starts a command, http speaks Streamable HTTP, and sse reaches older endpoints without Streamable HTTP |
| Sign-in | When a server asks for OAuth, the Copilot runtime hands the sign-in to VS Code, which stores the credentials. GitHub and Microsoft Entra are built in. Other providers use Dynamic Client Registration or a pre-registered client, and the portable format has a flat oauthClientId field for the second case. Redirects go to http://127.0.0.1:33418 or https://vscode.dev/redirect |
| Keys and headers | HTTP entries accept a headers object whose values can read environment variables as ${NAME}. The portable files ignore input prompts, envFile and SecretStorage |
| Tool approval | New sessions start on Manual permissions, which show the tool name and its inputs for any call that is not auto-approved. The chat input dropdown also offers Assisted permissions, where an LLM judges each call, and Allow all. Autopilot approves every tool |
| Plan | GitHub includes MCP on Copilot Free, Student, Pro, Pro+, Max, Business and Enterprise. Business and Enterprise seats additionally need the MCP servers in Copilot policy, off by default |
| Admin controls | allowedMcpServers and deniedMcpServers in enterprise-managed settings match a server by URL, command or name, and a local file cannot lift a block. chat.mcp.access set to none turns MCP off |
| Managing a server | Each entry in MCP Servers has a toggle and an ellipsis menu with Start, Stop, Enable or Disable, Uninstall and Show Output, plus Authenticate when a sign-in is pending. MCP: List Servers offers the same actions |
| Tool cap | 128 enabled tools per chat request. Past that, VS Code answers Cannot have more than 128 tools per request. |
Sources: VS Code MCP servers, VS Code MCP configuration reference, VS Code: manage MCP servers, VS Code MCP developer guide, VS Code tool approvals, VS Code agent harnesses, VS Code enterprise AI settings, GitHub: extend Copilot Chat with MCP, GitHub Copilot plans. Checked November 14, 2026.
Other editors and assistants
The same URL works in other MCP clients. HubSpot is approved once in Ryze AI, so nothing changes on the HubSpot side.
Cursor
Cursor has its own mcp.json and its entries use mcpServers with a url field, where the older VS Code format uses servers. Check the key before you move a file from one editor to the other. How to connect Cursor to HubSpot.
Claude and Claude Code
Claude takes the same URL under Customize, Connectors, and Claude Code takes it from the command line. How to connect Claude to HubSpot.
ChatGPT
ChatGPT takes the same URL as a custom MCP app. Its plan rules differ from Copilot's, so follow its own guide. How to connect ChatGPT to HubSpot.
HubSpot access and the scopes Ryze AI requests
Two sign-ins are involved: HubSpot's, done once in Ryze AI, and the Ryze AI sign-in that VS Code starts. Four things decide what Copilot Chat can reach in HubSpot.
- Which HubSpot account
- Each connection is one HubSpot portal. One workspace can hold several portals. One is the primary (starred) and is used unless you name another, and the tools accept an optional connection_id.
- Which permissions HubSpot grants
- The HubSpot sign-in asks for read and write on contacts, companies and deals, read on owners, read on the contact and deal schemas, write on the deal schema, read on lists, and content access for blog posts. Optional scopes include files, CMS functions, knowledge base and membership.
- What the token covers
- HubSpot's OAuth guide says an access token reflects the scopes the app requested and not the limits of the user who approved it. Its example: a user who can view only the contacts they own can still authorize a token that reads every contact in the account.
- What VS Code asks
- A server saved in Copilot Global may ask for your trust before it starts, and may ask again after its entry changes. The Ryze AI sign-in runs when the connector requests it, and Authenticate in the ellipsis menu restarts it. Manual permissions then hold each HubSpot call that is not auto-approved, with the tool name and inputs on screen.
Scopes behind each action
The table maps what you ask Copilot Chat to do to the HubSpot access involved, using the scopes Ryze AI documents for its HubSpot connection.
| Action in Ryze AI | HubSpot access |
|---|---|
| Read contacts, companies and deals | Read scopes on those objects |
| Create or update a contact, company or deal | Write scopes on those objects |
| Look up account owners | Owners read |
| Read contact lists | Lists read. Editing lists is not claimed |
| Read or edit blog posts | Content scope |
| Add associations between records | Done through the write tool, within the write scopes above |
What each HubSpot scope opens
Ryze AI words its HubSpot access as eight required parts and four optional ones. For each, the table names the matching entry in HubSpot's scope reference, what HubSpot says it allows, and which HubSpot accounts have it. The exact scope strings inside the Ryze AI app were not read for this guide, and HubSpot's consent screen shows them when you approve. The Ryze AI listing in the HubSpot Marketplace names eight kinds of shared data that line up with the required parts: contacts, contact properties, companies, deals, deal properties, contact lists, owners and CMS blog posts.
| What Ryze AI asks for | HubSpot scope entry | What HubSpot says it allows | Which accounts have it |
|---|---|---|---|
| Contacts, read and write (required) | crm.objects.contacts.read, crm.objects.contacts.write | View contact details; create, delete and change contacts | All accounts |
| Companies, read and write (required) | crm.objects.companies.read, crm.objects.companies.write | View company details; create, delete and change companies | All accounts |
| Deals, read and write (required) | crm.objects.deals.read, crm.objects.deals.write | View deal details; create, delete and change deals | All accounts |
| Owners, read (required) | crm.objects.owners.read | See which users are assigned to a CRM record | All accounts |
| Contact schema, read (required) | crm.schemas.contacts.read | See how contact properties are configured | All accounts |
| Deal schema, read and write (required) | crm.schemas.deals.read, crm.schemas.deals.write | See and change how deal properties are configured | All accounts |
| Lists, read (required) | crm.lists.read | See the details of contact lists | All accounts |
| Content (required) | content | Content APIs such as website pages, landing pages and blogs | CMS Hub or Marketing Hub, Professional or Enterprise |
| Files (optional) | files | The file manager, through a legacy scope; HubSpot asks existing apps to move to granular scopes such as files.read | All accounts |
| CMS functions (optional) | cms.functions.read, cms.functions.write | Content Hub serverless functions and their secrets | Content Hub Enterprise |
| Knowledge base (optional) | cms.knowledge_base.articles.read and related entries | Knowledge articles, read through the GraphQL API | Service Hub Professional or Enterprise |
| Membership (optional) | cms.membership.access_groups.read, cms.membership.access_groups.write | Membership access groups | Service Hub or Content Hub, Professional or Enterprise |
Required and optional parts behave differently at install. If the chosen portal cannot grant a required scope, HubSpot shows an error and the install stops. An optional scope the portal lacks is dropped from the request without a prompt. Whether a portal below CMS Hub or Marketing Hub Professional can finish the Ryze AI install was not tested for this guide.
Outside the Ryze AI access: tickets, custom objects, list editing (crm.lists.write), company property settings (crm.schemas.companies.read) and the Sensitive Data scopes, which HubSpot lists as separate entries. A ticket search through Ryze AI was refused on November 14, 2026. HubSpot's remote MCP server and its Agent CLI both reach tickets and custom objects, and the ways table below covers them.
Sources: HubSpot scopes, HubSpot OAuth guide, HubSpot: install apps, Ryze AI listing in the HubSpot Marketplace, Ryze AI help center page for HubSpot. Checked November 14, 2026.
Removing access
To stop access from VS Code, open Chat: Open Customizations, select MCP Servers and disable or uninstall the ryze server from its ellipsis menu. Stop is weaker, since it ends the current run and a later request can start the server again. To end HubSpot access, click View on the HubSpot card in Ryze AI and use the trash icon beside the portal, or inside HubSpot go to Settings, Integrations, Connected Apps, Actions, Uninstall and type uninstall to confirm.
What Copilot Chat can do in HubSpot
The Ryze AI connector exposes 5 HubSpot tools: 3 read, 1 write and 1 delete. Each takes a workspace and an optional connection_id that picks one of the connected portals. Writes and deletes are separate tools, so VS Code can ask about them on their own.
| 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. |
Some limits hold in every client. CMS source-code file endpoints return raw files and fail through the read tool. HubSpot returns a default subset of properties unless you request specific fields. Deleted blog posts may not be recoverable, while most CRM deletes go to HubSpot's recycling bin. Tool descriptions mention custom objects, but the requested permissions do not include them, so this page does not claim custom object support.
A new VS Code session uses Manual permissions unless a setting or an organization default says otherwise, so a HubSpot call that is not auto-approved shows its tool name and inputs before it runs. Watch Chat: Manage Tool Approval, because its top-level checkbox for ryze trusts every tool on the server, hubspot__delete included. Setting a tool to false in chat.tools.eligibleForAutoApproval keeps it on manual approval, while Allow all and Autopilot approve everything. The Ryze AI chat itself starts on Skip all approvals, and its Tool approvals picker can switch to Approve write & delete or Manual approve. Scheduled tasks run without an approval step.
Calls tested through the connector
Each row is one read-only call that went through the Ryze AI connector on November 14, 2026, to a HubSpot portal already linked in a workspace. Claude Code sent the calls, and it reaches the same server and the same tools that VS Code does. Filters matched nothing and IDs were invented, so no record from that portal appears here.
| Request | Tool and input | What came back |
|---|---|---|
| Find a contact by email | hubspot__search, email EQ a random 20-letter string | A valid empty answer: {"total":0,"results":[]} |
| Find a company by domain | hubspot__search, domain EQ 20 random letters | Valid, same empty shape |
| Find a deal by name | hubspot__search, dealname EQ 20 random letters | Valid, same empty shape |
| Page through contacts | hubspot__listObjects, limit 1, property hs_object_id | One result with id, properties, createdAt, updatedAt, archived and url, plus paging.next with after and link. HubSpot added createdate and lastmodifieddate unasked |
| Filter on a missing property | hubspot__search on contacts with an invented property name | Refused, Error 400 |
| Ask for 201 results | hubspot__search on contacts, limit 201, a filter that cannot match | Refused, Error 400 with the category VALIDATION_ERROR |
| Search tickets | hubspot__search on tickets, a filter that cannot match | Refused with status not_allowed |
| Read deal 0 | hubspot__read of crm/v3/objects/deals/0 | status not_found |
| Read an absent contact | hubspot__read of a contact path with an 18-digit ID | status not_found, after HubSpot returned an HTML 404 page |
| Read an absent blog post | hubspot__read of cms/v3/blogs/posts/ with an 18-digit ID | status not_found, the same HTML 404 |
| Read blog post 1 | hubspot__read of cms/v3/blogs/posts/1 | status not_found again. Neither blog call shows whether blog reads work on that portal |
Limits in numbers
HubSpot sets most of these numbers, in its own units. The listObjects and path rows come from the Ryze AI tool definitions, and the last row is VS Code's. The first row is HubSpot's rule for OAuth apps distributed through the HubSpot Marketplace. Ryze AI signs in with OAuth and has a Marketplace listing, yet HubSpot's page does not name Ryze AI and no response in the test carried a rate limit header. So the row states HubSpot's general rule, and no call measured it for Ryze AI.
| Limit | Figure | Source |
|---|---|---|
| Publicly distributed OAuth apps | 110 requests every 10 seconds for each HubSpot account that installs the app. The CRM Search API is excluded from this figure, and the API limit increase add-on does not raise it | HubSpot usage guidelines |
| Privately distributed apps, Free and Starter | 100 requests per app every 10 seconds and 250,000 per account per day | HubSpot usage guidelines |
| Privately distributed apps, Professional | 190 requests per app every 10 seconds and 625,000 per account per day | HubSpot usage guidelines |
| Privately distributed apps, Enterprise | 190 requests per app every 10 seconds and 1,000,000 per account per day | HubSpot usage guidelines |
| Past a limit | HubSpot answers 429 to later calls. The daily count resets at midnight in the account's time zone, and errors should stay under 5% of a day's requests | HubSpot usage guidelines |
| CRM Search API | 5 requests per second per account. Search responses carry no rate limit headers | HubSpot CRM search |
| One search page | 10 records when no limit is given and 200 at most. A request for 201 was refused in the test | HubSpot CRM search |
| Results per search query | 10,000 in total. Paging past 10,000 returns a 400 error | HubSpot CRM search |
| Search filters | Up to 5 filter groups with 6 filters each, 18 filters in all. A request over 3,000 characters returns a 400 error | HubSpot CRM search |
| New records in search | A new or updated record can take a few moments to appear. Archived records never appear | HubSpot CRM search |
| hubspot__listObjects page | Up to 100 records per page, also the most contacts HubSpot returns in one request | Ryze AI tool definition, 2026-11-14 |
| Path in read, write and delete | Up to 2,048 characters | Ryze AI tool definition, 2026-11-14 |
| Access token | Expires after 30 minutes. The app renews it with the refresh token | HubSpot OAuth tokens |
| Recycling bin | Deleted CRM records can be restored for 90 days. Permanent and GDPR deletions skip the bin | HubSpot restore deleted records |
| VS Code | 128 enabled tools per chat request | VS Code tools |
Sources: HubSpot usage guidelines, HubSpot CRM search, HubSpot OAuth tokens, HubSpot restore deleted records, VS Code tools, Ryze AI help center page for HubSpot. Checked November 14, 2026.
First 3 prompts to run
These prompts use only what the 5 tools document. What comes back is your own HubSpot data, so no sample output is shown.
1. Review your open deals
List the HubSpot deals that are still open with deal name, amount, stage and owner, sorted by close date.
Tools used: hubspot__search or hubspot__listObjects, hubspot__read for owners
What comes back: A list of deals with the properties you named. Nothing is changed.
2. Find recent contacts
Search HubSpot contacts created in the last 14 days and show first name, last name, email and lifecycle stage.
Tools used: hubspot__search
What comes back: The matching contacts with the chosen properties, found through the CRM Search API. Nothing is changed.
3. Update a deal and link a contact
Move the deal named Example deal to the next stage and associate it with the contact with email name@example.com. Read the deal back afterwards.
Tools used: hubspot__search, hubspot__write, hubspot__read
What comes back: A write call that updates the deal and adds the association once you approve it in VS Code, then a read so you can compare the stored values with your request.
Replace the example names and the email with your own records. Read each write and delete call before you approve it in VS Code.
10 jobs to hand to Copilot Chat
Ten jobs to type into Copilot Chat once the ryze server is running, each with the tool behind it and whether the default Ryze AI connection can do it. In the November 14, 2026 test, searches and a contact list ran with inputs that returned nothing or one record. The owner, list and property reads and every change were not run. Jobs that change HubSpot use the write or delete tool.
| Job | Ask Copilot | Tool | On the default connection |
|---|---|---|---|
| Pipeline review | List open deals with amount, stage and close date, grouped by stage. | hubspot__search | Yes |
| New contacts | Show contacts created this week with email and lifecycle stage. | hubspot__search | Yes |
| Company lookup | Find the company with this domain and list its contacts and deals. | hubspot__search, hubspot__listObjects | Yes. Associations were not requested in the test |
| Owner check | Which HubSpot owner is assigned to each of these deals? | hubspot__read on crm/v3/owners | Yes. Not run in the test |
| List read | Read the contact list I name and show how many records it returns. | hubspot__read on crm/v3/lists/{listId} | Yes, to read. Adding or removing members is outside the requested access. Not run in the test |
| Property definitions | Show the properties on deals with their types. | hubspot__read on crm/v3/properties/deals | Yes. Not run in the test |
| Create a contact | Create a contact with this name and email and associate it with this company. | hubspot__write | Yes, after you approve the call. Not run, because it changes the portal |
| Edit a blog post | Change the title of the blog post with this ID. | hubspot__write | Listed in the Ryze AI docs, not confirmed. The test read no real post, and HubSpot offers the content scope on CMS Hub or Marketing Hub Professional or Enterprise only |
| Remove a duplicate | Show me this duplicate contact, then delete it. | hubspot__delete | Yes, after approval. HubSpot keeps most deleted CRM records in its recycling bin for 90 days. Not run |
| Ticket queue | List the open tickets for this company. | hubspot__search | No. The ticket search in the test came back not_allowed |
5 ways to connect VS Code to HubSpot
Five ways can bring HubSpot into Copilot Chat in VS Code: four whose vendor page names VS Code, and HubSpot's remote server, which accepts any client that speaks OAuth with PKCE. They differ in where they run and how much of HubSpot they reach, and one reaches no CRM records at all. This guide treats the Ryze AI connector as the main way, because HubSpot is approved once inside Ryze AI, VS Code holds one hosted address, and read, write and delete stay separate tools. The other four were read on their own pages on November 14, 2026. None was set up for this guide.
| Way | Runs where | Setup in VS Code | What it reaches in HubSpot | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI at one address | Chat: Open Customizations > MCP Servers > Add Server (+), HTTP, ID ryze, saved to Copilot Global, or an mcpServers entry in a portable file. Sign in to Ryze AI in the browser. HubSpot is approved once in Ryze AI | Contacts, companies and deals to read, create, update and delete; owners and contact lists to read; CMS blog content. Several portals per workspace. No tickets or custom objects | 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, with a name and a redirect URL, to get a client ID and secret. HubSpot's page accepts any MCP client with OAuth and PKCE but does not name VS Code. VS Code's portable format has an oauthClientId field for pre-registered clients, and that route was not tried here. Whether HubSpot accepts VS Code's redirect addresses was not checked | 36 documented tools for CRM records, tickets and custom objects included, activities, campaigns and content, within the user's own HubSpot permissions. The website page, blog post and render tools are limited to Claude, ChatGPT and Gemini. No delete tool | No price stated. Open to all HubSpot accounts since April 13, 2026. The AEO tools need Marketing Hub Professional or Enterprise |
| HubSpot Developer MCP server | On your computer, as the server HubSpotDev | Install the HubSpot CLI with npm install -g @hubspot/cli, version 8.2.0 or higher, run hs mcp setup, pick VS Code from the clients and restart VS Code. For VS Code the code command must be in your PATH | 23 tools for HubSpot's developer docs, projects, builds, test accounts and CMS templates, modules and functions. No CRM records | No price stated |
| Composio | Hosted | Composio's ChatGPT page for HubSpot links guides for other clients, VS Code among them, and those steps were not opened for this guide. Its hosted MCP address is https://connect.composio.dev/mcp, and VS Code takes a hosted address as an HTTP server. HubSpot is linked through Composio's managed OAuth app, your own OAuth app or an API key | 354 HubSpot tools and 2 triggers by Composio's count, including batch create, update and archive | Free plan: 10,000 tool calls a month. Standard: $18 per seat per month |
| Zapier MCP | Hosted | Zapier lists VS Code among its other MCP clients. Add Zapier MCP and sign in, and Zapier creates a default server that turns on actions for the apps already linked to your Zapier account | The HubSpot actions you turn on, such as Create Contact, Create Company and Create Associations. Zapier prints no total | 2 tasks per successful call, failed calls free. Free has 100 tasks a month; Professional starts at $19.99 per month billed annually |
HubSpot options that do not fit VS Code
- HubSpot's connectors for ChatGPT, Claude, Gemini and Copilot. HubSpot's AI tools page names these four assistants for its live connectors, and each help article covers its own assistant only. The Copilot one is the HubSpot Agent for Microsoft 365 Copilot, a different product from GitHub Copilot in VS Code.
- @hubspot/mcp-server (npm, beta). Its README gives setup for Claude Desktop, Cursor and other clients, and does not name VS Code. It needs a legacy private app token, and HubSpot stopped new private apps on September 28, 2026 for new accounts and October 26, 2026 for older ones. The newest version, 0.4.0, dates from June 18, 2025.
- HubSpot Agent CLI (beta). HubSpot describes it as a command-line tool for AI agents, naming Claude Code, Claude Cowork and OpenAI Codex, and its skills README names Claude Code, Cursor and Windsurf. VS Code is not named.
- HubSpot plugins for Claude Code. The HubSpot/hubspot-mcp-plugins repository has install steps for Claude Code and the Claude desktop app only.
- Windsor.ai and Coupler.io. Both give reporting access to HubSpot data and neither page names VS Code. Windsor.ai counts 1,141 HubSpot fields, and Coupler.io passes loaded datasets to the AI as aggregates.
- A Copilot connector for HubSpot. GitHub's supported connectors page listed 26 services on November 14, 2026, and HubSpot was not one of them. The list is in public preview and can change.
- baryhuang/mcp-hubspot. The most starred result of a GitHub search for hubspot mcp (129 stars) runs in Docker with a HubSpot access token. Its README gives setup for the Claude desktop app only.
Which one to pick
Ryze AI is the best way to connect VS Code to HubSpot for CRM records and blog content from one hosted address, with several portals in one workspace and no HubSpot token in your files, with one caveat: tickets, custom objects and list editing are outside its access. For those, and for the activity and revenue-object tools the Ryze AI connector does not list, HubSpot's remote MCP server reaches further, at the cost of an MCP connector you create in HubSpot and a VS Code sign-in setup this guide did not confirm. When you build a HubSpot app or CMS theme in VS Code, the Developer MCP server is the one HubSpot lists for VS Code, and Copilot can run it beside the ryze server. Composio and Zapier fit teams that already route other apps through them. VS Code caps a chat request at 128 tools, so switch off servers you do not need.
Sources: HubSpot remote MCP server, HubSpot Developer MCP server setup, HubSpot Developer MCP tools, HubSpot AI tools, HubSpot Agent CLI guide, @hubspot/mcp-server on npm, HubSpot plugins for Claude Code, baryhuang/mcp-hubspot, GitHub supported connectors, Composio HubSpot, Composio pricing, Zapier MCP for HubSpot, Zapier MCP other clients, Zapier MCP usage, Zapier pricing, Windsor MCP, Coupler.io HubSpot MCP, Ryze AI help center page for HubSpot. Checked November 14, 2026.
HubSpot, Copilot and MCP: dates that matter
| Date | What happened |
|---|---|
| April 4, 2025 | VS Code 1.99, the March 2025 release, came out with MCP server support in agent mode. GitHub's changelog entry on Copilot in 1.99 carries this date. |
| April 25, 2025 | HubSpot first published @hubspot/mcp-server on npm. |
| July 14, 2025 | GitHub called MCP in VS Code generally available and moved organization access to the MCP servers in Copilot policy, off by default. |
| September 1, 2025 | The remote HubSpot MCP server opened its first public beta. |
| February 19, 2026 | The HubSpot Developer MCP server, which lists VS Code among its clients, became generally available. |
| April 13, 2026 | The remote HubSpot MCP server became generally available to all HubSpot accounts, with write access and OAuth 2.1 with PKCE required. |
| September 15, 2026 | HubSpot's fall release gave the remote server custom objects, activable objects, Leads and read-only conversations, with quotes in public beta. |
| September 28, 2026 | New HubSpot accounts lost the option to create legacy private apps, and older accounts followed on October 26, 2026. Service Keys replace them, and private apps made earlier keep working. |
| September 30, 2026 | VS Code 1.140 added Copilot Global and the workspace .mcp.json as destinations in MCP: Add Server. |
| October 22, 2026 | VS Code 1.143 made the Copilot harness the default for new sessions. |
| October 28, 2026 | VS Code 1.144 and GitHub opened Copilot connectors in preview with 26 services. HubSpot was not among them on November 14, 2026. |
| November 11, 2026 | VS Code 1.146 deprecated the Local harness that reads .vscode/mcp.json, with removal announced for February 2027. |
| December 4, 2026 | HubSpot will sunset the Pipelines API V1, as its changelog announced. |
| January 8, 2027 | The HubSpot developer CLI stops supporting Node.js 20 and will need Node.js 22 or higher, as HubSpot announced on October 19, 2026. The Developer MCP server runs from that CLI. |
Sources: VS Code 1.99, GitHub changelog, April 4, 2025, @hubspot/mcp-server on npm, GitHub changelog, July 14, 2025, HubSpot MCP beta changelog, HubSpot Developer MCP server changelog, HubSpot remote server GA changelog, HubSpot fall 2026 spotlight, HubSpot private app sunset, VS Code 1.140, VS Code 1.143, VS Code 1.144, GitHub changelog, October 28, 2026, VS Code 1.146, HubSpot Pipelines API V1 sunset, HubSpot Node.js 20 sunset. Checked November 14, 2026.
How this guide was tested
On November 14, 2026, a signed-in MCP client sent the live Ryze AI connector 11 HubSpot calls, all read-only: 6 searches, 4 reads and 1 list. The connector's sign-in details had been probed without a login on November 13. The table sums up what came back.
| What was run | What came back |
|---|---|
| Request to the address with no sign-in (November 13) | HTTP 401 with a WWW-Authenticate header that points to the sign-in details. Per Microsoft's docs, when a server needs OAuth the Copilot runtime asks VS Code to run the sign-in. |
| The discovery files (November 13) | Both loaded. They list the authorize, token and register endpoints, the authorization code and refresh token grants, PKCE with S256, and the scopes mcp:read and mcp:write. The register endpoint is what Dynamic Client Registration needs, and Microsoft's MCP developer guide names that method for VS Code. |
| HubSpot tool definitions (November 14) | All 5 loaded by name. Each takes a workspace and an optional connection_id, and they match the tools table above. |
| Searches and one list (November 14) | Contact, company and deal searches gave valid empty answers. Listing contacts with limit 1 returned one result and a paging cursor. No record content was kept. |
| Calls meant to fail (November 14) | Seven: two searches with bad input, one ticket search and four reads of IDs that do not exist. Their exact messages are in the errors section. |
Not run: anything inside VS Code. The ryze server was not added to Copilot Global, no trust prompt or sign-in was seen, and Copilot Chat sent no tool call. The VS Code steps follow Microsoft's documentation pages dated November 11, 2026 and GitHub's Copilot docs, both read on November 14, 2026. The HubSpot calls came from Claude Code, a different client that reaches the same server and tools. The portal was already connected in Ryze AI, so the HubSpot sign-in was not repeated. hubspot__write and hubspot__delete were not run, because they change the portal. No record was read by ID, and owners, lists, property definitions and blog posts were not listed. The over-limit request went to hubspot__search only, not to hubspot__listObjects.
Errors and fixes
Five messages came back word for word in the calls of November 14, 2026. They come first, and the rest of the list follows the documentation of Ryze AI, HubSpot, Microsoft and GitHub, without a test behind it.
| Message | What it means | What to do |
|---|---|---|
| limit must be in range [0..200] (actual value: 201) | Error 400 with the category VALIDATION_ERROR. A CRM search page holds 200 records at most. | Ask Copilot for 200 or fewer per page and to continue with the after value. |
| There was a problem with the request. | Error 400 for a search filter on a property HubSpot does not have. HubSpot does not say which one. | Have Copilot read crm/v3/properties/contacts first and filter on 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. | status not_allowed. The default Ryze AI connection could not search tickets on the test portal. | Keep contacts, companies and deals on Ryze AI. For tickets in VS Code, use HubSpot's remote MCP server. |
| Object not found. objectId is usually positive. | status not_found. No deal has the ID 0. | Search for the record first and reuse the id from the result. |
| [hubspot] GET crm/v3/objects/contacts/{id}: provider returned text/html;charset=iso-8859-1 (status 404) "Error 404 Not Found" | status not_found. HubSpot answered an invented contact or blog post ID with an HTML page, and the read tool, which parses only JSON, reports the 404. The ID is shown as {id}, and the trace value at the end of the real message is left out. | Check the ID. Look the contact up by email, or list blog posts and take an ID from the list. |
- The MCP server does not start in VS Code
- On Copilot Business or Enterprise, ask an administrator to enable the MCP servers in Copilot policy, which ships off. Admins can also block a server with deniedMcpServers or turn MCP off with chat.mcp.access set to none, and a local file cannot override either. Check the version too: MCP needs VS Code 1.99 or later and Copilot Global needs 1.140.
- The sign-in never opens
- Trust and sign-in are separate steps, so trust the server first. Then choose Authenticate from the ellipsis menu of ryze in MCP Servers, or run MCP: List Servers to see its state. Show Output in the same menu opens the log. Email Ryze AI support if it stays stuck.
- An older tutorial does nothing
- Tutorials built on .vscode/mcp.json target the Local harness. New sessions have used the Copilot harness since VS Code 1.143, which reads ~/.copilot/mcp-config.json and the workspace .mcp.json. Add the server again through Chat: Open Customizations.
- No HubSpot tools appear
- If HubSpot was connected in Ryze AI after the server was added, remove the ryze server, add it again and start a new chat so the tool list refreshes.
- HubSpot will not let me approve the connection
- Your HubSpot user may be neither a Super Admin nor a holder of App Marketplace access, or the portal may lack a scope the app requires, which stops the install with an error. Ask a Super Admin to run the connection or to grant you the permission.
- Copilot shows the wrong portal
- Each connection is one portal. The primary (starred) portal is used unless you name another in the prompt or pass a connection_id.
- A search fails with a 400 error
- HubSpot rejects a search that pages past 10,000 results, uses more than 18 filters or is longer than 3,000 characters. Ask for a narrower filter or date range.
- Copilot reports too many requests
- HubSpot allows 5 search requests per second per account and answers 429 once an app passes its limits. Wait a few seconds, or ask for fewer records at a time.
- A CMS source file fails to read
- CMS source-code file endpoints return raw files and fail through the read tool. Read blog posts or pages through their JSON resources.
- A property is missing from a record
- HubSpot returns a default subset of properties unless fields are requested. For a contact search that set is firstname, lastname, email, lastmodifieddate, hs_object_id and createdate. Name the properties in the prompt, such as lifecycle stage or deal amount.
- Cannot have more than 128 tools per request.
- VS Code allows 128 enabled tools in one chat request. Deselect tools or whole MCP servers in the tools picker of the Chat view until the count drops.
- The tools reply that a subscription is required
- The HubSpot tools need an active Ryze AI plan or free trial. Start the trial in Ryze AI, then retry.
Terms on this page
- Agent Customizations editor
- The VS Code screen opened by Chat: Open Customizations. Its MCP Servers page adds, lists and manages servers.
- Copilot Global
- The personal MCP destination in VS Code, ~/.copilot/mcp-config.json, read in every workspace.
- Copilot harness
- The runtime behind Copilot sessions in VS Code and the default for new sessions since VS Code 1.143. It reads the portable mcpServers files.
- Portal
- A single HubSpot account. Every Ryze AI connection covers exactly one, and a workspace holding several marks one with a star as the default.
- CRM object
- A type of record in HubSpot, such as a contact, company or deal.
- Association
- A link between two CRM records, such as a contact and the deal it belongs to.
- Scope
- A named HubSpot permission, such as crm.objects.deals.read, that an app requests at install. Each one opens a set of API endpoints and the data behind them.
Sources: VS Code MCP servers, VS Code MCP configuration reference, HubSpot scopes, HubSpot CRM contacts guide, HubSpot associations guide. Checked November 14, 2026.
Frequently asked questions
How do I connect VS Code to HubSpot?
Connect HubSpot in Ryze AI under Integrations by signing in to HubSpot, choosing the portal and approving the permissions. In VS Code, with Copilot as the session target, run Chat: Open Customizations, select MCP Servers, choose Add Server, pick HTTP, enter https://connector.get-ryze.ai/mcp and the server ID ryze, trust the server and finish the Ryze AI sign-in.
Is there a HubSpot MCP server for VS Code?
Yes, in two forms. The Ryze AI connector at https://connector.get-ryze.ai/mcp has 5 HubSpot tools for your connected portal. HubSpot's local Developer MCP server lists VS Code as a client through hs mcp setup, but its 23 tools cover developer docs, projects and CMS assets, not CRM records. HubSpot's remote server at https://mcp.hubspot.com reaches CRM data without naming VS Code.
Which HubSpot server should I use in VS Code?
For contacts, companies, deals and blog posts through one address, use the Ryze AI connector, which needs a Ryze AI plan and leaves out tickets and custom objects. For tickets or custom objects, HubSpot's remote server reaches them but needs an MCP connector created in HubSpot. To build HubSpot apps or CMS assets, use the Developer MCP server.
What is the HubSpot MCP server URL for VS Code?
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 signs in through an MCP connector you create in HubSpot.
Is there a Copilot connector for HubSpot?
Not as of November 14, 2026, when GitHub's supported connectors page named 26 services and HubSpot was not one of them. That list is a public preview. For now, add HubSpot by server address, such as the Ryze AI connector. HubSpot's own Copilot product is a separate agent for Microsoft 365 Copilot.
Does the HubSpot Developer MCP server give Copilot my CRM data?
No. It lists VS Code as a supported client, but its 23 tools cover HubSpot's developer docs, projects, builds and CMS templates, modules and functions. It has no tool for contacts, companies or deals. For CRM records use the Ryze AI connector or HubSpot's remote server.
Which Copilot plan do I need?
Any plan. GitHub's plans tables include MCP on Copilot Free, Student, Pro, Pro+, Max, Business and Enterprise, and GitHub's MCP article asks for VS Code 1.99 or later. Copilot Free, Pro, Pro+ and Max are outside the MCP policy. On Business or Enterprise through an organization, an administrator must enable the MCP servers in Copilot policy, which is off by default.
Can Copilot Chat edit my HubSpot contacts and deals?
Yes. Through Ryze AI, Copilot Chat can create and update contacts, companies, deals and blog posts and add associations between records with the write tool. New VS Code sessions start on Manual permissions, so a call that is not auto-approved shows its tool name and inputs first.
Can Copilot Chat delete HubSpot records?
Only through the separate hubspot__delete tool, which archives a resource by ID. Most CRM deletes go to HubSpot's recycling bin, but deleted blog posts may not be recoverable. Allow all, Autopilot or a server-wide approval in Chat: Manage Tool Approval skips the check, so keep the ryze server on manual approval if you want to review deletes.
Can Copilot read HubSpot tickets through Ryze AI?
No. A ticket search through the default Ryze AI connection was refused with status not_allowed on November 14, 2026, and tickets are not among the data the Ryze AI listing in the HubSpot Marketplace shares. HubSpot's remote MCP server and its Agent CLI both reach tickets.
Does this support custom objects or editing lists?
This page does not claim either. Tool descriptions mention custom objects, but the permissions Ryze AI requests do not include custom-object scopes, and lists are read only.
Which config file should I use?
For new setups use the portable format: ~/.copilot/mcp-config.json or .mcp.json at the workspace root, with the key mcpServers. The .vscode/mcp.json file with the key servers belongs to the Local harness, which VS Code 1.146 deprecated, with removal announced for February 2027.
Can I connect more than one HubSpot portal?
Yes. One workspace can hold several portals. One is the primary and is used unless you name another, and the tools accept an optional connection_id. Each connection is one portal, and you choose the workspace on the Ryze AI page during the sign-in from VS Code.
Why do the HubSpot tools not show up in VS Code?
If you connected HubSpot in Ryze AI after adding the server, remove the ryze server, add it again and start a new chat. Also confirm that you trusted the server and finished the Ryze AI sign-in, which are separate steps, and expand a tool call to see which server answered.
How much does it cost to connect VS Code 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, and Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect HubSpot from VS Code?
In Chat: Open Customizations, select MCP Servers and disable or uninstall the ryze server from its ellipsis menu. To end HubSpot access itself, disconnect the portal on the HubSpot card in Ryze AI, or uninstall the app inside HubSpot.