Kansas Code vs Oregon Code
A side-by-side look at the Kansas Code and Oregon Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kansas Code for legal work as a local process; choose Oregon 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 Kansas Code when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
Choose Oregon 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 | 43/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 | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Kansas Code tools
No tool names declared yet. Check the project README from the listing page.
Oregon 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.
Kansas Code
{
"mcpServers": {
"kansas-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-kansas-code"
]
}
}
}
Oregon Code
{
"mcpServers": {
"oregon-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-oregon-code"
]
}
}
}
Frequently asked questions
Kansas Code is categorized under Legal and uses a local stdio subprocess. Oregon Code belongs to Legal and uses a local stdio subprocess. Pick Kansas Code for legal work and Oregon 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.
Kansas Code has no declared pricing — check the project's own site. Oregon 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 kansas-code and oregon-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kansas Code has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Oregon Code has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.