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