HubSpot MCP: CRM answers and changes that need human review

HubSpot’s remote MCP server connects compatible AI agents to CRM records so they can answer sales and support questions and, with permission, create or update data. Claude users can use HubSpot’s connector; builders can connect their own MCP client through OAuth. Keep record changes behind human approval, especially deal stages, contact details, and customer notes. HubSpot’s MCP use cases

Documentation reviewed as of 30 Oct 2026. Browse related integrations in MCP servers for apps, or start with what MCP does.

What it can do

HubSpot documents access to contacts, companies, deals, tickets, and activity history, including notes and tasks. Available actions depend on the connection’s access. This supports a useful distinction: retrieving CRM context, drafting a recommendation, and committing a change are separate decisions. See the official MCP overview.

For an initial pilot, use prompts with a defined account, owner, and period:

• Pipeline review: summarize the open deals I can access, grouped by stage. Include record IDs, amounts, closing dates, and missing information. Treat a missing next step as a question for the owner, rather than evidence that a deal is lost.
• Account preparation: assemble a brief for a named company from accessible records and recent activity. Separate recorded facts from suggested talking points, and identify the records behind each assertion.
• Support handoff: summarize open tickets assigned to me, then draft a handoff note. Ask for unresolved questions and supporting record references; leave the draft outside the CRM until reviewed.

These are suggested workflows, not promises of complete answers. HubSpot’s Claude connector guide documents sales and support queries. Ask the agent to state the filters it used so a reviewer can reproduce the selection.

Which changes need a reviewer

Use a change proposal that a record owner can assess without rereading the entire conversation:

This table is a recommended operating policy. A confident summary is not authorization to change the underlying record. Ask for a proposal first, approve its exact contents, and read the record again afterward. If the current value has changed since the proposal was prepared, stop and revise it.

For bulk cleanup, review the selection criteria as carefully as the replacement values. A correct edit applied to the wrong customer is still a bad change. The MCP security checklist provides a broader access review.

Remote CRM server or local Developer MCP?

The remote server is the CRM connection. HubSpot’s separate Developer MCP server runs locally through its CLI for app and CMS development. Its documented setup uses hs mcp setup and supports editor clients including VS Code and Claude Code. Follow the Developer MCP setup guide for current prerequisites.

Choose according to the job: preparing a customer brief calls for CRM access; building a HubSpot extension calls for developer tooling. Installing the local developer server does not establish the remote CRM connection. The remote versus local MCP guide explains the hosting distinction.

How to connect it safely

1. Define a read task first. Choose the HubSpot account, an ordinary user with appropriate access, and a known record. Write down the permitted question and the fields needed to answer it. Avoid using an administrator account merely to bypass an access error.
2. For Claude, use the connector route. In Settings, open Connectors, browse for HubSpot, and connect the intended account. Follow the organization’s app approval process. The HubSpot setup guide lists account and paid Claude subscription requirements.
3. For a custom client, create the connector. In HubSpot, open Development → MCP Connectors → Create MCP connector. Follow the remote integration guide. Use the client’s required callback URL.
4. Configure the client and authentication. The remote endpoint is https://mcp.hubspot.com. In VS Code, use MCP: Add Server and choose HTTP; follow the selected client’s authentication flow. VS Code’s instructions describe the editor setup. HubSpot requires OAuth with PKCE; its official authentication example shows client credentials and matching callback URLs. Keep secrets out of chat and committed configuration.
5. Inspect the granted access. Run get_user_details to inspect the account and permissions, as shown in that authentication example. Connector scopes derive from available server tools and the permissions granted at installation; they are not manually defined when creating the connector. HubSpot’s permissions section explains this behavior.
6. Require approval for writes. In Claude’s HubSpot connector tool settings, set Write tools to Needs Approval, following HubSpot’s recommendation. In another editor client, inspect its approval controls and leave mutation tools disabled until a review path is established.
7. Verify the complete path. Retrieve the known record and compare the returned facts with HubSpot. Then rehearse a proposed edit without applying it. For an approved change, inspect the tool response and read back the record before reporting completion. See MCP in VS Code for editor workflow considerations.

When this does not work

Authentication breaks. Check PKCE support, the callback URL, and token renewal before changing CRM permissions. HubSpot’s authentication example covers these checks. Repeating the business prompt will not repair an invalid connection.

Expected data is unavailable. New scopes can require reinstalling the connector. Accounts with Sensitive Data enabled block activity and conversation access through the remote server. Check the current access documentation before treating an empty history as proof that nothing happened.

Search appears incomplete. HubSpot’s CRM search documentation says updates may take time to appear and archived records are excluded. Validate filters and inspect the record directly before proposing a duplicate. An empty result is evidence about that query, not the entire customer relationship.

A write returns an uncertain result. As an operating rule, inspect the target record before repeating the action. A timeout should not turn a reviewed note into duplicate notes. Preserve the proposal and record identifiers so the owner can reconcile what happened.

Where Tvijo fits

As of 30 Oct 2026, the DSHREM VS Code extension provides an editor entry for selected context and reviewable tasks. TvijoCode bundles the extension in a Code - OSS editor test build; the documented Windows build is unsigned and requires manual updates.

Tvijo MCP exposes Tvijo consultation to an MCP client. Supplied-diff review is prepared with publication pending in the dated release report; editor integration and safe delegation remain planned. These components do not establish a ready HubSpot connector. The technology map explains their separate roles.

A HubSpot workflow would need a separately scoped and tested connection: authorized CRM context for sales or support, a proposed result, and human review before updates. Start with a redacted brief and an explicit acceptance criterion.

On Tvijo’s offers page, as of 30 Oct 2026, Try is $0: up to 5 tasks, 50,000 tokens, or $0.05 of sponsored usage, whichever is reached first, from a shared $1 daily pool funded by TVIJO. Service credit is shown as $10 for requesting prepaid credit; provider usage is metered with an 8% service markup. Payment collection is not activated, and an order is not a charge. These are Tvijo offers, separate from HubSpot or client subscription requirements.

FAQ

Do I need the local server to use HubSpot in Claude?

Use the HubSpot connector for CRM work. The local Developer MCP server serves app and CMS development; choose it when that is the task. HubSpot distinguishes the routes.

Should an agent update a deal stage on its own?

Keep that decision with an authorized reviewer. Require the exact record, before-and-after values, and evidence supporting the proposed stage, then verify the saved result.

What should I ask before enabling writes?

Request a bounded, read-only brief about records you know. Check account identity, record references, filters, and missing data. Enable a reviewed change only after that evidence is dependable.

HubSpot is a trademark of its owner. Tvijo is not affiliated with or endorsed by it.