A side-by-side look at the Kentucky Code and Wisconsin Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kentucky Code for legal work as a local process; choose Wisconsin Code for legal as a local process. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | K Kentucky 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 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"kentucky-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-kentucky-code"
]
}
}
}
{
"mcpServers": {
"wisconsin-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-wisconsin-code"
]
}
}
}
| Community listing |
| GitHub stars | 0 | 0 |
|---|
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
|---|
| Tools | Not listed | Not listed |
|---|
| Full listing | View Kentucky Code | View Wisconsin Code |
|---|