Integrations for CRM & Ops: HubSpot & Zendesk

Enterprise business operations require seamless customer database updates. Connecting CRMs like HubSpot and ticket systems like Zendesk directly to MCP gives customer support agents a powerful assistant that can update details on the fly, summarize long ticket threads, and cross-reference data between tools.

Prerequisites

1. ▸A HubSpot account with a generated Private App Access Token.
2. ▸A Zendesk administrator account to generate an API Token.
3. ▸(Optional) Sandbox instances for both platforms to prevent accidental edits to real customer data during testing.

HubSpot Contact Update Tool Schema

When building or configuring the HubSpot MCP server, the tools exposed to the agent must have clearly defined input schemas so the agent knows exactly what data it can modify.

Here is an example of how the update_hubspot_contact tool is defined internally:

{
  "name": "update_hubspot_contact",
  "description": "Update details of a contact record inside HubSpot CRM.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "email": { "type": "string" },
      "properties": {
        "type": "object",
        "properties": {
          "firstname": { "type": "string" },
          "lastname": { "type": "string" },
          "company": { "type": "string" }
        }
      }
    },
    "required": ["email", "properties"]
  }
}

Custom Workflows & Prompts

• ▸Triage Ticket Escalation: "Check the Zendesk queue. If a customer sends a ticket labeled critical-severity, search HubSpot using their email to find their account tier. If they are Enterprise, escalate the Zendesk ticket to priority status."
• ▸Draft Replies: "Read ticket #1042. Summarize the customer's frustration, pull their latest contract renewal date from HubSpot, and draft a polite, apologetic reply offering a 10% discount."

Best Practices

• ▸Human-in-the-Loop: For destructive actions or sending emails/replies via Zendesk, always configure the MCP server to return drafts rather than executing the send directly. A human should click "Send".
• ▸Rate Limits: Both HubSpot and Zendesk have strict API rate limits. Ensure your agent doesn't trigger mass updates that could exhaust your quota.

Troubleshooting

• ▸401 Unauthorized: Your Zendesk token requires the email address to be appended in the format email@company.com/token. Ensure the auth header is constructed correctly.
• ▸Property Not Found: HubSpot custom properties have internal names (e.g., annual_revenue) that differ from their display labels. Make sure the agent is using the exact internal property name when pushing updates.

Using with OpenAI Codex

To use this MCP server with the OpenAI Codex CLI, you can add it to your configuration using the codex mcp add command:

codex mcp add --name crm-hubspot-zendesk --command "npx @modelcontextprotocol/server-crm-hubspot-zendesk"

(Note: Depending on the server, you may need to append arguments or use --env flags for environment variables as described in the configuration section above)