2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to HubSpot Sales Hub through Vinkius, pass the Edge URL in the `mcps` parameter and every HubSpot Sales Hub tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="HubSpot Sales Hub Specialist",
    goal="Help users interact with HubSpot Sales Hub effectively",
    backstory=(
        "You are an expert at leveraging HubSpot Sales Hub tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in HubSpot Sales Hub "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
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.

When paired with CrewAI, HubSpot Sales Hub becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HubSpot Sales Hub tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Customize the agent

Adjust the role, goal, and backstory to fit your use case

04

Run the crew

Run python crew.py. CrewAI auto-discovers 9 tools from HubSpot Sales Hub

Why Use CrewAI with the HubSpot Sales Hub MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with HubSpot Sales Hub through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

HubSpot Sales Hub + CrewAI Use Cases

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

01

Automated multi-step research: a reconnaissance agent queries HubSpot Sales Hub for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries HubSpot Sales Hub, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain HubSpot Sales Hub tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries HubSpot Sales Hub against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

HubSpot Sales Hub MCP Tools for CrewAI (9)

These 9 tools become available when you connect HubSpot Sales Hub to CrewAI 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 CrewAI

Ready-to-use prompts you can give your CrewAI 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 CrewAI

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

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

HubSpot Sales Hub + CrewAI FAQ

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

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Connect HubSpot Sales Hub to CrewAI

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