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