hubspot-conversations-mcp
This MCP server provides 24 tools to manage HubSpot Conversations, including reading and sending messages, managing threads, handling inboxes and channels, and integrating custom communication channels.
Thread Management: List and search threads with filters (inbox, status, contact, ticket, time). Retrieve thread details, update status (OPEN/CLOSED), archive (soft-delete, permanent after 30 days), or restore threads.
Message Operations: Access message history (including comments and system events) in a thread. Retrieve individual messages, fetch full untruncated content, and send new messages or internal comments (auto-derives channel and sender).
Inbox, Channel, and Actor Insights: List and get details for conversation inboxes, channels (email, chat, WhatsApp, etc.), and channel accounts (specific addresses/numbers). Batch-resolve actor IDs to participant profiles.
Custom Channel Integration: Create and manage accounts on custom channels, update account info (name, authorization), finalize staging connections, publish external messages into HubSpot, and update message delivery status (SENT, FAILED, READ).
Provides tools for interacting with the HubSpot Conversations API, enabling AI agents to manage conversation threads, messages, inboxes, channels, and custom channels.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hubspot-conversations-mcp Show me my recent conversation threads"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
hubspot-conversations-mcp
MCP server for the HubSpot Conversations API — 24 tools to read conversation threads and messages, send replies, manage threads and channel accounts, and integrate custom channels, from any MCP client (Claude Code, Claude Desktop, Hermes, etc.).
Covers two HubSpot API surfaces:
Conversations API (
/conversations/conversations/2026-09-beta) — threads, messages, inboxes, channels, actorsCustom Channels API (
/conversations/custom-channels/2026-03) — channel accounts, staging tokens, publishing external messages, delivery status
How authentication works
There is exactly one way to authenticate: per-user OAuth via your organization's broker.
Every user signs in with their own HubSpot login — tokens are issued individually, stored only on their machine (~/.hubspot-conversations-mcp/tokens.json, 0600), revocable per user, and die when the user is deactivated in HubSpot. No shared credentials exist anywhere.
The broker is a small stateless service your org hosts (free on Vercel, api/ in this repo). It is the only place your HubSpot app's client secret lives; it exchanges authorization codes and refreshes tokens, stores nothing, and never sees Conversations data — all API traffic goes directly from the user's machine to HubSpot.
Related MCP server: hubspot-mcp
Org setup (one-time, ~10 minutes)
Create a HubSpot app (in a developer account, e.g. as a developer-projects app): use
"distribution": "private"and allowlist your portal. Theauthblock ofapp-hsmeta.jsonshould look like:"auth": { "type": "oauth", "redirectUrls": ["http://localhost:4573/callback"], "requiredScopes": ["oauth", "conversations.read"], "optionalScopes": ["conversations.write"], "conditionallyRequiredScopes": [] }conversations.writeis optional, matching how the CLI requests it: the defaultloginsendsconversations.readin the authorize URL'sscopeparameter andconversations.writeinoptional_scope— HubSpot rejects the consent screen whenever that split does not match the app's configuration — except theoauthscope, which HubSpot grants automatically without it being requested. (Optional scopes are granted automatically when the portal supports them; a read-only sign-in means not requesting write at all — see below.) If your org uses custom channels, addconversations.custom_channels.read/conversations.custom_channels.writetooptionalScopesas well and request them at login via--optional-scopes.If you want read-only tokens (some agents may read conversations but never send, update or archive), create a second app with only the read scope — see Read-only vs read + write for why one app can't do both:
"auth": { "type": "oauth", "redirectUrls": ["http://localhost:4573/callback"], "requiredScopes": ["oauth", "conversations.read"], "optionalScopes": [], "conditionallyRequiredScopes": [] }Both apps live behind the same broker — the read-only app's credentials go in a second pair of env vars (next step), and
login --read-onlyselects it.Apps created from the pre-0.11 template (where
conversations.writesat inrequiredScopes): either move it tooptionalScopesas above (users re-authorize on their next login), or keep it required and have users sign in withlogin --scopes conversations.read,conversations.write— read-only sign-ins are not possible with that configuration.Deploy the app and note the client ID and client secret from its Auth tab.
Deploy the broker to Vercel — one click:
The button clones this repo and prompts for the two environment variables (
HUBSPOT_OAUTH_CLIENT_ID,HUBSPOT_OAUTH_CLIENT_SECRET). Alternatively create the Vercel project manually from your fork, or wire up CI deploys via deploy-broker.yml with theVERCEL_TOKEN/VERCEL_ORG_ID/VERCEL_PROJECT_IDrepo secrets.One deployment can front both apps:
Env var
App
HUBSPOT_OAUTH_CLIENT_ID/HUBSPOT_OAUTH_CLIENT_SECRETread + write (default)
HUBSPOT_OAUTH_READ_ONLY_CLIENT_ID/HUBSPOT_OAUTH_READ_ONLY_CLIENT_SECRETread-only (optional)
The client's
login --read-onlyselects the read-only app, and the choice travels with the tokens so refreshes use the right app's credentials. The broker's/api/configadvertises which apps exist and their scopes, sologinandsetuprequest exactly the right split automatically. Optional fine-tuning:HUBSPOT_OAUTH_SCOPES/HUBSPOT_OAUTH_OPTIONAL_SCOPESoverride what the default app's logins request (e.g. to add custom-channel scopes), andHUBSPOT_OAUTH_READ_ONLY_SCOPES/HUBSPOT_OAUTH_READ_ONLY_OPTIONAL_SCOPESdo the same for the read-only app (default: justconversations.read).Share the broker URL (e.g.
https://your-broker.vercel.app) with the team — it is not a secret, and neither is the client ID (the CLI fetches it from the broker's/api/config). SettingHUBSPOT_OAUTH_BROKER_URLorg-wide (dotfiles, MDM, onboarding docs) makes all commands flag-free.
Because the app is private-distribution and allowlisted, only your own org's portals can complete a login against your broker — each org runs its own broker with its own app, so tokens never cross organizational trust boundaries.
Per user
Interactive setup (recommended)
npx -y hubspot-conversations-mcp setupThe wizard walks through everything:
Broker — asks whether your org already has a broker; if not, it shows the setup guide (and links back here). The URL is verified live against
/api/configbefore continuing.Sign in — the wizard asks which access level to sign in with: read & write, or read-only (via the broker's read-only app when it has one, otherwise as a best-effort reduced-scope request). Brokers that advertise a scope profile decide the level themselves and skip the question. Then your browser opens HubSpot's consent screen; sign in with your own HubSpot login. Tokens land on your machine and auto-refresh through the broker.
Agents — pick which AI agents to configure with an arrow-key multiselect (↑/↓ to move, space to toggle): Claude Desktop, Claude Code, and/or Hermes (Nous Research hermes-agent). Each is configured automatically — no credentials are written to any config file.
Manual / scripted
npx -y hubspot-conversations-mcp login --broker-url https://your-broker.vercel.appnpx -y hubspot-conversations-mcp install --client all--client takes claude-desktop, claude-code, hermes, both (the two Claude clients), all, or a comma-separated combination:
claude-desktop — merges the server into
claude_desktop_config.json(existing servers preserved; timestamped backup first). Restart Claude Desktop afterwards.claude-code — runs
claude mcp add … -- npx -y hubspot-conversations-mcp(prints the command if theclaudeCLI is unavailable). Add--scope userto register across all your projects (the setup wizard defaults to this).hermes — merges the server into
~/.hermes/config.yamlundermcp_serverswithenabled: true(backup first; YAML comments are not preserved). Verify withhermes mcp test hubspot-conversations.
whoami shows the active sign-in, logout removes it. Use --dry-run to preview installs, --config-path / --hermes-config-path for non-standard config locations.
Read-only vs read + write
Write access is a property of the token, not of the server: the server looks at the
scopes granted at login and only registers the tools that token can actually use. HubSpot
enforces scopes server-side either way — the gating just keeps the tool list honest, so a
read-only sign-in gets a server without SendConversationMessage,
UpdateConversationThread or ArchiveConversationThread instead of tools that fail
with 403.
One app cannot give the same portal both access levels. HubSpot grants scopes per
app installation on the portal, not per authorization: once an app is connected with
write access, a later login requesting fewer scopes just re-attaches to the existing
grant and returns a token that still carries write (scopes only shrink when they are
removed from the app's auth settings entirely and the user reauthorizes — see HubSpot's
auth settings
and reauthorization
changelogs). The server will honestly show that: whoami reports read + write and the
write tools stay registered, because the token really can write.
Genuinely read-only tokens therefore come from a second, read-only app (org setup
above): an app whose only conversations scope is conversations.read, registered on the
same broker via HUBSPOT_OAUTH_READ_ONLY_CLIENT_ID / HUBSPOT_OAUTH_READ_ONLY_CLIENT_SECRET.
login --read-only signs in through that app — its tokens can never write, no matter
what is requested — and the profile travels with the stored tokens so refreshes keep
using the right app. Use a separate token store to keep it next to your main sign-in:
HUBSPOT_TOKEN_STORE_PATH=~/.hubspot-conversations-mcp/tokens-ro.json \
npx -y hubspot-conversations-mcp login --broker-url https://your-broker.vercel.app --read-onlyThen register a second MCP entry pointing at that store, e.g. for Claude Code:
claude mcp add hubspot-conversations-ro --env HUBSPOT_TOKEN_STORE_PATH=$HOME/.hubspot-conversations-mcp/tokens-ro.json -- npx -y hubspot-conversations-mcpThe default registration keeps the read + write token; hubspot-conversations-ro only
ever sees the 13 read tools — and its token couldn't write even outside MCP.
Details:
--read-onlyrequires the broker to have the read-only app configured (loginfails with a pointer here otherwise). Without a second app, the wizard's "Read-only (best effort)" choice — or--scopes conversations.read— requests a reduced grant from the main app, which yields a truly read-only token only if the app was never granted write on that portal (otherwise the existing grant wins, see above).When the broker advertises a scope profile for its default app (
HUBSPOT_OAUTH_SCOPES), plainloginrequests exactly that; a wizard run against such a broker (with no read-only app) shows the resulting access level instead of asking.--scopessets the app-required scopes and--optional-scopesthe app-optional ones, e.g.--optional-scopes conversations.write,conversations.custom_channels.read,conversations.custom_channels.write— custom-channel tools are likewise only offered when theconversations.custom_channels.*scopes were granted. HubSpot rejects the consent screen if the split does not match the app's scope configuration.The rare token store without recorded scopes (scope introspection failed during a pre-0.11 login) makes the server offer all tools, with HubSpot alone enforcing access; since 0.11
loginalways records scopes, falling back to the requested ones. Re-runloginto fix such a store.Upgrading from 0.10: tokens signed in with the default scopes never carried
conversations.custom_channels.*, so the 8 custom-channel tools disappear from the tool list on upgrade — they previously appeared but always failed with 403. Re-login with--optional-scopesincluding those scopes (and the app updated to offer them) to use them.whoamiprints the access level of the active sign-in (from the token's live scopes when reachable).The tool list is fixed when the server starts — after changing access level with a re-login, restart the MCP client/server to apply the new gating.
Broker endpoints
Endpoint | Purpose |
| Public app metadata (client IDs and scope profiles of the configured apps) so users only need the broker URL |
|
|
|
|
One-click bundle for Claude Desktop (MCPB)
The repo ships a manifest.json following Anthropic's MCP Bundle format:
npm run bundleThis produces a .mcpb file. Open it with Claude Desktop (or drag it into Settings → Extensions) for a one-click install. Run npx -y hubspot-conversations-mcp login once first — the extension uses the same per-user sign-in.
Releasing to npm
Releases ship automatically from main. Bump version in package.json and manifest.json plus SERVER_VERSION in server.ts — all three must match — and merge. The release workflow spots that the version isn't on npm yet, runs the tests, creates the v<version> tag + GitHub release with generated notes, and publishes that release to npm with provenance (auth via the NPM_TOKEN repo secret). Pushes without a version bump are no-ops.
prepublishOnly builds and runs the full test suite before the actual upload. The published package contains only dist/, manifest.json, README and LICENSE.
Configuration
Environment variable | Description |
| Your org's broker URL, used by |
| OAuth token store location (default |
| Default sender for |
| Default |
| Default |
| Default |
On the broker deployment (never on user machines): HUBSPOT_OAUTH_CLIENT_ID / HUBSPOT_OAUTH_CLIENT_SECRET (read + write app), optionally HUBSPOT_OAUTH_READ_ONLY_CLIENT_ID / HUBSPOT_OAUTH_READ_ONLY_CLIENT_SECRET (read-only app used by login --read-only), and optionally HUBSPOT_OAUTH_SCOPES / HUBSPOT_OAUTH_OPTIONAL_SCOPES (+ _READ_ONLY_ variants) to override the scopes logins request.
Tools
Tool availability follows the scopes granted at login (see
Read-only vs read + write): read tools need
conversations.read, write tools need conversations.write, and the custom-channel
group needs conversations.custom_channels.read / .write. Tokens with no recorded
scopes get all 24 tools.
Threads
Tool | Description |
| List/search threads — filter by inbox, OPEN/CLOSED, contact, ticket, time window; paginated |
| Get a single thread (status, inbox, channel, assignee, contact) |
| Set OPEN/CLOSED, archive or restore a thread |
| Soft-delete a thread (permanently deleted after 30 days) |
Messages
Tool | Description |
| Message history of a thread (messages, comments, system events); paginated |
| Get a single message |
| Original (untruncated) text/richText of a message |
| Send a message to the customer — or an internal comment with |
Inboxes, channels & actors
Tool | Description |
| Conversation inboxes / help desks |
| Channel types (email, chat, …) |
| Connected accounts (specific email addresses / numbers) |
| Resolve actor IDs ( |
Custom channels (offered only when the token carries the conversations.custom_channels.* scopes)
Tool | Description |
| Create an account on a custom channel |
| List accounts on a custom channel |
| Get one custom-channel account |
| Rename or (de)authorize a channel account |
| Finalize a staging-token connection (public apps) |
| Publish an external message into HubSpot |
| Get a custom-channel message |
| Report delivery status: SENT / FAILED / READ |
Sending replies
SendConversationMessage only requires thread_id and text. Everything else is derived:
channel_id/channel_account_id— taken from the thread'soriginalChannelId/originalChannelAccountIdrecipients— the senders of the latest incoming message (i.e. a normal reply)sender_actor_id— falls back toHUBSPOT_DEFAULT_SENDER_ACTOR_ID
Pass any of them explicitly to override. The full request body can also be supplied as a stringified JSON request_body (typed fields win on conflict), and calling with mode="get_request_schema" returns the raw body schema. The same pattern applies to PublishCustomChannelMessage.
Development
npm test # vitest — unit + in-memory MCP integration tests
npm run typecheck # tsc --noEmit (CLI + broker functions)
npm run build # compile to dist/
npm run bundle # build a .mcpb one-click bundle for Claude DesktopThe integration tests run the full MCP server against a stubbed fetch, so no HubSpot account is needed to develop.
Notes
The client retries once on
429/502/503(honoringRetry-After, capped at 10s) and once more with a refreshed token on401.Thread assignee endpoints (
PUT/DELETE /threads/{id}/assignee) exist in the HubSpot API but are not currently exposed as tools. Add them insrc/tools/threads.tsif needed.
Available Tools
24 toolsArchiveConversationThreadArchive a conversation threadADestructive
Archives a conversation thread, marking it for deletion. The thread is permanently deleted after 30 days.
Inputs: thread_identifier (required).
CreateChannelAccountCreate a channel account (custom channel)A
Create a new account within a specific custom communication channel. Enables multiple accounts to communicate over a single channel with different delivery identifiers. Requires the conversations.custom_channels.write scope.
Inputs: inbox_id (required), channel_id (required), account_name (required), is_authorized (required), +2 more.
GetChannelAccountDetailsGet channel account detailsBRead-only
Fetch detailed information about a specific HubSpot channel account using the channel account ID, such as its status and configuration.
Inputs: channel_account_id (required).
GetCustomChannelAccountsGet custom channel accountsARead-only
Fetch the list of accounts associated with a specific custom channel, identified by the channel ID.
Inputs: custom_channel_id (required), after, limit.
GetCustomChannelMessageDetailsGet custom channel message detailsARead-only
Get the details of a specific message sent through a custom channel — message content, sender information, and timestamps.
Inputs: channel_id (required), message_id (required).
GetInboxDetailsGet inbox detailsARead-only
Retrieve detailed information about a specific conversation inbox by its ID.
Inputs: inbox_id (required).
GetMessageHistoryForThreadGet message history for a threadARead-only
Retrieve the message history for a given conversation thread by its ID (messages, comments and system events like assignments and status changes). Paginated: pass after from paging.next.after to fetch the next page.
Inputs: thread_id (required), after, limit, is_archived.
ListConversationChannelsList conversation channelsBRead-only
Retrieve a list of conversation channels (e.g. email, live chat, forms, WhatsApp), with optional filters and sorting if needed.
Inputs: sort, after, limit.
ListConversationInboxesList conversation inboxesARead-only
Fetch a list of conversation inboxes (shared inboxes and help desks), with optional filters and sorting to customize the results.
Inputs: sort, after, limit, is_archived.
PublishCustomChannelMessagePublish a message to a custom channelA
Publish a message over a specified custom channel into HubSpot Conversations — used by custom-integrated messaging channels to sync external messages into HubSpot. Provide the message either as typed fields or as a stringified JSON request_body (typed fields win on conflict). Requires channelAccountId, senders and recipients. Call with mode='get_request_schema' to inspect the raw request body schema.
Inputs: custom_channel_id (required), mode, text, senders, +10 more.
ResolveConversationActorsResolve conversation actorsARead-only
Resolve a list of ActorIds to detailed participant information in one batch call — use this to understand who the participants in a conversation are.
Inputs: actor_ids (required).
RetrieveActorDetailsRetrieve actor detailsARead-only
Retrieve details of a specific actor (conversation participant) by actor ID. Actor IDs are prefixed by type: 'A-' agent/user, 'V-' visitor/contact, 'B-' bot, 'E-' email, 'S-' system, 'I-' integrator.
Inputs: actor_id (required).
RetrieveChannelAccountDetailsRetrieve custom channel account detailsARead-only
Retrieve detailed metadata about a channel account on a custom channel, including its channel, inbox ID, and delivery identifiers.
Inputs: channel_account_id (required), channel_identifier (required).
RetrieveChannelAccountsRetrieve channel accountsARead-only
Retrieve a list of channel accounts — concrete instances of a channel connected to an inbox (e.g. a specific email address or phone number). Supports optional filters and sorting to refine the results.
Inputs: sort, after, limit, inbox_id, +2 more.
RetrieveChannelDetailsRetrieve channel detailsARead-only
Retrieve comprehensive details about a specific channel in HubSpot Conversations by providing the channel ID.
Inputs: channel_id (required).
RetrieveConversationThreadsRetrieve conversation threadsARead-only
Retrieve conversation threads from HubSpot Conversations. You can apply optional filters (inbox, OPEN/CLOSED status, associated contact or ticket, time window) and sorting to tailor the results. Paginated: pass after from the previous response's paging.next.after.
Inputs: sort, after, limit, inbox_id, +7 more.
RetrieveFullMessageContentRetrieve full original message contentARead-only
Retrieve the original text and rich text of a message — useful for untruncated content when the message's truncationStatus indicates it might be truncated.
Inputs: message_id (required), conversation_thread_id (required).
RetrieveThreadByIdRetrieve a thread by IDARead-only
Retrieve detailed information about a conversation thread by ID: status, inbox, original channel, assignee and associated contact.
Inputs: conversation_thread_id (required), is_archived, include_ticket_association.
RetrieveThreadMessageRetrieve a single thread messageARead-only
Retrieve the details of a specific message within a conversation thread using the message ID.
Inputs: thread_id (required), message_id (required).
SendConversationMessageSend a message in a conversation threadA
Send a new message on an existing conversation thread — delivered to the customer on the thread's channel (set message_type=COMMENT for an internal note instead). Provide the content either as typed fields (text, recipients, …) or as a stringified JSON request_body; typed fields win on conflict. Missing channel_id/channel_account_id are taken from the thread, missing recipients are derived from the latest incoming message, and sender_actor_id falls back to HUBSPOT_DEFAULT_SENDER_ACTOR_ID. Call with mode='get_request_schema' to inspect the raw request body schema.
Inputs: thread_id (required), mode, text, subject, +8 more.
UpdateChannelAccountInfoUpdate channel account infoA
Update the name and/or authorization status of a channel account on a custom channel — including disabling the account by setting set_authorization_status to false.
Inputs: channel_id (required), channel_account_id (required), channel_account_name, set_authorization_status.
UpdateChannelAccountStagingUpdate channel account staging tokenA
Update the account name and delivery identifier of a channel account staging token (public app connection flow) in HubSpot Conversations.
Inputs: channel_id (required), account_name (required), account_token (required), delivery_identifier_type (required), +1 more.
UpdateConversationThreadUpdate or restore a conversation threadA
Update a single thread's status (OPEN/CLOSED) or archive/restore it. Set is_thread_archived=true to archive, false to restore an archived thread.
Inputs: thread_identifier (required), thread_status, is_thread_archived.
UpdateMessageStatusUpdate custom channel message statusB
Update the delivery status of a message within a custom channel: SENT, FAILED, or READ. For FAILED messages, include an error message for clarification.
Inputs: message_id (required), message_status (required), channel_identifier (required), error_message_for_failed_status.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 24 tools
Several tools have overlapping purposes, such as GetChannelAccountDetails vs RetrieveChannelAccountDetails and UpdateConversationThread vs ArchiveConversationThread, which both handle archiving. The distinction between general and custom channel tools is not immediately clear, making misselection likely.
Tool names mix Get, Retrieve, List, Update, Create, Send, Publish, and Archive without a consistent pattern. For example, 'GetChannelAccountDetails' and 'RetrieveChannelAccountDetails' are nearly identical in structure but use different verbs. The naming lacks a predictable verb_noun convention.
With 24 tools, the server is on the heavy side, though the HubSpot Conversations domain is broad enough to warrant many operations. However, several tools (like the multiple channel account retrieval variants) could be consolidated, making the count feel inflated.
The tool set covers the essential conversation lifecycle: listing and retrieving threads, sending and viewing messages, managing inboxes/channels/accounts, and archiving. Minor gaps exist, such as no way to create a thread or update an assignment, but these are not critical for typical workflows.
Maintenance
Related MCP Connectors
The HubSpot MCP Server acts as a bridge that enables AI assistants and Large Language Models to securely interact with HubSpot CRM data through natural conversation, without requiring users to understand complex API structures. It provides read-only access to standard CRM objects (contacts, companies, deals, tickets, products, invoices, and more) and their associations, secured via OAuth 2.0, allowing AI agents to perform tasks like summarizing deals, fetching company updates, and looking up record changes.
MCP server for the HubSpot Integrations Center HubDB: search and retrieve integration data.
HubSpot MCP server: 9 tools, every client portal on one connector. Writes preview first.
Connect Chatway, an AI-powered website live chat and customer support platform, to ChatGPT, Claude, Gemini, Cursor, and other AI assistants using MCP. Chatway helps businesses communicate with website visitors, manage customer conversations, and deliver faster support across multiple channels, including website live chat, email, WhatsApp, Instagram, and Facebook Messenger. Native mobile apps for iOS and Android let support teams manage conversations and respond to customers on the go. With Chatway's MCP server, AI agents can access and manage customer support operations. Search and read conversations, send replies, add private notes, resolve and assign chats, manage contacts, retrieve customer information, and search knowledge base articles. Chatway also includes a built-in AI Support Agent for automated customer service, a shared team inbox, support ticket management, a customizable website chat widget, a help center, team management, automated workflows, visitor tracking, and integrations with popular platforms, including WordPress and Shopify. Connect external AI agents to automate customer support, answer customer questions, access conversation history, and streamline support workflows without building custom integrations. Manage your customer support from anywhere using Chatway's web dashboard or mobile apps. The hosted MCP server supports Streamable HTTP and secure OAuth 2.1 authentication with scoped permissions. Available on all Chatway plans, including the Free plan. Conversation limits apply. Website: https://chatway.app Documentation: https://developers.chatway.app/mcp/guides.mcp_overview
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceThis MCP Server enables users to interact with HubSpot's marketing events API, allowing management of marketing event data through natural language commands.1-
- AlicenseAqualityDmaintenanceA read-only MCP server that exposes HubSpot CRM data (contacts, deals, companies, quotes) to AI agents, enabling natural language queries.9MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the HubSpot CRM API with tools for managing contacts, companies, deals, tickets, and CRM workflows. Generated with MCPForge. Sensitive operations can be protected with permissions, audit logs, and approval workflows.21 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with full access to HubSpot CRM. Manage contacts, companies, deals, pipelines, and associations directly from Claude, Cursor, or any MCP-compatible client.8 npmMIT