klaracase MCP & API for German law
The full corpus behind an MCP server and a REST API. Wire klaracase into your assistant, your agent, or your own product.
Built for your tools
MCP for assistants like Claude and your agents, a REST API for your own applications. Both offer search, decision texts, the citation graph, datapackages and the citation check. Over REST, the citation check also reads uploaded PDF and DOCX files. Every answer comes with the decision it is based on.
Pay once per answer: repeats in your credit period are included. How we charge
.mcp.json
{
"mcpServers": {
"klaracase": {
"type": "http",
"url": "https://klaracase.de/mcp",
"headers": {
"Authorization": "Bearer <token>"
}
}
}
}# MCP over HTTP
curl -X POST "https://klaracase.de/mcp" \
-H "Authorization: Bearer <token>" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"search_decisions",
"arguments":{"query":"Verkehrssicherungspflicht"}}}'# REST
curl "https://klaracase.de/api/v1/decisions/search?query=Verkehrssicherungspflicht" \
-H "Authorization: Bearer <token>"One call, a grounded answer
Every answer names its Aktenzeichen and paragraph number, matched against the corpus.
Metered by credits, authenticated by token
An API token belongs to exactly one organization. Every call, over MCP or REST, draws on that organization's credit balance, the same one the web app uses, at the same price. No separate billing, no separate account.
Chat apps such as ChatGPT and Claude need no token. They sign in with your klaracase account. Set up klaracase in ChatGPT and Claude
Data processing. The API and the MCP server use the same search as the web app. OpenRouter and Voyage AI process the text of a search query in the EU. Citation Check examines texts on our server in Germany, without AI services. More on privacy and security
API and MCP by area of law
Each area of law has its own page with an example query and the steps to connect through MCP and the REST API.