2,500+ MCP servers ready to use
Vinkius

HubSpot CRM (Full) MCP Server for CrewAI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to HubSpot CRM (Full) through the Vinkius — pass the Edge URL in the `mcps` parameter and every HubSpot CRM (Full) 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 CRM (Full) Specialist",
    goal="Help users interact with HubSpot CRM (Full) effectively",
    backstory=(
        "You are an expert at leveraging HubSpot CRM (Full) 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 CRM (Full) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

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

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

When paired with CrewAI, HubSpot CRM (Full) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HubSpot CRM (Full) 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 CRM (Full) MCP Server exposes 10 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 CRM (Full) to CrewAI via MCP

Follow these steps to integrate the HubSpot CRM (Full) 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 10 tools from HubSpot CRM (Full)

Why Use CrewAI with the HubSpot CRM (Full) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with HubSpot CRM (Full) 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 the 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 CRM (Full) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the HubSpot CRM (Full) MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries HubSpot CRM (Full) 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 CRM (Full), analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain HubSpot CRM (Full) 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 CRM (Full) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

HubSpot CRM (Full) MCP Tools for CrewAI (10)

These 10 tools become available when you connect HubSpot CRM (Full) to CrewAI via MCP:

01

hs_create_contact

Email is the primary identifier — provide a unique email address. HubSpot will auto-deduplicate by email. The lifecycle stage can be set to control where the contact enters the funnel (subscriber, lead, marketingqualifiedlead, salesqualifiedlead, opportunity, customer, evangelist). Returns the created contact with its new HubSpot ID. Create a new contact in HubSpot CRM with email, name, phone, and company association

02

hs_create_deal

The dealname is required. Optionally specify pipeline (by ID — use hs_list_pipelines to find), dealstage (stage ID within that pipeline), and amount. If no pipeline is specified, the deal goes into the default pipeline. Returns the created deal with its new HubSpot ID. Create a new deal/opportunity in the HubSpot sales pipeline with name, stage, amount, and close date

03

hs_create_note

The note body supports HTML formatting. Optionally associate it with a contact, company, or deal by providing their IDs. Notes appear in the timeline of associated records. Use when the user wants to log a meeting summary, record a conversation, or add internal context to a CRM record. Create an engagement note in HubSpot attached to a contact, company, or deal for activity logging

04

hs_create_ticket

The subject is required. Optionally set the pipeline stage (hs_pipeline_stage) and priority (hs_ticket_priority: HIGH, MEDIUM, LOW). The ticket enters the default support pipeline. Returns the created ticket with its new ID. Create a new support ticket in HubSpot Service Hub with subject, pipeline stage, and priority

05

hs_list_owners

Owners are the users who can be assigned to contacts, companies, deals, and tickets. Returns owner name, email, and whether the account is active. Use when the user asks about team members, needs owner IDs for record assignment, or wants to see who has CRM access. List all HubSpot owners (CRM users) in the account with their name, email, and active status

06

hs_list_pipelines

For deals, shows sales pipeline stages (e.g., Appointment Scheduled → Qualified → Proposal → Closed Won). For tickets, shows support pipeline stages (e.g., New → Waiting → Closed). Returns pipeline name, stage labels, stage IDs, and display order. Use when the user needs pipeline/stage IDs for creating deals or tickets, or wants to understand the sales/support process structure. List all deal or ticket pipelines in HubSpot with their stages, display order, and stage IDs

07

hs_search_companies

Returns matching companies with name, website domain, industry, annual revenue, employee count, and assigned owner. Use when the user wants to find a specific company, look up organizational details, check revenue/size data, or find companies in a particular industry. Search HubSpot companies by name, domain, or industry to find organizations in your CRM

08

hs_search_contacts

Returns matching contacts with first name, last name, email, phone, associated company, lifecycle stage (subscriber/lead/MQL/SQL/opportunity/customer/evangelist), and assigned owner. Use when the user wants to find a specific person, look up contact details, check which lifecycle stage someone is in, or find contacts at a particular company. Search HubSpot contacts by name, email, phone, or company name to find people in your CRM

09

hs_search_deals

Returns matching deals with 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, check deal amounts, or review upcoming closes. Search HubSpot deals by name to find opportunities in your sales pipeline with stage, amount, and close date

10

hs_search_tickets

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

Example Prompts for HubSpot CRM (Full) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with HubSpot CRM (Full) 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 CRM (Full) MCP Server with CrewAI

Common issues when connecting HubSpot CRM (Full) 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

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

HubSpot CRM (Full) + CrewAI FAQ

Common questions about integrating HubSpot CRM (Full) 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 CRM (Full) to CrewAI

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