A side-by-side look at the Court Records MCP and LegalSearch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Court Records MCP for legal work over a hosted endpoint; choose LegalSearch for legal over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
C
Choose Court Records MCP when
You need dedicated capabilities in the Legal domain.
No tool names declared yet. Check the project README from the listing page.
LegalSearch 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.
Court Records MCP is categorized under Legal and uses a remote HTTP/SSE transport. LegalSearch belongs to Legal and uses a remote HTTP/SSE transport. Pick Court Records MCP for legal work and LegalSearch 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.
Court Records MCP has no declared pricing — check the project's own site. LegalSearch 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 court-records-mcp and legalsearch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Court Records MCP has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. LegalSearch has 36/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.