Korean Law MCP vs Obsidian Regulatory MCP
A side-by-side look at the Korean Law MCP and Obsidian Regulatory MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Korean Law MCP for legal work as a local process; choose Obsidian Regulatory MCP for legal over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Korean Law MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
LAW_OC, LAW_API_PROTOCOL.
Choose Obsidian Regulatory MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 55/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | LAW_OCLAW_API_PROTOCOL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,773 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Korean Law MCP | View Obsidian Regulatory MCP |
Tools & capabilities
Korean Law MCP tools
No tool names declared yet. Check the project README from the listing page.
Obsidian Regulatory MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Korean Law MCP
{
"mcpServers": {
"korean-law-mcp": {
"command": "npx",
"args": [
"-y",
"--ignore-scripts",
"--omit=optional",
"korean-law-mcp"
],
"env": {
"LAW_OC": "YOUR_LAW_OC_HERE",
"LAW_API_PROTOCOL": "YOUR_LAW_API_PROTOCOL_HERE"
}
}
}
}
Obsidian Regulatory MCP
{
"mcpServers": {
"obsidian-regulatory-mcp": {
"url": "https://obsidianri.com/mcp"
}
}
}
Frequently asked questions
Korean Law MCP is categorized under Legal and uses a local stdio subprocess. Obsidian Regulatory MCP belongs to Legal and uses a remote HTTP/SSE transport. Pick Korean Law MCP for legal work and Obsidian Regulatory MCP for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Korean Law MCP has no declared pricing — check the project's own site. Auth: api key required. Obsidian Regulatory MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add korean-law-mcp and obsidian-regulatory-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Korean Law MCP has a quality signal of 55/100 (Good) with 3 views, 0 installs and 2,773 GitHub stars. Obsidian Regulatory MCP has 37/100 (Fair) with 3 views, 0 installs and 0 GitHub stars.