What HubSpot data can I access?

Contacts, Companies, Deals, Tickets, Notes, Owners, and Pipelines. All data respects your HubSpot permissions.

Can I create and update records?

Yes! Create contacts, deals, tickets, and notes. All through natural conversation.

How does authentication work?

Uses a HubSpot Private App token (Bearer). Create a Private App in Settings > Integrations > Private Apps, copy the token, and paste it.

HubSpot Operations Hub MCP Server for Claude Desktop 6 tools — connect in under 2 minutes

Name: HubSpot Operations Hub
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 6 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install HubSpot Operations Hub and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "hubspot-operations-hub": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About HubSpot Operations Hub MCP Server

Connect HubSpot CRM to any AI agent — instant access to your full CRM data without switching tabs.

Claude Desktop is the definitive way to connect HubSpot Operations Hub to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 6 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Contacts — Search, create, and manage contacts
Companies — Find companies by name or domain
Deals — Search and create deals with pipeline tracking
Tickets — Create and search support tickets
Notes — Create notes attached to any CRM record
Owners — View all owners and team assignments
Pipelines — List deal and ticket pipeline stages

The HubSpot Operations Hub MCP Server exposes 6 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect HubSpot Operations Hub to Claude Desktop via MCP

Follow these steps to integrate the HubSpot Operations Hub MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using HubSpot Operations Hub

Look for the 🔌 icon in the chat — your 6 tools are now available

Why Use Claude Desktop with the HubSpot Operations Hub MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with HubSpot Operations Hub through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

HubSpot Operations Hub + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the HubSpot Operations Hub MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

HubSpot Operations Hub MCP Tools for Claude Desktop (6)

These 6 tools become available when you connect HubSpot Operations Hub to Claude Desktop via MCP:

hs_create_property

Create a custom property (field) on a HubSpot CRM object to extend the data model with business-specific fields

hs_list_all_pipelines

Returns pipeline name, stage labels, internal stage IDs, and display order. Pipelines define the process stages for deals (sales process) or tickets (support process). Use when configuring automations, setting up deal/ticket routing, or when the user needs pipeline/stage IDs for creating records. List all deal or ticket pipelines with their stages, IDs, and display order for workflow configuration

hs_list_owners

Owners are the users who can be assigned to contacts, companies, deals, and tickets. Returns owner ID, name, email, active status, and team memberships. Use when configuring round-robin assignment rules, auditing user access, or when the user needs owner IDs for record assignment. List all HubSpot owners (CRM users) for use in assignment workflows, with name, email, and active status

hs_list_properties

Returns property internal name, display label, data type (string/number/date/enumeration), field type (text/number/date/select/checkbox), group name, and description. Essential for understanding the CRM data model. Use when the user asks "what fields exist on contacts?", wants to audit custom properties, or needs internal property names for filters/searches. List all properties (fields) configured on a HubSpot CRM object type — contacts, companies, deals, or tickets

hs_list_property_groups

Returns group internal name and display label. Property groups organize fields into logical sections in the HubSpot UI (e.g., "Contact Information", "Social Media", "Custom Fields"). Use to find valid group names before creating custom properties with hs_create_property. List property groups for a HubSpot CRM object — the logical sections that organize properties in the UI

hs_list_workflows

Returns workflow name, type (drip/standard/nurturing), enabled status (active vs inactive), and number of actions in the workflow. Workflows automate marketing, sales, and service processes — e.g., lead nurturing emails, deal stage automation, ticket routing. Use when the user asks about active automations, wants to audit workflows, or needs to check which automations are running. List all automation workflows in HubSpot with name, type, active/inactive status, and action count

Example Prompts for HubSpot Operations Hub in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with HubSpot Operations Hub immediately.

"Search for contacts at Acme Corp"

"Create a deal: Enterprise Package $50,000"

"Show me the deal pipeline stages"

Troubleshooting HubSpot Operations Hub MCP Server with Claude Desktop

Common issues when connecting HubSpot Operations Hub to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

HubSpot Operations Hub + Claude Desktop FAQ

Common questions about integrating HubSpot Operations Hub MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.