HubSpot CRM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUBSPOT_ACCESS_TOKEN | Yes | HubSpot private app access token with scopes for contacts, deals, and tickets read/write. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_contactsA | Search HubSpot contacts by name, email, or company. Returns up to |
| get_contactA | Fetch a single HubSpot contact by ID, including their core properties. Pair with get_account_summary for a fuller picture (deals + tickets included). |
| create_contactB | Create a new HubSpot contact. Email is required by HubSpot for deduplication; other fields are optional but recommended for a usable CRM record. |
| search_dealsB | Search HubSpot deals by name, optionally filtered to a specific pipeline stage. Useful for questions like 'what deals are in the proposal stage'. |
| get_dealA | Fetch a single HubSpot deal by ID, including stage, amount, close date, and the contacts associated with it. |
| create_dealC | Create a new HubSpot deal, optionally associated with an existing contact. Amount is in the portal's default currency. |
| update_deal_stageA | Move a deal to a new pipeline stage — the most common day-to-day CRM write action (e.g. advancing a deal from 'proposal' to 'closed won'). |
| search_ticketsA | Search HubSpot support tickets by subject text, optionally filtered by priority. Useful for 'what high-priority tickets are open' style questions. |
| create_ticketB | Create a new HubSpot support ticket, optionally associated with an existing contact. |
| get_account_summaryA | Build a single account brief for a contact: their profile, every deal associated with them (with stage and amount), and every support ticket associated with them (with priority). Use this instead of chaining get_contact + search_deals + search_tickets when you want the full picture in one call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool maps to a distinct resource/action: search vs get vs create for contacts/deals/tickets, plus a dedicated deal stage updater and an account summary aggregator. Even get_contact and get_account_summary are clearly differentiated by the summary's broader scope.
All tool names follow a consistent verb_noun snake_case pattern: search_*, get_*, create_*, plus update_deal_stage and get_account_summary. No mixed conventions or vague verbs.
10 tools is well-scoped for a HubSpot CRM server covering contacts, deals, and tickets. Each tool covers a meaningful operation without redundancy.
The surface covers search/get/create for contacts and deals, search/create for tickets, and deal stage updates, but lacks update/delete operations for contacts and tickets and a get_ticket by ID. These are notable gaps for a CRM lifecycle, though common workflows are still possible.