get_sections_batch — Vaquill MCP Tool Read-only
get_sections_batch
(get sections batch) is one of 27 tools on the
Vaquill
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_sections_batch from your client
- Claude Code Vaquill get_sections_batch run in your project directory
- Claude Desktop Vaquill get_sections_batch ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vaquill get_sections_batch ~/.cursor/mcp.json
- VS Code Vaquill get_sections_batch .vscode/mcp.json
- Zed Vaquill get_sections_batch ~/.config/zed/settings.json
- Windsurf Vaquill get_sections_batch ~/.codeium/windsurf/mcp_config.json
- Cline Vaquill get_sections_batch ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vaquill get_sections_batch ~/.gemini/settings.json
- Grok Vaquill get_sections_batch .mcp.json (in your project root)
- ChatGPT Vaquill get_sections_batch Settings → Connectors → Advanced → Developer mode
- Claude.ai Vaquill get_sections_batch Settings → Connectors → Add custom connector
- LangChain Vaquill get_sections_batch pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vaquill-mcp https://mcp.vaquill.ai/s/_
Other tools on this server
- count_statute_sections
- create_watch
- delete_watch
- fetch
- get_credit_balance
- get_pricing
- get_section_changes
- get_section_cited_by
- get_section_cross_state
- get_section_definitions
- get_section_neighbors
- get_us_statute_section
- get_us_statute_section_text
- get_watch_change_diff
- list_boards
- list_statute_divisions
- list_statutes_coverage
- list_watch_changes
- list_watch_deliveries
- list_watches
- resolve_statute_citation
- resolve_statute_citations_batch
- search
- search_us_statutes
- test_watch
- update_watch
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.