LexGraph

de.lexgraphPublished by lexgraph.deOfficial publisherv1.0.1Updated Nov 5, 2026

German and EU legal research with verifiable case law, legislation and legal sources.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

LexGraph is a remote MCP server for German and EU legal research, giving an assistant access to case law, legislation and legal sources.

What you can do
  • Research German and EU legal sources, including case law and legislation, through the remote endpoint.
  • Retrieve legal references that are described as verifiable, so answers can be traced back to sources.
  • No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Useful when an assistant needs to look up German or EU statutes and court decisions, for example to support legal research questions or to ground answers in citable legal sources.
Requirements
A remote MCP endpoint at api.lexgraph.de over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared.
Before you install
Access requires OAuth sign-in, so the server receives account credentials through that flow. Legal information retrieved this way is research material, not legal advice, and should be checked against the cited sources.

Installation

In SourceWeft

  1. Open LexGraph in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/de.lexgraph%2Flexgraph/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lexgraph": {
      "type": "http",
      "url": "https://api.lexgraph.de/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestNov 5, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.