Kentucky Code vs New Mexico Code
A side-by-side look at the Kentucky Code and New Mexico Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
K
Kentucky CodeLegal · Local subprocess (stdio)Kentucky Revised Statutes (KRS) — state statutes by citation and by topic.41FairAuth: no auth requiredN
New Mexico CodeLegal · Local subprocess (stdio)New Mexico Statutes Annotated 1978 (NMSA 1978) — section lookup, chapter41FairAuth: no auth requiredVerdict: choose Kentucky Code for legal work as a local process; choose New Mexico 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?
KChoose 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.
NChoose New Mexico 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 | K Kentucky Code | N New Mexico Code |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 41/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Kentucky Code tools
No tool names declared yet. Check the project README from the listing page.
New Mexico 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.
Kentucky Code
{
"mcpServers": {
"kentucky-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-kentucky-code"
]
}
}
}
New Mexico Code
{
"mcpServers": {
"new-mexico-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-new-mexico-code"
]
}
}
}
Frequently asked questions
Kentucky Code is categorized under Legal and uses a local stdio subprocess. New Mexico Code belongs to Legal and uses a local stdio subprocess. Pick Kentucky Code for legal work and New Mexico 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.
Kentucky Code is listed as free. Auth: no auth required. New Mexico 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 kentucky-code and new-mexico-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kentucky Code has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. New Mexico Code has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.