legalize-kr MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEGALIZE_KR_ROOT | Yes | Absolute path to the legalize-kr repository root (including kr/) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kr_read_fileB | 워킹 트리에서 kr/{lawDir}/{fileName} 전문을 UTF-8로 읽습니다 (README의 cat 예시와 동일). |
| kr_list_lawsA | kr/ 직계 하위 법령 디렉터리 이름을 정렬해 반환합니다. |
| kr_searchA | kr/**/*.md에서 문자열을 검색합니다 (README의 grep -r과 유사). ripgrep이 있으면 사용합니다. |
| kr_git_logB | 지정한 법령 경로에 대한 git log를 반환합니다 (README의 git log -- kr/.../). |
| kr_diffA | 동일 법령 폴더 안 두 Markdown 파일에 대해 git diff를 실행합니다 (README의 diff 예시). |
| kr_file_at_dateB | git log -1 --before=날짜로 해당 시점 커밋을 찾고, 선택적으로 git show로 당시 본문을 가져옵니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation: reading current files, listing law directories, diffing files, searching, viewing git history, and retrieving historical versions. The only slight overlap between kr_read_file and kr_file_at_date is clearly differentiated by temporal focus.
All tools share the 'kr_' prefix, and most follow a verb_noun pattern (read_file, list_laws, git_log, file_at_date). However, kr_diff and kr_search are verb-only, creating a minor inconsistency in naming style.
With 6 tools, the set is well-scoped for a legal document browsing server. Each tool serves a clear purpose without unnecessary redundancy, fitting comfortably within the ideal 3-15 range.
The server covers core read-only workflows: discovering laws, reading current and historical content, searching, diffing, and viewing git history. A notable gap is the lack of a tool to list individual files within a law directory, which prevents agents from enumerating files without guessing.