Customer Support Loadout
5 MCP servers for triaging tickets without losing context
Last verified:
A support agent's loadout: read a ticket in Intercom, search the runbook in Notion, file a Linear bug if needed, broadcast in Slack, follow up via email — all from one chat.
Install Customer Support Loadout
Paste into~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"intercom": {
"command": "npx",
"args": ["-y", "intercom-mcp"],
"env": { "INTERCOM_ACCESS_TOKEN": "..." }
},
"notion": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-notion"],
"env": { "NOTION_TOKEN": "secret_..." }
},
"linear": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-linear"],
"env": { "LINEAR_API_KEY": "lin_api_..." }
},
"slack": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-slack"],
"env": { "SLACK_BOT_TOKEN": "xoxb-...", "SLACK_TEAM_ID": "T..." }
},
"resend": {
"command": "npx",
"args": ["-y", "resend-mcp"],
"env": { "RESEND_API_KEY": "re_..." }
}
}
}After pasting, fully restart your MCP client. Replace placeholders (paths, API keys) with your own values.
What's in this loadout
- Intercom MCPcoremcp
Read open conversations, pull customer history, post replies as a team member.
- Notion MCP Servercoremcp
Query the support runbook, internal FAQ, customer notes — the agent grounds its answers in your real docs.
- Linear MCP Servercoremcp
File bugs the user reports straight into engineering's queue with the right project and labels.
- Slack MCP Servercoremcp
Ping the on-call channel for urgent escalations and notify channels of resolved incidents.
- Resend MCPoptionalmcp
Send polished follow-up emails outside the in-app chat (e.g. when a customer churned).
What you can do with it
Triage and escalate
Pull the 5 oldest open conversations in intercom. For each, search notion for known runbooks. If it's a confirmed bug, file a linear issue in the "Customer Bugs" project and reply in intercom with a link to the issue ID.Daily support briefing
Summarise yesterday's conversations from intercom by theme, identify the top 3 pain points, and post the summary in #support-daily on slack.Resolved incident broadcast
For the latest closed linear issue tagged "incident", draft a customer-facing recap in resend and post a short version in #incidents on slack.
Client compatibility
- Claude Desktop 0.7.4Tested ✓
- Cursor 0.42+Tested ✓
- Windsurf 1.4Tested ✓
- Continue 0.9Untested
Variants
Heavy version
Adds Zendesk for teams running both Intercom and Zendesk, plus Memory for long-running customer stories.
Adds: zendesk-mcp, mcp-server-memory
Lite version
Just Intercom + Notion + Linear. Enough to read, look up, and file.
Removes: mcp-server-slack, resend-mcp
FAQ — Customer Support Loadout
What is the Customer Support Loadout?
A support agent's loadout: read a ticket in Intercom, search the runbook in Notion, file a Linear bug if needed, broadcast in Slack, follow up via email — all from one chat. It includes 5 MCP servers: Intercom MCP, Notion MCP Server, Linear MCP Server, Slack MCP Server, Resend MCP.
Does this loadout work with Cursor and Windsurf?
Yes. The config block above is one JSON object that drops into Claude Desktop's, Cursor's, or Windsurf's MCP config. Each client uses the same mcpServers schema; only the file path differs.
How long does setup take?
About 3 minutes the first time: copy the config, paste it into your client's MCP configuration file, replace placeholder API keys with your own, and restart the client.
Can I customise this loadout?
Yes. Use the Lite version if you want fewer servers, or the Heavy version to add 2 more for advanced workflows. You can also remove any individual server by deleting its entry from the JSON.
How much does it cost?
Loadout itself is free. Most listed servers are open-source and free to run. Servers that talk to paid SaaS (Stripe, SendGrid, Linear, etc.) follow that vendor's pricing.
When was this loadout last verified?
Last verified on 2026-04-24. We re-test featured loadouts at least monthly and update the config when MCP servers ship breaking changes.