Summary
Dutch court decisions from the judiciary's open data service, no API key: search the ECLI index by date, court, area of law and type, and read the full text and metadata of any published decision of the Supreme Court, Council of State, courts of appeal and district courts.
Guided setup
Connect Rechtspraak.nl Open Data to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Rechtspraak.nl Open Data in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Rechtspraak.nl Open Data
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Rechtspraak.nl Open Data, install it, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Rechtspraak.nl Open Data + Microsoft Copilot
Dutch court decisions from the judiciary's open data service, no API key: search the ECLI index by date, court, area of law and type, and read the full text and metadata of any published decision of the Supreme Court, Council of State, courts of appeal and district courts.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
None. This connector needs no account, API key or sign-in.
Step 1 — Get credentials
Setup: nothing to configure. Try rechtspraak_get_decision_metadata with ECLI:NL:RVS:2024:2.
What it can and cannot do
- It finds decisions by metadata: decision date, court, area of law, type, modification date, or a former LJN number. There is no full-text or keyword search in this API: to find decisions about a topic, narrow by court, area of law and period with
rechtspraak_search_decisions, read the summaries in the result, then open the promising ones. - With an ECLI in hand,
rechtspraak_get_decisionreturns the whole text andrechtspraak_get_decision_metadataonly the header data.
Where to start
rechtspraak_search_decisionswithdate_fromanddate_to(a range), optionallycourtandlegal_area. Addwith_text_onlyDOC, because many index entries have no published text.rechtspraak_list_courtsandrechtspraak_list_legal_areasgive the identifier URIs the filters need; pass them unchanged.rechtspraak_list_procedure_typesandrechtspraak_list_formal_relationsdecode fields of a decision.
ECLI: ECLI:NL:HR:2024:300 reads country NL, court code HR, year 2024, number 300. Common court codes: HR Supreme Court (Hoge Raad), PHR its Advocate General's office (conclusions), RVS Council of State, CRVB Central Appeals Tribunal, CBB Trade and Industry Appeals Tribunal, GH plus city for courts of appeal (GHAMS, GHARL, GHDHA, GHSHE), RB plus region for district courts (RBAMS, RBDHA, RBROT). Decisions before 2013 carry their old LJN as the number (ECLI:NL:HR:2013:BZ9225).
Reading the answers (XML converted to JSON; attributes sit next to the text, which is then under #text)
- Search:
feed.subtitleholds the total number of hits;feed.entryis the list (missing when there are none, a single object when there is one). Long summaries are cut off in the list; the full one is in the decision. - Decision:
open-rechtspraak.RDF.Descriptionis a list of two blocks, the first about the decision (creator, date, zaaknummer, procedure, subject, relation, references), the second about its web page. The text is underuitspraak(orconclusie), as sections andparalists in reading order. - Names of private persons are anonymised in the source ([appellant], [verweerder]).
Paging and limits: a search returns at most 1000 entries per call (max, default here 50); continue with offset. Results are ordered by modification date, not decision date. The service publishes no rate limit: keep the request rate moderate, and use the Council's bulk archives for whole-collection downloads.
Reuse: the decisions are public and free to reuse; cite the ECLI. Personal data that remains in a text falls under data protection law.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
Rechtspraak.nl Open Datatools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
rechtspraak_search_decisions | Search the Dutch judiciary's ECLI index (about 3.8 million decisions) by date, court, area of law and type. There is no keyword search: the… |
rechtspraak_get_decision | Get one decision by ECLI with its full text, parsed from XML to JSON under open-rechtspraak: RDF.Description (metadata: court in creator… |
rechtspraak_get_decision_metadata | Get only the metadata of a decision by ECLI, without the text: court (creator), decision date (date), publication date (issued), last… |
rechtspraak_list_courts | List every court and judicial body in the index (Instanties): Identifier (the URI for the court filter), Naam, Afkorting (the court code… |
rechtspraak_list_legal_areas | List the areas of law (Rechtsgebieden) as a two-level tree: Identifier (the URI for the legal_area filter) and Naam, with the sub-areas of… |
rechtspraak_list_procedure_types | List the procedure types (Proceduresoorten) that appear in decision metadata, such as first instance, appeal, cassation or interim relief… |
rechtspraak_list_formal_relations | List the kinds of formal relation between decisions (FormeleRelaties), such as appeal, cassation, referral or the opinion that belongs to a… |
Example prompts
- "Find decisions of the Hoge Raad in tax law from the last three months that have a published text."
- "Give me the full text of ECLI:NL:HR:2024:300 and summarise the ruling."
- "Which decisions of the Council of State on environmental permits were published in October?"
- "What are the court, date, case number and procedure of ECLI:NL:RVS:2024:2?"
- "List the court codes I can filter on, with their names."
FAQ
Do I need an account or an API key? No. The connector reads the Open Data service of the Dutch Council for the Judiciary with no account or key. The service publishes no rate limit, so keep the request rate moderate; for whole-collection downloads use the Council's bulk archives.
Can it search decisions by keyword? No. The API finds decisions by metadata only: decision date, court, area of law, type, modification date or a former LJN number. To find a topic the AI narrows by court, area of law and period, reads the summaries and opens the promising decisions. With an ECLI it returns the full text or only the metadata. Texts are in Dutch, and names of private persons are anonymised in the source.
Is it read-only, and can I reuse the decisions? Yes, every tool only reads and nothing installs switched off. The decisions are public and free to reuse; cite the ECLI. Personal data that remains in a text falls under data protection law.
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
Was this guide helpful?