# Indiana Code [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/pipeworx-io/mcp-indiana-code  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/indiana-code

## Description
Indiana Code — state statutes by citation, plus topic search and

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "indiana-code": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-indiana-code"]
  }
}
```

## Documentation

## What Indiana Code does

The Indiana Code MCP server exposes Indiana statutes from the Indiana General Assembly’s official site at iga.in.gov. It covers the 37 Indiana Code titles represented as separate source documents, including 77,780 sections in the 2026 code. Title 7 is folded into Title 7.1 and does not have separate content. Titles 17, 18, and 19 are retained as repealed, zero-section results rather than being treated as missing.

The server belongs in the Legal category and supports two main ways to find material:

- Resolve a citation such as `9-21-5-5` or `32-31-3-6`.
- Search statute text by a subject such as landlord retaliation or oversized vehicle permits.

Citation results include the section text and a separate `history` field for trailing “As added by” or “Amended by” notes, as well as pre-recodification citation lines when present.

## How it works

`in_code_section` locates a citation inside a title document and extracts the matching section boundary. The source stores one HTML document per title and year, so the lookup can handle titles, articles, chapters, and sections at different levels in the hierarchy.

For the current code, the server checks a prefetched title bundle first and makes a live request when that bundle is unavailable. Supplying a different year bypasses the current bundle and retrieves the requested historical edition from the source site. Available years vary by title; a year without archived content returns `year_or_title_not_found` rather than assuming a universal earliest year.

`in_code_search` uses full-text search backed by an FTS5 shard. Search results provide a citation and heading; call `in_code_section` with the returned citation to obtain the complete section text.

## Setup and configuration

The Indiana Code MCP server can be connected through the Pipeworx streamable HTTP endpoint:

```json
{
  "mcpServers": {
    "indiana-code": {
      "url": "https://gateway.pipeworx.io/indiana-code/mcp"
    }
  }
}
```

It also runs locally as a stdio package without a Pipeworx account:

```json
{
  "mcpServers": {
    "indiana-code": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-indiana-code"]
    }
  }
}
```

The gateway endpoint adds shared Pipeworx meta-tools, while the standalone process exposes only this pack’s tools. The gateway also supports direct HTTP calls through `/v1/tools/in_code_section` and other tool endpoints. No account is needed for the first gateway calls according to the supplied documentation.

## Tools and capabilities

The Indiana Code MCP server provides:

- Citation-based section lookup with `in_code_section`.
- Topic and full-text search with `in_code_search`.
- Historical lookups by passing a year to section retrieval.
- Separate amendment and recodification history data.
- Current-code coverage across 37 Indiana Code title documents.

The source requires a browser-shaped User-Agent for direct retrieval; the packaged server handles this source-access requirement. Refreshing the prefetched data is a manual operation using `node scripts/ingest-indiana-statutes.mjs`; no automatic refresh schedule is wired in.

## Limitations and notes

This is an independent, unofficial integration and is not affiliated with or endorsed by the Indiana General Assembly. Historical availability differs by title, and a requested year may not exist. The source provides title-sized documents rather than one remote document per section, which affects retrieval implementation but not the section-level tool result.

The gateway pack endpoint lists shared routing and memory tools in addition to the Indiana-specific tools. Use the standalone package when only Indiana Code tools are wanted, or use `ask_pipeworx` through the gateway to ask questions in plain language. The supplied material does not describe a legal-advice function, so results should be treated as sourced statute data rather than legal advice.

_Full upstream README: https://allmcps.com/mcp/indiana-code/readme_