build_legislative_evidence_packet — bill commons MCP Tool
build_legislative_evidence_packet
(build legislative evidence packet) is one of 11 tools on the
bill commons
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call build_legislative_evidence_packet from your client
- Claude Code bill commons build_legislative_evidence_packet run in your project directory
- Claude Desktop bill commons build_legislative_evidence_packet ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor bill commons build_legislative_evidence_packet ~/.cursor/mcp.json
- VS Code bill commons build_legislative_evidence_packet .vscode/mcp.json
- Zed bill commons build_legislative_evidence_packet ~/.config/zed/settings.json
- Windsurf bill commons build_legislative_evidence_packet ~/.codeium/windsurf/mcp_config.json
- Cline bill commons build_legislative_evidence_packet ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI bill commons build_legislative_evidence_packet ~/.gemini/settings.json
- Grok bill commons build_legislative_evidence_packet .mcp.json (in your project root)
- ChatGPT bill commons build_legislative_evidence_packet Settings → Connectors → Advanced → Developer mode
- Claude.ai bill commons build_legislative_evidence_packet Settings → Connectors → Add custom connector
- LangChain bill commons build_legislative_evidence_packet pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bill-commons https://mcp.billcommons.org/mcpOther tools on this server
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.