Indiana Code vs South Dakota Code
A side-by-side look at the Indiana Code and South Dakota Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Indiana Code for legal work as a local process; choose South Dakota 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 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.
- You want tools like
in_code_section, in_code_search.
Choose South Dakota 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.
- You want tools like
sd_statute, sd_search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 59/100 · Good | 60/100 · Good |
| 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 | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 2 | 2 |
| Full listing | View Indiana Code | View South Dakota Code |
Tools & capabilities
Indiana Code tools 2
in_code_sectionGet the FULL TEXT of a section of the Indiana Code — Indiana state law — by citation, plus when it was added or amended. "IC 9-21-5-5" is an oversized-vehicle speed limit (traffic, Title 9); "IC 32-31-3-6" defines "rent" in the landlord-tenant chapter (Title 32). An ARTICLE ("IC 24-16") or CHAPTER ("IC 24-16-4") reference also works — it returns that group's own section list (citation + heading for each) instead of failing, so you can pick the right one and call this again for its full text. Pass `year` (e.g. 2020) to retrieve a historical annual edition instead of the current code — Indiana publishes a separate archived edition per year. Keyless. Use for "what does Indiana Code 9-21-5-5 say" or to check an Indiana statute a lease, ticket, or case relies on.in_code_searchSearch the Indiana Code BY TOPIC or keyword rather than citation — "traffic oversized vehicle permit", "landlord retaliatory eviction", "concealed handgun license". Returns ranked sections with their citations across all 37 Indiana Code titles; use in_code_section afterward for the full text of one. Full-text search, so it answers questions no citation lookup can. Keyless.
South Dakota Code tools 2
sd_statuteGet the FULL TEXT of a section of the South Dakota Codified Laws — South Dakota state law — by citation. "22-16-4" is murder in the first degree; "43-32-13" covers a landlord's notice of lease modification. Accepts natural forms: "22-16-4", "SDCL 22-16-4", "§ 22-16-4". Returns the current statutory text, the official catchline, and — when present — the "Source:" line listing every session law that enacted or amended the section (split out into `history`). South Dakota publishes the CURRENT text only, no per-year historical archive, so a prior (pre-amendment) version of the text is not available; this tool says so rather than guessing. Keyless. Use for "what does SDCL 22-16-4 say" or to check a South Dakota statute a case or lease relies on.sd_searchSearch the South Dakota Codified Laws BY TOPIC or keyword rather than citation — "landlord security deposit", "concealed pistol permit", "homicide". Matches against the Legislature's own official section and chapter CATCHLINES across the whole Code (not full statutory prose — South Dakota does not publish a full-text search of Code section text, verified live), e.g. "landlord" surfaces sections like "Modification of lease--Written notice by landlord" even in a chapter not named for landlords. Returns matching citations and catchlines; call sd_statute with a citation for the full text. Keyless.
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"
]
}
}
}
South Dakota Code
{
"mcpServers": {
"south-dakota-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-south-dakota-code"
]
}
}
}
Frequently asked questions
Indiana Code is categorized under Legal and uses a local stdio subprocess. South Dakota Code belongs to Legal and uses a local stdio subprocess. Pick Indiana Code for legal work and South Dakota 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. South Dakota 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 south-dakota-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 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. South Dakota Code has 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars.