Japan Law Search MCP Server

Full-text search of all current Japanese laws (official e-Gov data), down to exact article text. That is what the japan law search mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

This MCP server searches and retrieves the full text of current Japanese legislation — acts, cabinet orders, and ministerial ordinances — from the official e-Gov Laws API (Government of Japan). Built for legal-tech, compliance, HR, and contract-review AI agents working with Japanese law.

The tools it exposes

The server publishes 3 tools. What each one is for:

• search_laws — Full-text search across the body text of every current law (or search by law title). Returns matched snippets, law categories, promulgation dates
• get_law_structure — Table of contents for any law: chapters, sections, and article headings. Long statutes (e.g. the Civil Code with 1,000+ articles) are automatically
• get_law_article — Retrieve the exact text of any article. Accepts flexible references — 3, 第3条, 第三条の二, 3の2 — and normalizes kanji numerals automatically. Output

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Japan Law Search's toolset — search_laws, get_law_structure, get_law_article — is a fair guide to whether it matches your workflow. It is maintained by easakura; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Japan Law Search's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.