CaseMargin MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CASEMARGIN_API_KEY | No | Your CaseMargin API key. Optional — without it, brief generation runs on the anonymous per-IP tier. Get a free key at https://casemargin.com/signup. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_case_briefA | Generate a structured case brief from a support ticket thread. Returns an assessment, what has been tried, current status, and recommended next step. |
| check_escalation_readinessA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Both tools operate on support tickets but have clearly distinct purposes: one generates a structured brief, the other assesses escalation readiness. No overlap or ambiguity in their output.
Both tool names follow a consistent verb_noun pattern with underscores, making the toolset predictable and easy to navigate.
With only two tools, the server feels thin for the apparent domain, but each tool serves a specific analytic function, making it a borderline case.
The two tools cover the workflow of briefing and escalation readiness, but lack any case management operations (e.g., list, update, delete), leaving notable gaps in the domain surface.