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 Service Hub MCP Server for CrewAI 6 tools — connect in under 2 minutes

Name: HubSpot Service Hub
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 6 Tools Framework

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

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="HubSpot Service Hub Specialist",
    goal="Help users interact with HubSpot Service Hub effectively",
    backstory=(
        "You are an expert at leveraging HubSpot Service 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 Service Hub "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 6 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 Service 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 Service Hub becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HubSpot Service Hub tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the 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 Service Hub MCP Server exposes 6 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 Service Hub to CrewAI via MCP

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

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py — CrewAI auto-discovers 6 tools from HubSpot Service Hub

Why Use CrewAI with the HubSpot Service Hub MCP Server

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

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

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

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

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 Service Hub + CrewAI Use Cases

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

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

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

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

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

HubSpot Service Hub MCP Tools for CrewAI (6)

These 6 tools become available when you connect HubSpot Service Hub to CrewAI via MCP:

hs_create_ticket

Subject is required. Optionally provide content (detailed description), hs_pipeline (pipeline ID), hs_pipeline_stage (stage ID), and hs_ticket_priority (HIGH, MEDIUM, LOW). If no pipeline is specified, uses the default support pipeline. Returns the created ticket with its HubSpot ID. Create a new support ticket in HubSpot Service Hub with subject, description, pipeline stage, and priority

hs_list_feedback

Returns survey name, customer rating/score, survey type (NPS/CSAT/CES), and response content. Use when the user asks about customer satisfaction, NPS scores, or wants to review recent feedback from support interactions. List customer feedback survey submissions in HubSpot with ratings, survey type, and response content

hs_search_tickets

Returns ticket subject, current pipeline stage/status, priority (HIGH/MEDIUM/LOW), pipeline name, category, and creation date. Use when the user asks about open tickets, needs to find a specific support case, or wants to check the status of a customer issue. Search HubSpot Service Hub tickets by subject or keyword to find customer support cases

hs_ticket_pipelines

Returns pipeline name, stage labels, stage IDs (needed for creating/filtering tickets), and display order. Support pipelines define the workflow tickets follow: typically New → Waiting on Contact → Waiting on Us → Closed. Essential for finding stage IDs before ticket operations. List all ticket/support pipelines in HubSpot with their stages, display order, and internal IDs

hs_tickets_by_status

Returns tickets with subject, priority, and dates. Use when the user asks "how many tickets are open?", "what is waiting for response?", or for support queue analysis. Find stage IDs using hs_ticket_pipelines first. Get all HubSpot tickets at a specific pipeline stage to analyze queue depth, workload, or resolution bottlenecks

hs_update_ticket

Only specified fields are updated. Common use: advance hs_pipeline_stage when a case progresses, escalate hs_ticket_priority, or update the subject for clarity. Use when the user says a ticket moved stages, priority changed, or needs correction. Update an existing HubSpot ticket — change status, priority, subject, or reassign to reflect case progress

Example Prompts for HubSpot Service Hub in CrewAI

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

"Search for contacts at Acme Corp"

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

"Show me the deal pipeline stages"

Troubleshooting HubSpot Service Hub MCP Server with CrewAI

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

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

Rate limiting or 429 errors

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

HubSpot Service Hub + CrewAI FAQ

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

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.

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.

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.

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.

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.