BackCrew HubSpot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_contacts | List a contact (person) record. At least one of email, firstname, or lastname is required on create. records, cursor-paginated. Maps to GET /crm/v3/objects/contacts. [tier: readonly-owner] |
| get_contactC | Get a single a contact (person) record. At least one of email, firstname, or lastname is required on create. by ID. Maps to GET /crm/v3/objects/contacts/{id}. [tier: readonly-owner] |
| list_companiesC | List a company record. At least one of name or domain is required on create — domain is recommended, since it's the primary de-duplication key. records, cursor-paginated. Maps to GET /crm/v3/objects/companies. [tier: readonly-owner] |
| get_companyC | Get a single a company record. At least one of name or domain is required on create — domain is recommended, since it's the primary de-duplication key. by ID. Maps to GET /crm/v3/objects/companies/{id}. [tier: readonly-owner] |
| list_dealsB | List a deal (sales opportunity) record. dealname and dealstage are required on create; pipeline defaults to your account's default pipeline if omitted. records, cursor-paginated. Maps to GET /crm/v3/objects/deals. [tier: readonly-owner] |
| get_dealB | Get a single a deal (sales opportunity) record. dealname and dealstage are required on create; pipeline defaults to your account's default pipeline if omitted. by ID. Maps to GET /crm/v3/objects/deals/{id}. [tier: readonly-owner] |
| list_pipelines | List the deal pipelines and their stages configured for this account — use this to find valid dealstage/pipeline IDs before creating or updating a deal. Maps to GET /crm/v3/pipelines/deals. [tier: readonly-owner] |
| list_notesA | List a note logged on a CRM record's timeline (e.g. a contact, company, or deal). hs_timestamp is required on create — pass associations to attach it to a record, otherwise it won't show up anywhere useful. records, cursor-paginated. Maps to GET /crm/v3/objects/notes. [tier: readonly-owner] |
| get_noteA | Get a single a note logged on a CRM record's timeline (e.g. a contact, company, or deal). hs_timestamp is required on create — pass associations to attach it to a record, otherwise it won't show up anywhere useful. by ID. Maps to GET /crm/v3/objects/notes/{id}. [tier: readonly-owner] |
| list_owners | List HubSpot users who can be assigned as an owner on records. Maps to GET /crm/v3/owners. [tier: readonly-owner] |
| list_associationsA | List the records of one object type associated with a specific record. Maps to GET /crm/v4/objects/{fromObjectType}/{fromObjectId}/associations/{toObjectType}. [tier: readonly-owner] |
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 8 tools
Each tool targets a distinct resource or action: contacts, companies, deals, notes, and associations, with clear 'list' vs 'get' differentiation. No overlap in purpose.
All tools follow a consistent verb_noun pattern with snake_case (e.g., get_contact, list_companies). The 'list' and 'get' prefixes are standard and predictable.
8 tools is well-scoped for a read-only CRM server covering contacts, companies, deals, notes, and associations. Each tool serves a clear purpose without redundancy.
The server is read-only and lacks essential create, update, and delete operations for CRM objects. For a HubSpot CRM server, this is a significant gap that limits agent workflows.