trace_legislative_history — bill commons MCP Tool
trace_legislative_history
(trace legislative history) 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 trace_legislative_history from your client
- Claude Code bill commons trace_legislative_history run in your project directory
- Claude Desktop bill commons trace_legislative_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor bill commons trace_legislative_history ~/.cursor/mcp.json
- VS Code bill commons trace_legislative_history .vscode/mcp.json
- Zed bill commons trace_legislative_history ~/.config/zed/settings.json
- Windsurf bill commons trace_legislative_history ~/.codeium/windsurf/mcp_config.json
- Cline bill commons trace_legislative_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI bill commons trace_legislative_history ~/.gemini/settings.json
- Grok bill commons trace_legislative_history .mcp.json (in your project root)
- ChatGPT bill commons trace_legislative_history Settings → Connectors → Advanced → Developer mode
- Claude.ai bill commons trace_legislative_history Settings → Connectors → Add custom connector
- LangChain bill commons trace_legislative_history 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.