casemargin-mcp-server — Claude Code MCP server: ticket briefs
Turns a support thread into a structured case brief and scores how ready a ticket is for L2 escalation. Handy when cases change hands.
claude mcp add casemargin-mcp-server -e CASEMARGIN_API_KEY=<CASEMARGIN_API_KEY> -- npx -y casemargin-mcp-serverWhat casemargin-mcp-server does
Two tools ship with this server. generate_case_brief takes ticket text between 10 and 50,000 characters and returns JSON: a quick assessment, the next step, status, the current problem, actions already taken with their outcomes, and key context. check_escalation_readiness scores a ticket from 0 to 100, breaks the score into dimensions, predicts what L2 will ask, and lists what is missing.
It does not pull tickets from anywhere. Zendesk and other helpdesks are out of scope — you paste or pipe the thread in yourself. The server reasons over data you hand it.
An API key is optional. Without one, brief generation falls back to an anonymous per-IP tier, and the escalation check is free either way. When a key is present it travels as a request header, so the server refuses to start if CASEMARGIN_API_URL points at a non-https origin outside loopback. npx fetches the package on first run, so there is nothing to install beforehand.
What it helps with
- condense a long ticket thread into a short brief for the next agent
- judge whether a ticket has enough evidence to escalate to L2
- see which questions the second line will ask
- pull the actions already taken and their outcomes out of a thread
- check whether business impact is quantified in the ticket
Example prompts for the agent
- What's happening with this ticket? Here's the thread: customer reports VPN drops every 30 minutes since Monday
- Is this ticket ready to escalate to L2? Score it and tell me what's missing
- Write a case brief for this ticket and give the next step for the receiving agent
How to install casemargin-mcp-server
Platform CLI
claude mcp add casemargin-mcp-server -e CASEMARGIN_API_KEY=<CASEMARGIN_API_KEY> -- npx -y casemargin-mcp-serverReplace <…> with your own values
Platform CLI
codex mcp add casemargin-mcp-server --env CASEMARGIN_API_KEY=<CASEMARGIN_API_KEY> -- npx -y casemargin-mcp-serverReplace <…> with your own values
Config file
{
"mcpServers": {
"casemargin-mcp-server": {
"command": "npx",
"args": [
"-y",
"casemargin-mcp-server"
],
"env": {
"CASEMARGIN_API_KEY": "<CASEMARGIN_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"casemargin-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"casemargin-mcp-server"
],
"env": {
"CASEMARGIN_API_KEY": "<CASEMARGIN_API_KEY>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e CASEMARGIN_API_KEY=<CASEMARGIN_API_KEY> casemargin-mcp-server npx -y casemargin-mcp-serverReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about casemargin-mcp-server
How do I install casemargin-mcp-server in Claude Code?
Run claude mcp add casemargin-mcp-server -e CASEMARGIN_API_KEY=<CASEMARGIN_API_KEY> -- npx -y casemargin-mcp-server. You can leave the key out and still get briefs on the anonymous tier.
What does casemargin-mcp-server do?
It generates a structured brief from a support thread and scores escalation readiness for L2, with a dimensional breakdown and a list of missing items.
Do I need an API key?
Not for the escalation check — that one is free. Brief generation works without a key too, but on an anonymous per-IP tier.
