hubspot-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (default 3000, Render sets automatically) | 3000 |
| TRANSPORT | No | Transport mode: 'stdio' (default) or 'http' | stdio |
| MCP_API_KEY | No | Bearer token for authentication in HTTP mode (required for HTTP transport) | |
| HUBSPOT_ACCESS_TOKEN | Yes | HubSpot private app token (required) |
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 |
|---|---|
| hubspot_get_contactA | Retrieve a single HubSpot contact by their record ID. Returns standard contact fields (name, email, phone, company, job title, lifecycle stage). Args:
Returns: Contact object with id, firstName, lastName, email, phone, company, jobTitle, lifecycleStage Errors:
|
| hubspot_list_contactsA | List contacts from HubSpot CRM with pagination. Args:
Returns: { contacts: ContactOutput[], hasMore: boolean, nextCursor?: string, total: number } |
| hubspot_create_contactA | Create a new contact record in HubSpot CRM. Args:
Returns: Created contact with its new record ID Errors:
|
| hubspot_update_contactA | Update properties on an existing HubSpot contact. Only provided fields are changed. Args:
Returns: Updated contact record |
| hubspot_delete_contactA | Archive (soft-delete) a contact in HubSpot. The record moves to the recycle bin and can be restored within HubSpot. Args:
Returns: Confirmation message with deleted ID |
| hubspot_get_companyA | Retrieve a single HubSpot company record by ID. Args:
Returns: Company with id, name, domain, industry, city, state, country, phone, employees, annualRevenue, lifecycleStage |
| hubspot_list_companiesA | List company records from HubSpot CRM with pagination. Args:
Returns: { companies: CompanyOutput[], hasMore: boolean, nextCursor?: string } |
| hubspot_create_companyA | Create a new company record in HubSpot CRM. Args:
Returns: Created company with its new record ID |
| hubspot_update_companyA | Update properties on an existing HubSpot company. Only provided fields are changed. Args:
Returns: Updated company record |
| hubspot_delete_companyA | Archive (soft-delete) a company in HubSpot. Record moves to the recycle bin. Args:
Returns: Confirmation message |
| hubspot_get_dealA | Retrieve a single HubSpot deal record by ID. Args:
Returns: Deal with id, dealName, amount, dealStage, pipeline, closeDate, dealType, description, ownerId |
| hubspot_list_dealsA | List deals from HubSpot CRM with pagination. Args:
Returns: { deals: DealOutput[], hasMore: boolean, nextCursor?: string } |
| hubspot_create_dealA | Create a new deal in HubSpot CRM. Args:
Returns: Created deal with new record ID |
| hubspot_update_dealA | Update properties on an existing HubSpot deal. Only provided fields are changed. Common use cases:
Args:
Returns: Updated deal record |
| hubspot_delete_dealA | Archive (soft-delete) a deal in HubSpot. Record moves to the recycle bin and can be restored. Args:
Returns: Confirmation message |
| hubspot_searchA | Search contacts, companies, or deals using full-text query and/or property filters. Args:
Returns: { total: number, results: HubSpotRecord[], hasMore: boolean, nextCursor?: string } Examples:
|
| hubspot_associate_recordsA | Create an association between two HubSpot CRM records (e.g. link a contact to a company, or a deal to a contact). Args:
Supported pairs and their defaults:
Returns: Confirmation of the association created |
| hubspot_list_associationsA | List all records of a given type associated with a source CRM record. Args:
Example: List all companies associated with contact 12345 fromObjectType="contacts", fromObjectId="12345", toObjectType="companies" Returns: { associations: [{ id: string, type: string }], total: number } |
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 18 tools
Each tool targets a distinct combination of CRM object (contact, company, deal) and action (create, get, update, delete, list), with separate tools for search and associations. There is no functional overlap, and an agent can clearly differentiate them.
All tools follow the consistent pattern 'hubspot_<verb>_<object>' (e.g., hubspot_create_contact, hubspot_delete_company), with the exception of 'hubspot_search' and 'hubspot_list_associations' which still align with verb_object structure. Naming is uniform and predictable.
With 18 tools covering CRUD for three objects (12 tools), list operations (3), search (1), and associations (2), the count is well-scoped for a CRM server. Each tool serves a distinct purpose without redundancy.
The tool set fully covers CRUD for contacts, companies, and deals, plus searching and listing. Associations are partially covered (create and list, but no dedicated delete association tool). This minor gap is the only missing piece, making the surface nearly complete.