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