JSON Contracts vs Kentucky Code
A side-by-side look at the JSON Contracts and Kentucky Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose JSON Contracts for legal work as a local process; choose Kentucky 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 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. - You want tools like
list_contracts, read_contract, get_json_contract.
Choose Kentucky 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.
- You want tools like
ky_statute, ky_search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 57/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | JSON_CONTRACTS_DIR | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 8 | 2 |
| Full listing | View JSON Contracts | View Kentucky Code |
Tools & capabilities
JSON Contracts tools 8
list_contractsList currently loaded JSON contracts.read_contractRead a loaded JSON contract.get_json_contractReturn schema, rules, examples, instructions, and input so the agent/model can produce JSON.get_edit_contractReturn schema, rules, current JSON, edit instructions, and input so the agent/model can edit existing JSON.validate_jsonValidate agent-produced JSON against a contract schema.get_repair_contractReturn schema, rules, previous invalid JSON, validation errors, and repair instructions.statusReturn json-contracts MCP server status and loaded contract metadata.reload_contractsRescan the JSON contracts directory and reload valid contracts.
Kentucky Code tools 2
ky_statuteGet the FULL TEXT of a section of the Kentucky Revised Statutes (KRS) — Kentucky state law — by citation. "507.020" is murder; "383.580" is the landlord security-deposit statute. Accepts natural forms: "507.020", "KRS 507.020", "§ 507.020". Returns the current statutory text, the catchline, the "Effective:" date, and the legislative "History:" (the Acts that enacted and amended it). Kentucky publishes the CURRENT text only — a prior (pre-amendment) version's text is not available online, only its existence; this tool says so rather than guessing. Keyless. Use for "what does KRS 507.020 say" or to check a Kentucky statute a case or contract relies on.ky_searchSearch the Kentucky Revised Statutes BY TOPIC or keyword rather than citation — "security deposit", "concealed carry", "DUI per se limit", "homicide". Real full-text search over the statutory body text, not just catchlines: a query like "landlord" surfaces KRS 383.580 ("Security deposits") even though that catchline contains neither word. Returns matching citations and catchlines; call ky_statute with a citation for the full text. Keyless.
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.
JSON Contracts
{
"mcpServers": {
"json-contracts": {
"command": "npx",
"args": [
"-y",
"json-contracts@latest"
],
"env": {
"JSON_CONTRACTS_DIR": "YOUR_JSON_CONTRACTS_DIR_HERE"
}
}
}
}
Kentucky Code
{
"mcpServers": {
"kentucky-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-kentucky-code"
]
}
}
}
Frequently asked questions
JSON Contracts is categorized under Legal and uses a local stdio subprocess. Kentucky Code belongs to Legal and uses a local stdio subprocess. Pick JSON Contracts for legal work and Kentucky 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.
JSON Contracts has no declared pricing — check the project's own site. Kentucky 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 json-contracts and kentucky-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, JSON Contracts has a quality signal of 57/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Kentucky Code has 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars.