Back to Blog
RecipeJan 27, 202618 min read

Build an AI Customer Support Summarizer with MCP (Intercom + Zendesk Recipe)

NT

Nikhil Tiwari

MCP Playground

🍳 MCP Recipe

  • What you'll build: An AI workflow that fetches support tickets from Intercom or Zendesk and produces summaries and digests
  • MCP servers used: Intercom MCP, Zendesk MCP (or one of them)
  • Time to complete: 60-90 minutes
  • Difficulty: Intermediate

Support teams drown in tickets. This recipe helps you build an AI assistant that pulls conversations from Intercom or Zendesk, summarizes them, and surfaces trends and urgent issues.

You'll be able to ask things like:

  • "Summarize all open Intercom conversations from the last 24 hours and flag anything that mentions 'billing' or 'refund'."
  • "Give me a daily digest of Zendesk tickets: count by priority, list the top 5 longest-open tickets, and suggest which need escalation."
  • "Compare this week's support volume to last week and list the top 3 topics."

What You'll Build

The flow: MCP tools fetch tickets/conversations → AI reads and summarizes → you get a concise report (in chat or exported).

1. Fetch

Intercom/Zendesk MCP gets recent tickets

2. Analyze

AI summarizes and extracts themes

3. Report

Digest, trends, and escalation hints

Prerequisites

Intercom or Zendesk

Active account with API access

API Credentials

API key or OAuth for the platform

MCP Client

Claude Desktop or Cursor

Step 1: Set Up Intercom or Zendesk MCP

Use an MCP server that wraps the Intercom or Zendesk API (e.g. community Intercom MCP, Zendesk MCP). Configure it with your API key or OAuth credentials so it can list conversations, get ticket details, and optionally update tickets.

Typical tools you'll see: list_conversations, get_conversation, search_tickets, get_ticket, list_agents.

Step 2: Configure in Your MCP Client

Add the server to Claude Desktop or Cursor. For HTTP-based servers, use the server URL and auth header. For STDIO servers, set command and env vars for the API key.

Step 3: Example Prompts

  • "Fetch all Zendesk tickets from the last 24 hours. Summarize by priority and list the 3 most urgent. For each, give a one-line summary and the ticket URL."
  • "Get open Intercom conversations. Group by topic (billing, technical, onboarding) and tell me how many are in each group and which have been waiting longest."
  • "Create a Monday morning digest: compare ticket volume last week vs the week before, top 5 tags, and suggest one process improvement."

Best Practices

  • Use read-only API scopes when you only need summaries; add write scope only if you want the AI to update tickets.
  • For large teams, run digests on a schedule (e.g. cron + script that calls your AI with a fixed prompt) and post to Slack or email.

Test MCP Servers Online

Validate Intercom or Zendesk MCP in the browser

Open MCP Playground →

Related Recipes

Frequently Asked Questions

Do I need both Intercom and Zendesk MCP?
No. You can use only Intercom or only Zendesk. If you use both, the AI can combine data from both platforms in one summary.
Can the AI reply to tickets automatically?
Only if your MCP server exposes write actions (e.g. reply to conversation) and you configure them. This recipe focuses on read-only summarization; you can extend it to drafts or replies with the right tools and guardrails.
NT

Written by Nikhil Tiwari

15+ years in product development. AI enthusiast building developer tools that make complex technologies accessible to everyone.