Legalize

Legalize — the MCP connector for consolidated legislation

What a law said on any past date, with the citation and the git commit behind it. Your assistant answers from the corpus instead of from memory.

[MCP] [Corpus read-only] [Auth] [License: MIT] [Web]

Connect your AI client (Claude, ChatGPT, Cursor, VS Code, Gemini CLI…) to Legalize and ask about legislation in plain language. Every answer comes back with three things a model cannot invent:

• 📜 The text itself — the whole law or one whole article, never a truncated fragment.
• 🕰️ A date — not only the current wording, but the version that was on the books on the day you name.
• 🔗 A citation and a git SHA — the commit in the public corpus that holds those exact bytes, so the other side can check the quote.

One remote endpoint:

https://legalize.dev/mcp

Sign-in required. See it live at legalize.dev/mcp, which always shows the current coverage and allowance.

Quick connect

It is a remote server (Streamable HTTP, stateless). Nothing is installed: you hand the URL to your client, and the client walks you through the sign-in the first time it calls a tool.

One click, if yours is one of these:

[Add to Claude] [Add to Cursor] [Add to VS Code] [Add to ChatGPT]

The first three pre-fill the name and the address, then ask you to confirm it and sign in. ChatGPT opens its create-connector form — it takes no parameter for the server, so paste https://legalize.dev/mcp in yourself, with developer mode on under Advanced.

Claude.ai · Claude Desktop (Connectors)

Settings → Connectors → Add custom connector → paste https://legalize.dev/mcp.

Claude Code (CLI)

claude mcp add --transport http legalize https://legalize.dev/mcp

Cursor

Use the button above, or in ~/.cursor/mcp.json:

{  "mcpServers": {    "legalize": {      "url": "https://legalize.dev/mcp"    }  }}

VS Code (GitHub Copilot)

Use the button above, or in .vscode/mcp.json:

{  "servers": {    "legalize": {      "type": "http",      "url": "https://legalize.dev/mcp"    }  }}

ChatGPT

Settings → Connectors → Advanced → turn on developer mode, then create a connector and paste https://legalize.dev/mcp. There is no install link for this one: ChatGPT only deep-links to apps listed in its own directory, and custom connectors sit behind developer mode, on Plus or Pro.

Gemini CLI and other clients

{  "mcpServers": {    "legalize": {      "httpUrl": "https://legalize.dev/mcp"    }  }}

Any client that speaks remote MCP works. If yours only speaks stdio, bridge it:

npx mcp-remote https://legalize.dev/mcp

The tools

Nothing here can change a law. The corpus is read-only to the connector: no tool alters a text, a version or a history, because those come from the git repositories and this server has no way in. The full descriptions the model reads, with every argument and its type, are published live by the running server at /mcp/tools.json.

The rest manage your own subscriptions — the one question reading the corpus cannot answer, which is tell me when this changes. They are the only tools that write anything, what they write is your account's own subscription, and they need a paid plan.

One rule, two ways to receive it. A webhook posts every change to a server you run; a digest lists a day of them in your inbox:

The digest goes to the account's own address and there is no argument for another one. Not an omission: a free-text recipient would turn a connector into a way to send mail to somebody else, signed by our domain, on a model's say-so.

Narrow the subscription or you will stop reading it. The filters compose as AND, a rule that could never match — an unknown country, a law id that is not in the corpus — is refused rather than stored, and a text filter reaches one language: laws are written in their own, so proteccion de datos finds the Spanish act and not the Portuguese protecao de dados.

The ones marked ✎ are declared to clients with readOnlyHint: false, so a client that confirms before a write will confirm before these. A paid plan is needed to create one; pausing and deleting never are, on any plan, because the account that most needs to turn its deliveries off is the one whose plan has just ended. On a plan without the feature, creating answers a structured feature_not_available error and creates nothing — and nothing is delivered either, to an endpoint or to an inbox, until it is back. Neither delivery is instant: webhooks are signed and batched daily (the format and the verifier), and a digest is one mail a day — on a day when nothing matched, no mail at all.

Every tool returns the same envelope — data, citation, url, source, note — and every result links back to its page on legalize.dev. A tool-level failure is a successful call whose data is a structured error naming what to do next, so the model can correct itself instead of guessing.

