ContractGate vs JSON Contracts
A side-by-side look at the ContractGate and JSON Contracts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ContractGate for legal work as a local process; choose JSON Contracts 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 ContractGate when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CONTRACTGATE_API_KEY.
Choose JSON Contracts when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
JSON_CONTRACTS_DIR.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 40/100 · Fair | 35/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CONTRACTGATE_API_KEY | JSON_CONTRACTS_DIR |
| Verified owner |
Tools & capabilities
ContractGate tools
No tool names declared yet. Check the project README from the listing page.
JSON Contracts 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.
ContractGate
{
"mcpServers": {
"contractgate": {
"command": "npx",
"args": [
"-y",
"@nightmoose/contractgate-mcp-server"
],
"env": {
"CONTRACTGATE_API_KEY": "YOUR_CONTRACTGATE_API_KEY_HERE"
}
}
}
}
JSON Contracts
{
"mcpServers": {
"json-contracts": {
"command": "npx",
"args": [
"-y",
"json-contracts@latest"
],
"env": {
"JSON_CONTRACTS_DIR": "YOUR_JSON_CONTRACTS_DIR_HERE"
}
}
}
}
Frequently asked questions
ContractGate is categorized under Legal and uses a local stdio subprocess. JSON Contracts belongs to Legal and uses a local stdio subprocess. Pick ContractGate for legal work and JSON Contracts 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.
ContractGate has no declared pricing — check the project's own site. JSON Contracts 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 contractgate and json-contracts as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ContractGate has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 4 GitHub stars. JSON Contracts has 35/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.