Side-by-Side Model Context Protocol Comparison
Corpus vs Corpus Law
In-depth architectural comparison of the Corpus and Corpus Law MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Corpus
Legal · Local stdio
Quality: 25/100 (Emerging) | Auth: No auth required
Corpus Law
Legal · Remote HTTP/SSE
Quality: 42/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Corpus if you need specialized Legal tools running via a local process. Choose Corpus Law if your workspace requires Legal integration with remote web transport. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
C
Choose Corpus when:
- You need dedicated capabilities in the Legal domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
C
Choose Corpus Law when:
- You need dedicated capabilities in the Legal domain.
- You prefer remote streaming HTTP/SSE transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
Feature & Specification Comparison
Tools & Capabilities Breakdown
Corpus Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Corpus Law Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Corpus Configuration
Corpus Law Configuration