Examples (ask your assistant)

• "What did article 348 bis of the Spanish Companies Act say in March 2023?"
• "Has the French Code du travail changed on this point since 2020? Show me the diff."
• "Which norms have amended this law, and when?"
• "How much of Latvian legislation does Legalize actually hold?"
• "Email me every morning when anything about data protection changes in Spain — in Spanish."

Authentication

Sign-in required; there is no anonymous access. Every call is tied to an account, and an unauthenticated request gets 401 with the WWW-Authenticate challenge that starts the OAuth flow.

Your client discovers the authorization server from https://legalize.dev/.well-known/oauth-protected-resource, registers itself dynamically, and sends you to sign in once in a browser. After that it holds the token and you never see the handshake again. No API key is pasted anywhere.

Limits

There is a free monthly allowance and a per-minute burst guard. Neither number is written here on purpose — they would go stale the day either changes, and a README that quietly lies about a limit is worse than one that points at it. Both are stated, live, on legalize.dev/mcp and legalize.dev/pricing.

What does not change: past the monthly allowance the connector answers quota_exceeded and stops until the month rolls over — nothing is charged and nothing is cut off silently. Every country is included in every tier.

Before you quote it

Most of the corpus is consolidated: amendments are folded into the text, so what you read is the law as it stands. Some of it is not. A text published as enacted comes back flagged, with the norms that amend it named, and never as the law in force — but the flag is only useful if you read it before pasting the quote into a brief.

Three more limits worth knowing:

• A date resolves to what was published on or before it, not to what was in force.
• Article boundaries are derived by matching headings in the text, not published as structure by the source. Quote the anchor, and check the boundary before relying on it.
• Counts are of what Legalize has ingested, not of what the official gazette has published. A gap in the corpus is not evidence that a norm does not exist.

A body is never truncated: a law too large to send whole comes back as its table of contents with instructions for asking again, because half an article reads exactly like a whole one.

For developers

Transport is Streamable HTTP, stateless. Every JSON-RPC method needs a token, initialize and tools/list included. So the first thing to check is the catalogue, which is served beside the endpoint as a plain GET and needs nothing:

curl -s https://legalize.dev/mcp/tools.json | jq '.tools[] | {name, readOnly}'

That is what a directory reads, and it is where readOnly per tool is published. The JSON-RPC endpoint itself answers 401, and that 401 is the handshake — its WWW-Authenticate header is what tells a client where the authorization server is:

curl -si -X POST https://legalize.dev/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_countries","arguments":{}}}' | head -20# 401 + WWW-Authenticate: Bearer ... resource_metadata="..."   ← correct: that is the handshake

Once signed in, the same call answers with the tool's payload.

What is behind the data

Legalize builds one public git repository per country: every law is a Markdown file, and every reform it holds is a dated commit. That is where the SHA in an answer comes from — it is a commit in a public repo, not an identifier minted for the reply.

Where a corpus starts later than the act it holds — a source that publishes its consolidated texts from 1996 onwards, say, for a code from 1885 — reform_history says so in history, and asking for a date before that is a plain "the corpus starts on X", never a retry.

Ask what the Spanish Companies Act said in March 2023 and the answer carries commit 3b9aea8d5 of legalize-dev/legalize-es:

git show 3b9aea8d5:es/BOE-A-2010-10544.md

returns that file: the text the connector hands back, under the YAML frontmatter the corpus keeps its metadata in. The connector reaches every country Legalize publishes — the live list, with the size of each corpus, is on legalize.dev and from the list_countries tool.

More

• 🌐 Web: legalize.dev — browse the corpus, free, no account.
• 🔌 This connector, online: legalize.dev/mcp
• 🧾 REST API: legalize.dev/api — the same data over HTTP.
• 💶 Pricing: legalize.dev/pricing
• 🛠️ Pipeline and corpus: github.com/legalize-dev/legalize — open source.

About Legalize

Legalize turns official gazettes into git: consolidated legislation as Markdown, one commit per reform, one repository per country. This repository documents its MCP connector — the surface an AI assistant talks to.

legalize.dev · MIT licence