Fermat 360 vs Nexus Legal MCP
A side-by-side look at the Fermat 360 and Nexus Legal MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
Fermat 360LegalDutch legal AI for law firms: answers from Dutch case law, legislation and EU law, with citations.36FairAuth: oauth 2.0Verdict: choose Fermat 360 for legal work; choose Nexus Legal MCP for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
FChoose Fermat 360 when
- You need dedicated capabilities in the Legal domain.
- Its auth model fits you: OAuth 2.0.
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 | F Fermat 360 | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 36/100 · Fair | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Paid service | Paid service |
| Required env vars | None listed | NEXUS_API_KEY |
Tools & capabilities
Fermat 360 tools
No tool names declared yet. Check the project README from the listing page.
Nexus Legal MCP 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.
Fermat 360
No confirmed install command for Fermat 360 yet — follow the setup steps linked from its listing page rather than a guessed package name.
Nexus Legal MCP
{
"mcpServers": {
"djtellado-nexus-legal-mcp": {
"command": "npx",
"args": [
"-y",
"@nexus-legal/mcp"
],
"env": {
"NEXUS_API_KEY": "YOUR_NEXUS_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Fermat 360 is categorized under Legal and uses an install path we have not confirmed yet. Nexus Legal MCP belongs to Legal and uses a local stdio subprocess. Pick Fermat 360 for legal work and Nexus Legal MCP 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. Fermat 360 has no confirmed install command yet — follow its own setup instructions.
Fermat 360 is listed as a paid service. Auth: oauth 2.0. Nexus Legal MCP is listed as a paid service. Auth: api key required. 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 fermat-360 and djtellado-nexus-legal-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fermat 360 has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Nexus Legal MCP has 51/100 (Good) with 3 views, 0 installs and 2 GitHub stars.