This is a reposting of the HubSpot Developer changelog post announcing the MCP server, if there are any differences between this post and the changelog, changelog always takes precedent as the official source of truth. https://developers.hubspot.com/changelog/mcp-server-beta
---
The HubSpot MCP server is now available in public beta. It allows AI clients such as Cursor and Claude to interact with HubSpot data and unlocks powerful integration possibilities.
What is MCP?
MCP (Model Context Protocol) is an emerging standard that allows AI models to interact with applications through a consistent interface. It acts as an abstraction layer over traditional APIs, letting AI agents access application functionality without needing to understand specific API protocols.
What does the HubSpot MCP Server do?
Interact with business-critical tools, such as HubSpot’s Smart CRM, through natural language AI applications like Claude Desktop to create and update objects, notes, and tasks tied to the way your business operates.
The current MCP tools in this server enable you to:
Retrieve, create, or update HubSpot objects
List HubSpot objects and their properties
Access and create associations between objects
Create tasks and notes in your HubSpot account
Open specific screens within the HubSpot UI
Provide feedback on the MCP server through natural language
To help put it into perspective here are some examples of prompts that your AI client could handle with the HubSpot MCP Server.
Streamline your development
"Get the company record for Google and place it in a JSON file that I can reference in my code as a placeholder as work on the UI for my UI Extension, website module, and template."
"I don't know if the sales reps have been using a custom property called "Serial number" properly can you fetch 100 part records and let me know what data type that property is, and any rules that seem to apply to that data so I can create a regex in my application to ensure consistency?"
"I just ran a serverless function locally and want to test that the record is properly updated. Can you look at my log to see which record I updated and then look up that record in my CRM to see if that change is reflected?"
Get insights from your HubSpot data
"Get me the latest update about Acme Inc. from my HubSpot account."
"Summarize all deals in the “Decision maker bought in” stage in my HubSpot pipeline with deal value > $1000."
"Summarize the last five tickets created for Alex Smith in my HubSpot account"
Create and update CRM records
"Update the address for John Smith in my HubSpot account"
"Create a new contact “John.Johnson@email.com” for Acme Inc. in my HubSpot account."
CRM associations
"List all associated contacts and their roles for Acme Inc, from my HubSpot account."
"List associated contacts for Acme Inc in my HubSpot account"
"Associate John Smith with Acme Inc. as a company in my HubSpot account"
Add engagements
"Add a task to send a thank-you note to jane@example.com in my HubSpot account"
"Add a note for Acme. Inc. in my HubSpot account"
"List my overdue HubSpot tasks"
“From my HubSpot account, find the number of contacts <company-name> has.”
Get started
The HubSpot MCP server is available as an NPM package that you can easily install and configure. To get started, all you need to do is copy the configuration JSON to your client apps (for example, Claude desktop) with your HubSpot private app access token.
HubSpot’s MCP public beta is only the beginning. We want your feedback on the use cases you build and the problems you solve. Alternatively, use a prompt, like “provide feedback for the HubSpot MCP Server” from your client application!
Note: LLM's are prone to hallucination, always review when prompted for permission to use an MCP tool that makes changes to your account, if those changes reflect what you requested. If you'd like to experiment with full write and delete permissions we recommend doing so in a developer sandbox or other non-production account. This product will evolve to include more functionality and an improved authentication system.
I’ve been trying for the past two days to get the mcp-hubspot app installed using Smithery CLI, and I keep running into issues that are blocking progress. Here’s a breakdown of what I’ve encountered so far in case anyone else has been through this—or better yet, found a fix.
Latest Error:
When I run the following command: npx -y @smithery/cli@latest install mcp-hubspot --client claude
I get this:: ✖ Failed to install mcp-hubspot Error: Package resolution failed with status 500: Internal server error
This seems to be a backend issue—possibly with the package registry or Smithery service—but I haven’t found any documentation or status updates confirming this.
Other Issues Faced Previously:
Smithery CLI glitches
The install command doesn’t always resolve dependencies smoothly, especially when scoped packages or custom clients like --client claude are involved.
HubSpot CMS compatibility issues
Even when I managed to install other packages, I ran into version mismatches or incomplete configurations that required manually editing theme.json, fields.json, and other project scaffolding files.
Lack of documentation
There’s very little documentation or step-by-step guidance for MCP-related packages or Smithery workflows beyond simple use cases. Advanced setups with custom clients or integrations (e.g., Claude, GPTs, etc.) are totally absent.
Ambiguous errors from CLI
Most CLI errors aren’t descriptive and don’t provide actionable feedback, making troubleshooting extremely difficult. Even adding --debug doesn’t help much beyond a stack trace.
Ask:
Has anyone in the community successfully installed mcp-hubspot using Smithery CLI recently? If so:
What command did you use?
Which Node/npm version are you on?
Any tweaks to .env or file structure?
Did you face and resolve this 500 error?
I’d really appreciate any insights. It’s a promising setup, but these issues make onboarding extremely frustrating.
Replace YOUR_PUBLIC_IP and YOUR_PORT: Set these to the public IP address and port you want the MCP server to be accessible from. For example, -p 203.0.113.10:8050:8000 will expose the server on IP 203.0.113.10 and port 8050.
Replace your_hubspot_token: Use your actual HubSpot Private App Access Token here. This token allows the MCP server to authenticate with your HubSpot account.
Replace your_authorization_key: This is the bearer token used by the supergateway to authorize requests. Ensure it's a secure, randomly generated string.
This setup uses the supercorp/supergateway Docker image to expose the MCP server over Server-Sent Events (SSE), enabling remote connections. It's a quick way to make the server accessible externally.
However, please be aware that this method is not the most secure or elegant solution for production environments.
The supergateway serves as a bridge, allowing you to expose any MCP server that communicates over standard input/output (stdio), like the one provided by HubSpot. This is particularly useful for testing and development purposes.
Nice work! it’s clean, practical, and solves a real need we have. We’re already testing it at HostDime Brasil and it's fitting in well with our Stack.
Quick question: have you run any benchmarks using open-source LLMs? Curious to hear what models and parameters gave you the best results.
We’ve set up a flow using n8n, exposing MCP Server via supergateway as an SSE endpoint, which allows the native MCP client node in n8n to connect to it seamlessly.
LLM-wise, we’ve had the most consistent performance running Qwen3:latest, temperature around 0.1, and a 16k context window.
Best,
--
Filipe Mendes
🌐hostdime.com.br Most certified data center in Latin America
Fully owned infrastructure. No shortcuts. Full control.
.png "HubSpot Employee"){kind=icon}
