2,500+ MCP servers ready to use
Vinkius

HubSpot Sales Hub MCP Server for Cursor 9 tools — connect in under 2 minutes

Built by Vinkius GDPR 9 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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 Sales Hub and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "hubspot-sales-hub": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
HubSpot Sales Hub
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 Sales Hub MCP Server

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

Cursor's Agent mode turns HubSpot Sales Hub into an in-editor superpower. Ask Cursor to generate code using live data from HubSpot Sales Hub and it fetches, processes, and writes. all in a single agentic loop. 9 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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 Sales Hub MCP Server exposes 9 tools through the Vinkius. Connect it to Cursor 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 Sales Hub to Cursor via MCP

Follow these steps to integrate the HubSpot Sales Hub MCP Server with Cursor.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using HubSpot Sales Hub

Open Agent mode in chat and ask: "Using HubSpot Sales Hub, help me...". 9 tools available

Why Use Cursor with the HubSpot Sales Hub MCP Server

Cursor AI Code Editor provides unique advantages when paired with HubSpot Sales Hub through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

HubSpot Sales Hub + Cursor Use Cases

Practical scenarios where Cursor combined with the HubSpot Sales Hub MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

HubSpot Sales Hub MCP Tools for Cursor (9)

These 9 tools become available when you connect HubSpot Sales Hub to Cursor via MCP:

01

hs_create_deal

dealname is required. Specify pipeline and dealstage by their IDs (use hs_list_pipelines to find). Amount is a string representing monetary value. closedate is ISO format. If no pipeline is specified, the deal goes to the default pipeline at its first stage. Create a new deal/opportunity in the HubSpot sales pipeline with name, stage, amount, and expected close date

02

hs_create_product

Products serve as catalog items that sales reps can attach to deals as line items or include in quotes. Name is required. Price is the default unit price. SKU (hs_sku) is the internal product identifier. Returns the created product with its HubSpot ID. Create a new product in the HubSpot product library with name, price, SKU, and description for quoting

03

hs_deals_by_stage

Returns deals with name, amount, close date, and owner. Use when the user asks "what deals are in Proposal stage?" or "how much revenue is in the Negotiation stage?" or for pipeline stage analysis. Get all deals at a specific pipeline stage to analyze bottlenecks, forecast revenue, or review stage-specific activity

04

hs_list_meetings

Returns meeting title, start and end timestamps, outcome/disposition, and associated contacts. Meetings are logged interactions — either via calendar sync or manual entry. Use when the user asks about recent meetings, scheduled calls, or meeting history with a prospect. List recent meetings logged in HubSpot with title, participants, start/end times, and meeting outcome

05

hs_list_pipelines

For deals: sales pipeline stages like Appointment Scheduled → Qualified → Proposal → Closed Won. For tickets: support stages like New → Waiting → Closed. Returns pipeline name, stage labels, stage internal IDs (needed for creating/updating deals), and display order. Essential for finding stage IDs before deal operations. List all deal or ticket pipelines in HubSpot with their stages, display order, and IDs

06

hs_list_quotes

Returns quote title, approval status (draft/pending/approved/rejected), total amount, expiration date, and associated deal. Quotes are formal price proposals sent to prospects. Use when the user asks about pending quotes, proposal status, or approved pricing documents. List sales quotes in HubSpot with title, status, total amount, and expiration date

07

hs_search_deals

Returns deal name, pipeline stage, monetary amount, pipeline name, expected close date, and assigned owner. Use when the user asks about pipeline status, wants to find a specific deal, needs to check deal amounts, or wants to review upcoming closes. Search HubSpot deals by name to find opportunities in the sales pipeline with stage, amount, and close date

08

hs_search_products

Returns product name, unit price, SKU, and description. Products are the catalog items that can be added to deals via line items or included in quotes. Use when the user asks about available products, needs to check pricing, or wants to find a product ID for deal line items. Search HubSpot product library by name to find items available for quoting with prices and SKUs

09

hs_update_deal

Only specified fields are updated. Common use: advance dealstage when a deal progresses in the pipeline, update amount after negotiation, push closedate when timeline shifts. Use when the user says a deal moved stages, the amount changed, or a close date was updated. Update an existing HubSpot deal — change stage, amount, close date, or name to reflect pipeline progress

Example Prompts for HubSpot Sales Hub in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with HubSpot Sales Hub immediately.

01

"Search for contacts at Acme Corp"

02

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

03

"Show me the deal pipeline stages"

Troubleshooting HubSpot Sales Hub MCP Server with Cursor

Common issues when connecting HubSpot Sales Hub to Cursor through the Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

HubSpot Sales Hub + Cursor FAQ

Common questions about integrating HubSpot Sales Hub MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Connect HubSpot Sales Hub to Cursor

Get your token, paste the configuration, and start using 9 tools in under 2 minutes. No API key management needed.