Customer Support Plugin Integrations: Supported Platforms and MCP Configuration Guide

The customer support plugin integrates with Slack, Microsoft Teams, Intercom, Zendesk, HubSpot, Salesforce, and other enterprise tools through configurable MCP (Model Context Protocol) connections that use category-based placeholders to remain tool-agnostic.

The customer support plugin in the anthropics/knowledge-work-plugins repository provides a flexible integration framework designed to work with your existing tech stack. Rather than hardcoding vendor-specific APIs, the plugin uses generic category placeholders that map to concrete services via MCP servers, allowing teams to connect their preferred CRM, help desk, and communication platforms without modifying source code.

Default Integrations and Supported Platforms

According to customer-support/CONNECTORS.md lines 9-19, the plugin organizes integrations into six functional categories. Each category ships with default MCP servers pre-configured in customer-support/.mcp.json, while offering alternatives that you can substitute via Claude settings.

Chat and Communication

• Default: Slack
• Alternatives: Microsoft Teams

Email and Cloud Storage

• Email: Microsoft 365 (default)
• Cloud Storage: Microsoft 365 (default)

Support Platforms

• Default: Intercom
• Alternatives: Zendesk, Freshdesk, HubSpot Service Hub

CRM and Customer Data

• Default: HubSpot
• Alternatives: Salesforce, Pipedrive

Knowledge Management

• Defaults: Guru, Notion
• Alternatives: Confluence, Help Scout

Project Tracking

• Default: Atlassian (Jira/Confluence)
• Alternatives: Linear, Asana

The customer-support/README.md lines 47-53 reiterates these default connections and confirms that the plugin is designed to work with any MCP-compliant server that implements the corresponding category interface.

How the Tool-Agnostic Integration Mechanism Works

The plugin architecture decouples business logic from specific vendor implementations through placeholder notation. In customer-support/.claude-plugin/plugin.json and skill definitions like customer-support/skills/ticket-triage/SKILL.md, you will find references to generic categories such as ~~support platform and ~~chat.

At runtime, Claude replaces these placeholders with the concrete MCP server URLs configured in your Claude settings. Because the plugin code references only the category placeholders (e.g., ~~support platform rather than "Intercom" or "Zendesk"), swapping one vendor for another requires only updating the MCP connection configuration—no changes to the plugin source files are necessary.

Configuring Customer Support Plugin Integrations

Installing with Default Integrations

To use the plugin with the pre-configured default servers (Slack, Intercom, HubSpot, etc.), run:

claude plugins add knowledge-work-plugins/customer-support

Overriding Default Integrations

To replace a default integration with an alternative platform, update your Claude MCP settings rather than modifying plugin files. For example, to use Zendesk instead of the default Intercom for the support platform category:

# In Claude settings → MCP connections

# Replace the placeholder for the "support platform" category with your Zendesk MCP URL

This configuration change takes effect immediately across all plugin commands that reference ~~support platform, including ticket triage and response drafting.

Real-World Usage Examples

Ticket Triage with Multiple Integrations

When you run the /triage command defined in customer-support/skills/ticket-triage/SKILL.md, Claude simultaneously queries your configured support platform, CRM, and chat systems:

You: /triage Customer reports "cannot reset password" – premium plan

Claude (leveraging Intercom ticket history, HubSpot CRM contact data, and Slack for internal notes):
- Category: Authentication issue
- Priority: P2
- Suggested routing: Tier 1 Support → Engineering

Knowledge Base-Assisted Responses

The plugin can draft responses that automatically pull from your configured knowledge base:

You: /draft-response Customer asked for API rate-limit details

Claude (retrieves relevant Guru article, includes it in the response):
"Hi Alex, our API allows up to 1,000 requests per minute… (full answer)"

Summary

• Six integration categories are supported: Chat, Email, Cloud Storage, Support Platform, CRM, and Knowledge Base/Project Tracking.
• Tool-agnostic placeholders like ~~support platform and ~~chat allow vendor swapping without code changes.
• Default servers are defined in customer-support/.mcp.json and include Slack, Intercom, HubSpot, and Microsoft 365.
• Alternative options such as Zendesk, Salesforce, and Linear can be configured via Claude MCP settings.
• All integration mappings are documented in customer-support/CONNECTORS.md and customer-support/README.md.

Frequently Asked Questions

What customer support platforms integrate with the plugin by default?

By default, the plugin connects to Intercom for support ticketing, HubSpot for CRM data, Slack for internal chat, Microsoft 365 for email and storage, and Guru/Notion for knowledge management. These defaults are pre-configured in the .mcp.json file bundled with the plugin.

Can I use Zendesk instead of Intercom with this customer support plugin?

Yes. The plugin is designed to be tool-agnostic; you can replace Intercom with Zendesk, Freshdesk, or HubSpot Service Hub by updating the MCP connection for the ~~support platform category in your Claude settings. No changes to the plugin code in anthropics/knowledge-work-plugins are required.

How does the placeholder integration system work?

The plugin uses category placeholders (e.g., ~~support platform, ~~crm) in its skill definitions. At runtime, Claude resolves these placeholders to concrete MCP server URLs based on your configuration. This abstraction layer means the plugin logic remains constant even when you switch underlying service providers.

Where are the integration options documented?

The complete list of categories, default servers, and alternatives is maintained in customer-support/CONNECTORS.md. High-level setup instructions and the default MCP connection list appear in customer-support/README.md under the "Included MCP connections" section.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}