MCP server
Connect an AI client to the Klaracase MCP server (v0.107.0) to ground answers on the corpus and citation graph.
Credits and repeats: what counts as the same answerClient support
Do you use ChatGPT or Claude in the chat? Go to the guide under AI assistants
The server offers two ways in: a personal bearer token for clients that allow custom headers, and OAuth 2.1 for chat clients that do not. Vendor details as of 2026-11-07.
OAuth 2.1 has been live since 2026-07-29. We tested Claude and ChatGPT through to a first tool call with real accounts, ChatGPT through the directory entry. Plan and authentication details from the vendors were checked on 2026-11-07 and can change at any time.
Get a token
Connect a client
The MCP endpoint is https://klaracase.de/mcp (streamable HTTP, POST). It accepts both a bearer token and OAuth 2.1.
A connection is working once the client lists the klaracase tools and a first call returns a result. A client that shows the server as connected but lists no tools has not authenticated. See below.
Working with AI assistants
An AI assistant does not always call klaracase on its own. When it answers from memory, call klaracase yourself, as the rows below show. This makes the answers easier to rely on: you get decisions with sources instead of statements without proof.
When it does not work
Credits, API budget and limits
Every priced tool call is paid in credits. This section explains where the credits come from and what a client does when a call is refused.
Plan credits
Each plan includes credits for one credit period. They pay for the web app, the API and MCP together. A paid plan renews them when the next credit period starts.
API budget
On the Professional plan, and on Enterprise where the contract provides it, an organization admin can load a prepaid API budget in euros. The API budget pays for MCP and API calls once the plan credits are used up. It does not expire. The web app does not use it: when the plan credits are used up, the web app stops. The API budget is for AI assistants and programs, which should not stop halfway through a task.
Top up the API budgetOrder of payment
The plan credits are spent first. The API budget pays for the rest, at the rate on the pricing page. A call is paid in full or it does not run: if the plan credits and the API budget together cannot pay for it, nothing is executed and nothing is charged. A call never runs in part.
Limits per connection and per token
An organization admin can set a credit limit for each MCP connection (the sign-in of an AI client) and each API token. The limit counts plan credits and API budget credits together in one credit period. When a connection reaches its limit, only that connection is refused. The other connections of the organization keep working. The count starts again with the next credit period.
Three refusals and what a client does
Each refusal is a tool error with a stable error_code and a message. Nothing ran and nothing was charged. A refusal stays the same until a person acts or the credit period ends, so do not retry it in a loop.
The value plan_credits_exhausted for reason is reserved. The server does not serve it today. A client must tolerate a reason value it does not know and treat it like api_budget_not_available.
A client or an AI agent never tops up, pays or changes a limit by itself. It tells its user what to do and stops.
Fields in the answer
Every answer and every refusal carries the credits block with metered, cost and credits_remaining. cost counts the credits that the plan and the API budget paid together. credits_remaining is the plan credits left and never includes the API budget. An organization that holds an API budget, or may load one, also gets api_budget with cents (what is left, in euro cents), rate_cents_per_credit and credits_at_rate (how many more credits that pays for). For any other organization the key is absent.
Price
The price per credit from the API budget stands on the pricing page. This page shows no price.
Go to the pricing pageCorpus coverage
Data processing
Examples by area of law
MCP tools
Each tool description below lists its purpose, arguments, refusal codes, and credit price. Response fields are documented in the tool guide so a client does not load them on every connection.
Read the MCP tool guide