Casemargin MCP server

CaseMargin MCP Server

CaseMargin MCP server exposes support case reasoning tools — generate structured case briefs and check escalation readiness from any MCP-compatible AI client (Claude Desktop, Claude Code, Cursor, and others). It sits above helpdesk data layers: it doesn't read tickets from Zendesk or any ticketing system — you pass ticket content in, it returns structured analysis powered by the same AI that runs casemargin.com.

Tools

generatecasebrief

Generate a structured case brief from a support ticket thread. Returns an assessment, what has been tried, current status, and recommended next step.

Input: ticket_content (string) — the full ticket thread: messages, internal notes, whatever you paste or pipe in. 10–50,000 characters.

Output (structured JSON):

{
  "quick_scan": {
    "assessment": "…what this case is about and how serious it is…",
    "next_step": "…the single action the receiving agent should take now…",
    "status": "Waiting on customer"
  },
  "full_brief": {
    "current_problem": "…symptoms, blockers, business impact…",
    "actions_taken": ["action → outcome", "…"],
    "key_context": "…customer plan, history, logs, error codes…"
  },
  "metadata": {
    "input_length": 4210,
    "brief_length": 1250,
    "compression_ratio": 0.3
  }
}

checkescalationreadiness

Analyze whether a support ticket is ready to escalate to L2. Returns a readiness score (0–100), dimensional breakdown, predicted L2 questions, and missing items.

Input: ticket_content (string) — the ticket notes to evaluate. 10–20,000 characters.

Output (structured JSON):

{
  "overall_score": 62,
  "readiness": "borderline",
  "dimensions": {
    "problem_clarity": { "score": 80, "note": "…" },
    "troubleshooting_evidence": { "score": 55, "note": "…" },
    "business_impact": { "score": 40, "note": "…" },
    "next_action": { "score": 70, "note": "…" },
    "billing_defensibility": { "score": 65, "note": "…" }
  },
  "predicted_l2_questions": ["…", "…"],
  "missing_items": ["…", "…"]
}

Installation

Nothing to install ahead of time — npx fetches the package on first run. Add this to your claudedesktopconfig.json and restart Claude Desktop:

{
  "mcpServers": {
    "casemargin": {
      "command": "npx",
      "args": ["-y", "casemargin-mcp-server"],
      "env": {
        "CASEMARGIN_API_KEY": "your-api-key-here"
      }
    }
  }
}

Cursor and Claude Code take the same shape of config in their own files. The config lives at ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows. Quit and reopen the app rather than closing the window — the config is read at process start.

The API key is optional — without it, brief generation runs on the anonymous per-IP tier. Get a free key (8 briefs/month) at casemargin.com/signup. The escalation readiness check is free and needs no key. Drop the whole env block to run keyless.

Also on the MCP Registry as com.casemargin/casemargin-mcp-server, and on npm.

Running from source

Only needed if you're modifying the server:

git clone https://github.com/Casemargin/casemargin-mcp-server.git
cd casemargin-mcp-server
npm install
npm run build

Then point command at node and args at the absolute path of the built dist/index.js.

Example usage

"What's happening with this ticket?"

Paste a ticket thread into your AI client and ask what's going on:

You: What's happening with this ticket?

Customer reports VPN drops every ~30 min since Monday. Rebooted router, reinstalled client v4.2, issue persists. Firewall logs show DHCP lease renewing every 30 min. Customer is on the Premium SLA, CFO is affected. Told them we'd escalate if not fixed by Friday…

Shortened. The full README is on GitHub.