in_code_section — Indiana Code MCP Tool
in_code_section
(in code section) is one of 38 tools on the
Indiana Code
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call in_code_section from your client
- Claude Code Indiana Code in_code_section run in your project directory
- Claude Desktop Indiana Code in_code_section ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Indiana Code in_code_section ~/.cursor/mcp.json
- VS Code Indiana Code in_code_section .vscode/mcp.json
- Zed Indiana Code in_code_section ~/.config/zed/settings.json
- Windsurf Indiana Code in_code_section ~/.codeium/windsurf/mcp_config.json
- Cline Indiana Code in_code_section ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Indiana Code in_code_section ~/.gemini/settings.json
- Grok Indiana Code in_code_section .mcp.json (in your project root)
- ChatGPT Indiana Code in_code_section Settings → Connectors → Advanced → Developer mode
- Claude.ai Indiana Code in_code_section Settings → Connectors → Add custom connector
- LangChain Indiana Code in_code_section pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http indiana-code https://gateway.pipeworx.io/indiana-code/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- in_code_search
This list was read from the server itself, by connecting to it and calling tools/list on 7 October 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.