Skip to main content

​
Connect Case.dev through MCP

One authenticated endpoint. No duplicate orchestration layer. Your MCP client stays in control while Case.dev provides matters, vaults, OCR, transcription, and legal research.

​
Endpoint

Streamable HTTP
https://api.case.dev/mcp

​
API Key

Use a Case.dev API key directly in the bearer header.
mcpServers.json
{
  "mcpServers": {
    "case.dev": {
      "type": "streamable-http",
      "url": "https://api.case.dev/mcp",
      "headers": {
        "Authorization": "Bearer sk_case_YOUR_API_KEY"
      }
    }
  }
}

​
OAuth Bearer

Case.dev also accepts OAuth bearer tokens. Use this when your MCP client can inject a token issued through your Case.dev auth flow.
mcpServers.json
{
  "mcpServers": {
    "case.dev": {
      "type": "streamable-http",
      "url": "https://api.case.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${CASEDEV_OAUTH_TOKEN}"
      }
    }
  }
}

​
Tool Surface

The first release stays intentionally small.
  • Matters
  • Work items
  • Human orchestration decisions
  • Vault objects
  • OCR jobs
  • Transcription jobs
  • Deep legal research

​
Why This Shape

Case.dev should not be the orchestrator inside MCP. The client is already the orchestrator. The server should expose the legal substrate cleanly and stay out of the way.

CLI

Install the Case.dev CLI.

Matters

Matter-native legal operations.