coretext-hubspot-mcp-server

Coretext HubSpot MCP Server

This MCP server was generated using the Template Orchestrator and includes the following integrations:

Available Tools

This MCP server provides 59 tools across 1 integrations:

Hubspot Tools

• hubspot_get_deal: Retrieve a deal by ID with optional associations
• hubspot_get_form: Get a specific form configuration
• hubspot_get_task: Get a specific task
• hubspot_get_ticket: Retrieve a ticket by ID with optional associations
• hubspot_list_deals: List all deals with optional filtering
• hubspot_list_forms: Get all forms with optional filtering
• hubspot_list_tasks: List all tasks with optional filtering
• hubspot_create_deal: Create a new deal with specified properties and associations
• hubspot_create_task: Create a new task
• hubspot_delete_deal: Delete a deal
• hubspot_get_company: Retrieve a company by ID
• hubspot_get_contact: Retrieve a contact by ID
• hubspot_submit_form: Submit form data and create/update contact
• hubspot_update_deal: Update a deal's properties including stage transitions. IMPORTANT: HubSpot v3 API requires properties to be wrapped in a 'properties' object. When using this endpoint, ensure your request body follows the format: {"properties": {"dealname": "Updated Deal", "amount": "5000", "dealstage": "closedwon"}}
• hubspot_update_task: Update a task's properties and status
• hubspot_get_pipeline: Get a specific deal pipeline configuration
• hubspot_get_workflow: Get a specific workflow configuration
• hubspot_list_tickets: List all tickets with optional filtering
• hubspot_search_deals: Search deals using filters and criteria
• hubspot_create_ticket: Create a new support ticket with contact associations
• hubspot_delete_ticket: Delete a ticket
• hubspot_list_contacts: List all contacts with optional filtering
• hubspot_list_webhooks: Get all webhook subscriptions
• hubspot_update_ticket: Update a ticket's properties and status. IMPORTANT: HubSpot v3 API requires properties to be wrapped in a 'properties' object. When using this endpoint, ensure your request body follows the format: {"properties": {"subject": "Updated Ticket", "hs_ticket_priority": "HIGH"}}
• hubspot_create_company: Create a new company with specified properties
• hubspot_create_contact: Create a new contact with specified properties
• hubspot_create_webhook: Create a new webhook subscription
• hubspot_delete_company: Delete a company
• hubspot_delete_contact: Delete a contact
• hubspot_delete_webhook: Delete a webhook subscription
• hubspot_list_companies: List all companies with optional filtering
• hubspot_list_pipelines: Get all deal pipelines with their stages
• hubspot_list_workflows: Get all workflows with optional filtering
• hubspot_search_tickets: Search tickets using filters and criteria
• hubspot_update_company: Update a company's properties. IMPORTANT: HubSpot v3 API requires properties to be wrapped in a 'properties' object. When using this endpoint, ensure your request body follows the format: {"properties": {"name": "Updated Company", "domain": "example.com"}}
• hubspot_update_contact: Update a contact's properties. IMPORTANT: HubSpot v3 API requires properties to be wrapped in a 'properties' object. When using this endpoint, ensure your request body follows the format: {"properties": {"phone": "+1-555-0199", "jobtitle": "Updated Title"}}
• hubspot_update_webhook: Update a webhook subscription
• hubspot_create_pipeline: Create a new deal pipeline
• hubspot_delete_pipeline: Delete a deal pipeline
• hubspot_search_contacts: Search contacts using filters and criteria
• hubspot_update_pipeline: Update a deal pipeline configuration. NOTE: Pipeline updates use flat parameter format (unlike CRM objects which require nested properties). Request body format: {"label": "Pipeline Name", "displayOrder": 1}
• hubspot_get_contact_list: Get a specific contact list with members
• hubspot_search_companies: Search companies using filters and criteria
• hubspot_enroll_in_workflow: Enroll objects in a workflow
• hubspot_list_contact_lists: Get all contact lists
• hubspot_create_contact_list: Create a new contact list
• hubspot_add_contacts_to_list: Add contacts to an existing list
• hubspot_get_form_submissions: Get submissions for a specific form
• hubspot_list_ticket_pipelines: Get all ticket pipelines with their stages
• hubspot_unenroll_from_workflow: Unenroll an object from a workflow
• hubspot_list_company_properties: Get all company property definitions
• hubspot_list_contact_properties: Get all contact property definitions
• hubspot_associate_deal_to_company: Associate a deal with a company
• hubspot_associate_deal_to_contact: Associate a deal with a contact
• hubspot_list_contact_associations: Get all associations for a contact
• hubspot_remove_contacts_from_list: Remove contacts from a list
• hubspot_associate_ticket_to_company: Associate a ticket with a company
• hubspot_associate_ticket_to_contact: Associate a ticket with a contact
• hubspot_associate_contact_to_company: Associate a contact with a company

Installation

npm install @coretext-ai-public/coretext-hubspot-mcp-server-c296df67-e450-4b54-b3f3-095d3b64560c

Environment Setup

Create a .env file with the following variables:

HUBSPOT_ACCESS_TOKEN=your_hubspot_access_token_here

Usage

Running the server

# Development mode
npm run dev

# Production mode
npm run build && npm start

Using with Claude Desktop

Add this to your Claude Desktop configuration:

{
  "mcpServers": {
    "coretext-hubspot-mcp-server": {
      "command": "npx",
      "args": ["@coretext-ai-public/coretext-hubspot-mcp-server-c296df67-e450-4b54-b3f3-095d3b64560c"],
      "env": {
        "HUBSPOT_ACCESS_TOKEN": "your_hubspot_access_token_here"
      }
    }
  }
}

Instructions for Fetching API Keys/Tokens

• COMING SOON

Advanced Features

Request Cancellation

This MCP server supports request cancellation according to the MCP cancellation specification. Clients can cancel in-progress requests by sending a notifications/cancelled message with the request ID.

When a request is cancelled:

• The server immediately stops processing the request
• Any ongoing API calls are aborted
• Resources are cleaned up
• No response is sent for the cancelled request

Progress Notifications

The server supports progress notifications for long-running operations according to the MCP progress specification.

To receive progress updates:

1. Include a progressToken in your request metadata
2. The server will send notifications/progress messages with:
   • Current progress value
   • Total value (when known)
   • Human-readable status messages

Progress is reported for:

• Multi-step operations
• Batch processing
• Long-running API calls
• File uploads/downloads

Example progress notification:

{
  "method": "notifications/progress",
  "params": {
    "progressToken": "operation-123",
    "progress": 45,
    "total": 100,
    "message": "Processing item 45 of 100..."
  }
}

Generated Information

• Generated at: Fri Oct 24 2025 15:17:56 GMT+0000 (Coordinated Universal Time)
• Orchestrator version: 0.0.2
• Template repository: Coretext-AI-Dev/server-template-v2
• Total endpoints: 59