Indiana Code vs Oklahoma Code
A side-by-side look at the Indiana Code and Oklahoma Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
I
Indiana CodeLegal · Local subprocess (stdio)Indiana Code — state statutes by citation, plus topic search and40FairAuth: no auth requiredVerdict: choose Indiana Code for legal work as a local process; choose Oklahoma 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?
IChoose Indiana 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.
Choose Oklahoma 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 | I Indiana Code | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 40/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Indiana Code tools
No tool names declared yet. Check the project README from the listing page.
Oklahoma 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.
Indiana Code
{
"mcpServers": {
"indiana-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-indiana-code"
]
}
}
}
Oklahoma Code
{
"mcpServers": {
"oklahoma-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-oklahoma-code"
]
}
}
}
Frequently asked questions
Indiana Code is categorized under Legal and uses a local stdio subprocess. Oklahoma Code belongs to Legal and uses a local stdio subprocess. Pick Indiana Code for legal work and Oklahoma 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.
Indiana Code has no declared pricing — check the project's own site. Auth: no auth required. Oklahoma 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 indiana-code and oklahoma-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Indiana Code has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Oklahoma Code has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.