Nexus Legal MCP vs North Dakota Code
A side-by-side look at the Nexus Legal MCP and North Dakota Code 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 North Dakota Code for legal as a local process. 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.
Choose North Dakota Code when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 56/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Paid service | Free |
| Required env vars | NEXUS_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Nexus Legal MCP | View North Dakota Code |
Tools & capabilities
Nexus Legal MCP tools
No tool names declared yet. Check the project README from the listing page.
North Dakota Code 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"
}
}
}
}
North Dakota Code
{
"mcpServers": {
"north-dakota-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-north-dakota-code"
]
}
}
}
Frequently asked questions
Nexus Legal MCP is categorized under Legal and uses a local stdio subprocess. North Dakota Code belongs to Legal and uses a local stdio subprocess. Pick Nexus Legal MCP for legal work and North Dakota Code 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.
Nexus Legal MCP is listed as a paid service. Auth: api key required. North Dakota Code is listed as free. Auth: no auth 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 djtellado-nexus-legal-mcp and north-dakota-code 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 56/100 (Good) with 4 views, 0 installs and 2 GitHub stars. North Dakota Code has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.