code_lookup_sections — Georgia Commons MCP Tool
code_lookup_sections
(code lookup sections) is one of 23 tools on the
Georgia Commons
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call code_lookup_sections from your client
- Claude Code Georgia Commons code_lookup_sections run in your project directory
- Claude Desktop Georgia Commons code_lookup_sections ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Georgia Commons code_lookup_sections ~/.cursor/mcp.json
- VS Code Georgia Commons code_lookup_sections .vscode/mcp.json
- Zed Georgia Commons code_lookup_sections ~/.config/zed/settings.json
- Windsurf Georgia Commons code_lookup_sections ~/.codeium/windsurf/mcp_config.json
- Cline Georgia Commons code_lookup_sections ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Georgia Commons code_lookup_sections ~/.gemini/settings.json
- Grok Georgia Commons code_lookup_sections .mcp.json (in your project root)
- ChatGPT Georgia Commons code_lookup_sections Settings → Connectors → Advanced → Developer mode
- Claude.ai Georgia Commons code_lookup_sections Settings → Connectors → Add custom connector
- LangChain Georgia Commons code_lookup_sections pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http georgia-commons https://mcp.georgiacommons.org/mcpOther tools on this server
- describe_site
- get_coverage
- search
- fetch
- verify_quote
- opinions_lookup
- opinions_get_text
- opinions_list
- opinions_search
- bills_lookup
- bills_get_text
- bills_list
- bills_search
- code_describe_structure
- code_lookup_section
- code_browse
- code_get_chapter
- code_search
- code_find_chapter
- code_find_act
- constitution_lookup
- constitution_browse
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.