Law.AI — Lawyer Search vs Swiss Case Law | AllMCPs
Side-by-Side Model Context Protocol Comparison
Law.AI — Lawyer Search vs Swiss Case Law
In-depth architectural comparison of the Law.AI — Lawyer Search and Swiss Case 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
Law.AI — Lawyer Search
Legal · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Swiss Case Law
Legal · Remote HTTP/SSE
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Law.AI — Lawyer Search if you need specialized Legal tools running via a local process. Choose Swiss Case 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?
Choose Law.AI — Lawyer Search when:
You need dedicated capabilities in the Legal domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
Search the Law.AI directory of 537,000+ verified lawyer profiles. Filter by practice area, state, city, and bar status. Returns ranked results with claimed/verified profiles first.
get_lawyer_profile
Get the full profile of a specific lawyer by their Law.AI ID. Returns detailed information including bio, education, bar admissions, practice areas, and contact info (for claimed profiles).
find_lawyer_by_name
Look up a specific lawyer by name. Useful for verifying if a lawyer exists and is properly licensed. Handles common names with disambiguation by location.
get_practice_areas
List all practice areas available in the Law.AI directory with lawyer counts. Useful for discovering what types of lawyers are available.
get_jurisdictions
List US states and jurisdictions with lawyer counts. Shows where Law.AI has coverage.
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).
Law.AI — Lawyer Search is categorized under Legal and uses a local stdio subprocess. In contrast, Swiss Case Law belongs to Legal using remote streaming HTTP/SSE transport. Select Law.AI — Lawyer Search when you need capabilities focused on legal and Swiss Case Law when you require tools for legal.
Describe a legal issue in plain English and get matched with relevant lawyers. The tool classifies the issue into practice areas and returns ranked lawyer matches based on relevance, credentials, and location.
get_legal_cost_estimate
Get estimated legal costs for a type of legal issue. Returns fee ranges by billing structure (hourly, flat fee, contingency), adjusted for case complexity and region. Complexity is the primary cost driver.
Swiss Case Law Tools (21)
search_decisions
Full-text search with filters (court, canton, language, date range, chamber)
get_decision
Fetch a single decision by docket number or ID. Includes citation graph counts (cited by / cites).
list_courts
List all courts with decision counts
get_statistics
Aggregate stats by court, canton, or year
find_citations
Show what a decision cites and what cites it, with confidence scores
find_appeal_chain
Trace the appeal chain (Instanzenzug) — prior and subsequent instances
find_leading_cases
Find the most-cited decisions for a topic or statute
analyze_legal_trend
Year-by-year decision counts for a statute or topic
draft_mock_decision
Build a research-only mock decision outline from facts, grounded in caselaw + statute references; asks clarification questions before conclusion
get_case_brief
Structured brief for any case — regeste, key Erwägungen, cited statutes, and citation authority
get_doctrine
Statute article or legal concept → ranked leading cases + doctrine timeline
generate_exam_question
Legal topic → real BGE fact pattern with hidden analysis for Fallbearbeitung practice