A side-by-side look at the Nexus Legal MCP and Fermat 360 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Nexus Legal MCP for legal work as a local process; choose Fermat 360 for legal. You can also run both side by side in one mcpServers block.
NEXUS_API_KEY.Rows where the two servers differ are marked.
| Spec | F Fermat 360 | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 51/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | OAuth 2.0 |
| Pricing | Paid service | Paid service |
| Required env vars | NEXUS_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| 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 Fermat 360 |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"djtellado-nexus-legal-mcp": {
"command": "npx",
"args": [
"-y",
"@nexus-legal/mcp"
],
"env": {
"NEXUS_API_KEY": "YOUR_NEXUS_API_KEY_HERE"
}
}
}
}
No confirmed install command for Fermat 360 yet — follow the setup steps linked from its listing page rather than a guessed package name.