MCP servers for a customer support agent
The MCP server bundle to build an AI that drafts support replies and files issues.
3 servers · ~36 tools · Last updated June 17, 2026
TL;DR: A support agent needs to read the knowledge base, raise issues for real bugs, and keep the team in the loop. This bundle connects all three so the agent turns a customer message into a drafted reply plus the right internal follow-up.
Bottom line: start with Linear MCP Server (official remote) and add the rest as your needs grow. All 3 install together via the merged config below (~36 tools total).
Tool budget: this stack exposes about 36 tools. That's within Cursor's practical ~40-tool ceiling, so all servers can stay enabled together. Check your own config →
What's in the stack
File and update issues for bugs and feature requests.
Source ↗One-click config
All 3 servers merged into a single block — pick your client and paste.
{
"mcpServers": {
"linear-mcp-server-official-remote": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.linear.app/mcp"
]
},
"slack-mcp-server-korotovsky": {
"command": "npx",
"args": [
"-y",
"slack-mcp-server@latest",
"--transport",
"stdio"
],
"env": {
"SLACK_MCP_XOXP_TOKEN": "<your-slack-user-oauth-token-xoxp>"
}
},
"notion-mcp-server-official": {
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_TOKEN": "<your-notion-integration-token>"
}
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json and fully restart Claude Desktop. Replace any placeholder keys/tokens with your own.
Capabilities this stack covers
FAQ
Should the agent reply to customers directly?
Start with draft-and-review. Let it propose replies and file issues; a human approves anything customer-facing until you trust it.
Can I use Zendesk/Intercom instead?
Swap the ticketing slot for whatever you run — the manage-tasks-projects capability lists the options.