JSON Contracts vs Texas Code
A side-by-side look at the JSON Contracts and Texas 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 Texas 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.
Choose Texas Code when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 35/100 · Fair | 41/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 | JSON_CONTRACTS_DIR | None listed |
| Verified owner |
Tools & capabilities
JSON Contracts tools
No tool names declared yet. Check the project README from the listing page.
Texas 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.
JSON Contracts
{
"mcpServers": {
"json-contracts": {
"command": "npx",
"args": [
"-y",
"json-contracts@latest"
],
"env": {
"JSON_CONTRACTS_DIR": "YOUR_JSON_CONTRACTS_DIR_HERE"
}
}
}
}
Texas Code
{
"mcpServers": {
"texas-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-texas-code"
]
}
}
}
Frequently asked questions
JSON Contracts is categorized under Legal and uses a local stdio subprocess. Texas Code belongs to Legal and uses a local stdio subprocess. Pick JSON Contracts for legal work and Texas 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. Texas Code 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 json-contracts and texas-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 35/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Texas Code has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.