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