Oklahoma Code vs Alabama Code
A side-by-side look at the Oklahoma Code and Alabama Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Alabama CodeLegal · Local subprocess (stdio)Code of Alabama 1975 — state statutes by citation and by topic.40FairAuth: no auth requiredVerdict: choose Oklahoma Code for legal work as a local process; choose Alabama 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 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.
AChoose Alabama 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 | A Alabama Code | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 37/100 · Fair | 40/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
Oklahoma Code tools
No tool names declared yet. Check the project README from the listing page.
Alabama 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.
Oklahoma Code
{
"mcpServers": {
"oklahoma-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-oklahoma-code"
]
}
}
}
Alabama Code
{
"mcpServers": {
"alabama-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-alabama-code"
]
}
}
}
Frequently asked questions
Oklahoma Code is categorized under Legal and uses a local stdio subprocess. Alabama Code belongs to Legal and uses a local stdio subprocess. Pick Oklahoma Code for legal work and Alabama 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.
Oklahoma Code is listed as free. Auth: no auth required. Alabama 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 oklahoma-code and alabama-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Oklahoma Code has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Alabama Code has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.