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

Name: HubSpot CMS Hub
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to HubSpot CMS Hub through Vinkius, pass the Edge URL in the `mcps` parameter and every HubSpot CMS 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 CMS Hub Specialist",
    goal="Help users interact with HubSpot CMS Hub effectively",
    backstory=(
        "You are an expert at leveraging HubSpot CMS 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 CMS 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)

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 CMS 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 CMS Hub becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HubSpot CMS 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 CMS 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 CMS Hub to CrewAI via MCP

Follow these steps to integrate the HubSpot CMS 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 9 tools from HubSpot CMS Hub

Why Use CrewAI with the HubSpot CMS Hub MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with HubSpot CMS 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 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 CMS Hub + CrewAI Use Cases

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

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

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

HubSpot CMS Hub MCP Tools for CrewAI (9)

These 9 tools become available when you connect HubSpot CMS Hub to CrewAI via MCP:

hs_get_blog_post

Returns full post details including title, meta description, slug, body content length, author, featured image, publish date, and SEO settings. Use after listing/searching posts to drill into a specific article for complete details. Get the complete details of a specific HubSpot blog post by ID, including body content length and SEO metadata

hs_list_blog_authors

Returns author display name, URL slug, email, and bio. Authors are linked to blog posts for byline attribution. Use when the user asks about content contributors, wants to find an author profile, or needs author IDs for blog post creation. List blog authors configured in HubSpot CMS with name, email, slug, and biography

hs_list_blog_posts

Returns post title, URL slug, current state (draft/published/scheduled), author name, and publish date. Use when the user asks about blog content, wants to review recent articles, check publishing status, or audit the content calendar. List recent blog posts from HubSpot CMS with title, URL slug, publish status, author, and publish date

hs_list_blog_tags

Returns tag name and slug used for content categorization and URL generation. Blog tags group related posts for navigation and topic clustering. Use when the user asks about content categories, available tags, or wants to audit the blog taxonomy. List blog tags used for categorizing HubSpot blog content with tag name and URL slug

hs_list_domains

Returns domain name, whether DNS is resolving correctly, if the domain is primary, and which HubSpot features use it (CMS, email, landing pages). Use when the user asks about connected domains, DNS configuration, or wants to verify domain setup. List all domains connected to HubSpot with DNS resolution status, primary domain flag, and usage type

hs_list_landing_pages

Landing pages are standalone conversion-focused pages (signup forms, lead magnets, event registration). Returns page title, slug, status, and full URL. Distinct from regular site pages — landing pages are typically ungated and optimized for form fills. Use when the user asks about conversion pages or lead capture pages. List HubSpot landing pages designed for conversion with title, URL, publish status, and campaign association

hs_list_site_pages

Returns page title, URL slug, current state (draft/published), and associated domain. Site pages are standard website pages (About, Contact, Pricing, etc.) — distinct from blog posts and landing pages. Use when the user asks about website content, page inventory, or publishing status. List website pages hosted in HubSpot CMS with title, URL slug, publish status, and domain

hs_search_blog_posts

Returns matching posts with title, slug, status, and date. Use when the user wants to find a specific article, check if a topic has been covered, or locate a post for updating. Search HubSpot blog posts by title or keyword to find specific articles in the content library

hs_search_site_pages

Returns matching pages with title, slug, status, and domain. Use when the user wants to find a specific website page or check if a topic has a dedicated page. Search HubSpot site pages by title or keyword to find specific web pages

Example Prompts for HubSpot CMS Hub in CrewAI

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

"Search for contacts at Acme Corp"

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

"Show me the deal pipeline stages"

Troubleshooting HubSpot CMS Hub MCP Server with CrewAI

Common issues when connecting HubSpot CMS 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

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

HubSpot CMS Hub + CrewAI FAQ

Common questions about integrating HubSpot CMS 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.