rechercher_dans_texte_legalLABSCO SUMMARY
Grounded in the official texts, which is exactly where a model asked about French law otherwise invents.
Article numbers that look right and are not are the characteristic failure here, and every answer through these tools is anchored to a Legifrance lookup instead. Nothing is cached, so each question is a live query. The corpora stop at statutes, codes and judicial case law — the other Legifrance collections are not covered yet.
What it is
An experimental MCP server over the Legifrance API, covering three French legal corpora: statutes and regulations, the articles of the legal codes, and judicial case law.
What you get
- rechercher_dans_texte_legal — search inside a named statute or regulation by keywords or article number, choosing which field to search and how the terms combine
- rechercher_code — search the articles of a named French code, with sorting, field selection and an option to retrieve every result
- rechercher_jurisprudence_judiciaire — search judicial case law by terms or case number, filtered by court, by whether the decision was published in the bulletin, and by which response fields to return
- A packaged prompt, agent_juridique_expert, which sets up a legal assistant that cites its sources, works step by step and links back to the official texts
Requirements
Python and a local checkout — the server is started from the repository. It needs an API key for the maintainer's Legifrance gateway, requested from him directly, placed in a local environment file alongside the gateway address.
Setup effort
One command plus a key — pip install git+https://github.com/rdassignies/mcp-server-legifrance.git, then supply credentials
USE CASES
01
Finding a specific article of a statute
Search inside the named text by article number rather than hunting through the consolidated version.
02
Writing a summary of how a code treats a topic
Search the code's articles by subject and get the actual text back to work from.
03
Surveying recent case law on a question
Search the judicial decisions by topic, filtered to the courts and publication status you care about.
04
Working outward from a decision you already have
Find the judgment by case number, extract the articles it relies on, then look those up in the codes.
3 tools
Listed in project docs. Your client may show a different list.
rechercher_coderechercher_jurisprudence_judiciaireBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation. agent_juridique_expert is a prompt, not a tool. All three tools read, and other Legifrance collections are not implemented yet.
Requires
- Python 3.9+
- DASSIGNIES_API_KEY in your environment
- DASSIGNIES_API_URL in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
Créer et activer un environnement virtuel: python -m venv venv puis source venv/bin/activate (ou uv venv .venv / source .venv/bin/activate)
Installer: pip install git+https://github.com/rdassignies/mcp-server-legifrance.git (ou uv pip install git+https://github.com/rdassignies/mcp-server-legifrance.git)
Créer un fichier .env à la racine avec DASSIGNIES_API_KEY et DASSIGNIES_API_URL
Ajouter le bloc de configuration ci-dessus au fichier de configuration Claude Desktop, puis démarrer Claude Desktop
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"legifrance": {
"command": "<YOUR_PATH_TO_REP>/mcp-server-legifrance/venv/bin/python",
"args": [
"<YOUR_PATH_TO_REP>/mcp-server-legifrance/src/server.py"
]
}
}
}The configuration on this page does not set DASSIGNIES_API_KEY and DASSIGNIES_API_URL; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
