Nexus Legal MCP vs Site
A side-by-side look at the Nexus Legal MCP and Site MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SiteLegalMiCA Requirements: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not...37FairAuth: not declaredVerdict: choose Nexus Legal MCP for legal work as a local process; choose Site for legal. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Nexus Legal 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:
NEXUS_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Site | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 55/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | NEXUS_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Nexus Legal MCP | View Site |
Tools & capabilities
Nexus Legal MCP tools
No tool names declared yet. Check the project README from the listing page.
Site 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.
Nexus Legal MCP
{
"mcpServers": {
"djtellado-nexus-legal-mcp": {
"command": "npx",
"args": [
"-y",
"@nexus-legal/mcp"
],
"env": {
"NEXUS_API_KEY": "YOUR_NEXUS_API_KEY_HERE"
}
}
}
}
Site
No confirmed install command for Site yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Nexus Legal MCP is categorized under Legal and uses a local stdio subprocess. Site belongs to Legal and uses an install path we have not confirmed yet. Pick Nexus Legal MCP for legal work and Site 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. Site has no confirmed install command yet — follow its own setup instructions.
Nexus Legal MCP is listed as a paid service. Auth: api key required. Site 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 djtellado-nexus-legal-mcp and site-176 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Nexus Legal MCP has a quality signal of 55/100 (Good) with 3 views, 0 installs and 2 GitHub stars. Site has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.