Contract Parser vs North Dakota Code
A side-by-side look at the Contract Parser 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 Contract Parser for legal work over a hosted endpoint; 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 Contract Parser when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
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 | 39/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Contract Parser | View North Dakota Code |
Tools & capabilities
Contract Parser 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.
Contract Parser
{
"mcpServers": {
"document-to-json-pdf-invoice-statement-contract-parser": {
"url": "https://mcp.apify.com/?actors=opportunity-biz/document-to-json-mcp"
}
}
}
North Dakota Code
{
"mcpServers": {
"north-dakota-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-north-dakota-code"
]
}
}
}
Frequently asked questions
Contract Parser is categorized under Legal and uses a remote HTTP/SSE transport. North Dakota Code belongs to Legal and uses a local stdio subprocess. Pick Contract Parser 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.
Contract Parser has no declared pricing — check the project's own site. 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 document-to-json-pdf-invoice-statement-contract-parser and north-dakota-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Contract Parser has a quality signal of 39/100 (Fair) with 2 views, 0 installs and 8 GitHub stars. North Dakota Code has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.