local_rules_browse — Indiana Code MCP Tool
local_rules_browse
(local rules browse) is one of 26 tools on the
Indiana Code
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call local_rules_browse from your client
- Claude Code Indiana Code local_rules_browse run in your project directory
- Claude Desktop Indiana Code local_rules_browse ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Indiana Code local_rules_browse ~/.cursor/mcp.json
- VS Code Indiana Code local_rules_browse .vscode/mcp.json
- Zed Indiana Code local_rules_browse ~/.config/zed/settings.json
- Windsurf Indiana Code local_rules_browse ~/.codeium/windsurf/mcp_config.json
- Cline Indiana Code local_rules_browse ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Indiana Code local_rules_browse ~/.gemini/settings.json
- Grok Indiana Code local_rules_browse .mcp.json (in your project root)
- ChatGPT Indiana Code local_rules_browse Settings → Connectors → Advanced → Developer mode
- Claude.ai Indiana Code local_rules_browse Settings → Connectors → Add custom connector
- LangChain Indiana Code local_rules_browse pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http indiana-code https://mcp.openindianalaw.org/mcp
Other tools on this server
- corpus_manifest
- ic_search
- ic_resolve_citation
- ic_get_section
- ic_get_versions
- ic_browse
- ic_get_act
- ic_list_companion
- ic_search_companion
- ic_get_companion
- case_search
- case_transcription_search
- case_get
- ic_cases_citing
- cases_construing
- cases_citing_case
- cases_cited_in
- cases_citing_court
- iac_search
- iac_resolve_citation
- iac_get_section
- iac_browse
- local_rules_search
- judicial_officers_browse
- judicial_officers_search
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.