A Model Context Protocol (MCP) server that enables AI assistants to interact with HubSpot CRM data, providing built-in vector storage and caching
Connect HubSpot to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server that enables AI assistants to interact with HubSpot CRM data, providing built-in vector storage and caching mechanisms help overcome HubSpot API limitations while improving response times. The hubspot mcp server is what makes that connection.
A Model Context Protocol (MCP) server that enables AI assistants to interact with HubSpot CRM data. This server bridges AI models with your HubSpot account, providing direct access to contacts, companies, and engagement data. Built-in vector storage and caching mechanisms help overcome HubSpot API limitations while improving response times.
The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
hubspot_create_contact — Create contacts with duplicate preventionhubspot_create_company — Create companies with duplicate preventionhubspot_get_company_activity — Retrieve activity for specific companieshubspot_get_active_companies — Retrieve most recently active companieshubspot_get_active_contacts — Retrieve most recently active contactshubspot_get_recent_conversations — Retrieve recent conversation threads with messageshubspot_search_data — Semantic search across previously retrieved HubSpot dataPrerequisites — You'll need a HubSpot access token with these scopes: - crm.objects.contacts (read/write) - crm.objects.companies (read/write) - sales-email-readConfiguration is passed through the environment: HUBSPOT_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
You'll need a HubSpot access token with these scopes: - crm.objects.contacts (read/write) - crm.objects.companies (read/write) - sales-email-read
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. HubSpot's toolset — hubspot_create_contact, hubspot_create_company, hubspot_get_company_activity and 5 more — is a fair guide to whether it matches your workflow. It is maintained by peakmojo; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| hubspot_create_contact | Create contacts with duplicate prevention |
| hubspot_create_company | Create companies with duplicate prevention |
| hubspot_get_company_activity | Retrieve activity for specific companies |
| hubspot_get_active_companies | Retrieve most recently active companies |
| hubspot_get_active_contacts | Retrieve most recently active contacts |
| hubspot_get_recent_conversations | Retrieve recent conversation threads with messages |
| hubspot_search_data | Semantic search across previously retrieved HubSpot data |
| Prerequisites | You'll need a HubSpot access token with these scopes: - crm.objects.contacts (read/write) - crm.objects.companies (read/write) - sales-email-read |
{
"mcpServers": {
"hubspot-peakmojo": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"HUBSPOT_ACCESS_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
You'll need a HubSpot access token with these scopes: - crm.objects.contacts (read/write) - crm.objects.companies (read/write) - sales-email-read
| Variable | Description | Required |
|---|---|---|
| HUBSPOT_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.