Case Knowledge is an MCP Server. It gives AI assistants (Claude, etc.) direct access to your legal cases and documents from connected source systems (e.g. Advoware, Amberlo, Lexolution, Secib) and supports configurable prompts.
Tools
The server provides the following tools an AI assistant can call:
| Tool | Description |
|---|---|
stp_ltck_get_connections |
Lists all connected source systems with their connection URIs. |
stp_ltck_list_cases |
Lists cases, optionally filtered by connection, title, and a result limit. |
stp_ltck_list_analyzed_cases |
Lists cases whose latest analysis finished in a date range, optionally filtered by title and a result limit. |
stp_ltck_get_case |
Returns the case details (summary, participants, timeline, status) without the documents. Access is always verified against the source system. |
stp_ltck_list_documents |
Returns the case’s documents with their summaries, without the per-document participants and events. |
stp_ltck_get_document_metadata |
Returns the metadata of a single document: its name, file type and date, and — once the document has been analyzed — its summary, participants and timeline events. A document that has not been analyzed yet is returned with a note saying so. |
stp_ltck_get_document_content |
Returns the text content of a document. Uses the processed full-text version when available; otherwise it extracts the text directly from the original document — so document content is available even before a case has been processed. |
stp_ltck_search_documents |
Searches the documents within a case for content matching a query and returns the most relevant documents. Whether this is semantic (meaning-based) or lexical (keyword) search depends on the connected source system. |
stp_ltck_get_timeline |
Returns the case timeline (events sorted by date). |
stp_ltck_create_case |
Creates a new case in a connected Advoware, Amberlo or SECIB system. Requires the connection URI and the case name; optional fields depend on the system. Returns the new case’s URI. Every call creates a new case, and cases can’t be deleted through MCP. |
stp_ltck_upload_document |
Uploads a file (PDF, TXT, MD, DOCX or XLSX) into a case. Requires the case URI, file bytes, original file name, and MIME content type; returns the document ID assigned by the source system. Reserved for interactive MCP apps and host integrations; AI models don’t call it themselves (see below). |
Typical workflow
An AI assistant will typically follow this sequence:
-
stp_ltck_get_connections— discover which catalogues are connected -
stp_ltck_list_cases— find the relevant case -
stp_ltck_get_case— load the case details -
stp_ltck_list_documents— load the case’s documents and their summaries -
stp_ltck_get_document_metadata— load a single document’s summary, participants and timeline -
stp_ltck_search_documents— find the most relevant documents in a case by content -
stp_ltck_get_document_content— read the content of individual documents
stp_ltck_upload_document is not part of this sequence.
It is marked as app-only (MCP Apps
_meta.ui.visibility: ["app"]), because an AI model can’t
reliably pass a file’s raw contents as a tool argument. AI assistants
that support this setting don’t offer the tool to the model, so the
model never calls it. Interactive MCP apps can still call it, and so can
MCP hosts that upload a user’s file directly.
Resources
Every case is available as an MCP resource at its case URI. The resource contains the full case JSON: metadata, documents list, events, participants, and AI-augmented summaries (if the case has been processed by Case Knowledge).
Resource templates
All cases and connections are identified by these source-specific URI templates:
| Type | URI |
|---|---|
| Connection (catalogue) | stplegaltwin://advoware/{catalogue} |
| Case | stplegaltwin://advoware/{catalogue}/{caseId} |
| Connection (portfolio) | stplegaltwin://amberlo/{portfolioId} |
| Case | stplegaltwin://amberlo/{portfolioId}/{caseId} |
| Connection | stplegaltwin://lexolution/{connectionId} |
| Case | stplegaltwin://lexolution/{caseId} |
Examples: stplegaltwin://advoware/DB1/2026000022,
stplegaltwin://amberlo/portfolio-1/2026000022,
stplegaltwin://lexolution/abc-123
Use stp_ltck_get_connections and
stp_ltck_list_cases to discover concrete connection and
case URIs.
Prompts
Prompts are supported and configurable on both the tenant and personal level via the Case Knowledge UI. The server provides these built-in starter prompts:
| Name | Title | Purpose |
|---|---|---|
summarize_case |
Aktenzusammenfassung erstellen | Summarizes the facts, important details, and current status of a case. |
case_status |
Übersicht über den aktuellen Stand des Falls | Identifies unresolved questions, deadlines, appointments, and possible next steps. |
case_timeline |
Zeitliche Übersicht des Falls erstellen | Creates a chronological table of important case events, including deadlines and unclear or conflicting dates. |
list_participants |
Auflistung aller (KI-erkannten) Beteiligten | Lists participants, their roles, and their relationship to the case, grouped by side. |
key_documents |
Übersicht über alle Dokumente der Akte mit kurzer Zusammenfassung | Lists the important case documents chronologically with a short summary and their significance. |
The prompts are available through the MCP prompt interface and can be selected as chat starters. In the Case Knowledge UI, Restore default prompts recreates missing built-in prompts and resets built-in prompts to their original text. Custom tenant-wide prompts and private prompts are left unchanged.
Authentication
This MCP Server requires the scope lt.mcp3 or role
LegalTwin.McpUser (no default group) and license
legaltwin-mcp. It is available as a protected resource at
https://common.stp-cloud.de/legal-twin/caseknowledge/mcp
and supports stateless Streamable HTTP. To authenticate, an MCP host
needs an STP.Identity client registration.
Installation
Claude AI
We do not endorse using Claude AI for working with real client data or professional secrets!
| Setting | Value |
|---|---|
| Name | Legal Twin Case Knowledge |
| Remote MCP Server URL | https://common.stp-cloud.de/legal-twin/caseknowledge/mcp |
| OAuth Client ID | claude_ai |
LibreChat
These settings only work running LibreChat at http://localhost:3080. If your instance is running at a different URL, you need to obtain a dedicated Identity Configuration from us. Please send us a service request.
| Setting | Value |
|---|---|
| Name | Legal Twin Case Knowledge |
| MCP Server URL | https://common.stp-cloud.de/legal-twin/caseknowledge/mcp |
| Transport | Streamable HTTPS |
| Authentication | OAuth |
| Client ID | librechat |
| Authorization URL | https://common.stp-cloud.de/identity/connect/authorize |
| Token URL | https://common.stp-cloud.de/identity/connect/token |
| Scope | lt.mcp3 offline_access |
| Token Exchange Method | Auto |
Related to