le-bills-mcp
Related Servers
Alternatives to le-bills-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to query U.S. legislative data, including jurisdictions, legislators, and bills, via the OpenStates API.1-
- AlicenseAqualityCmaintenanceProvides access to legislative data from all 50 US states through the LegiScan API, enabling comprehensive search and retrieval of bills, votes, legislators, and legislative session information.1013 npm12MIT
- AlicenseNot gradedqualityBmaintenanceEnables searching US state bills by keyword, sponsor, committee, status, or chamber, and searching speaker-attributed committee hearing testimony across all 50 states and DC. Also retrieves full bill details, hearing transcripts, speaker activity histories, and the list of states with available data.61 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets AI assistants search and retrieve New York State legislative records — bills, laws, members, committees, floor calendars, agendas, transcripts, votes, and change feeds — through the NYS Open Legislation API or an optional local SQLite corpus. It supports full-text ElasticSearch queries and returns citation-ready links for law sections.357 npm5MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to access Washington State Legislature data for bill tracking, committee meetings, legislator lookup, and legislative document retrieval via conversational interfaces.91MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to pull the full text of any state statute by citation, and to search official section catchlines by topic or keyword to find matching citations. Keyless, and handles citation suffixes such as "12.1-16-01" or "47-16-13.1".175 npmMIT
TDQS
Scored across 19 tools
Most tools have clearly distinct purposes, especially across bills, legislators, committees, and bill-text working memory. There is some overlap between list_bills and search_bills with an empty query, and several bill-document/text tools are adjacent, but descriptions mostly resolve these boundaries.
All tool names consistently use snake_case with predictable verb_noun patterns such as get_bill, list_committees, search_bills, load_bill, and unload_bill. The naming is easy to scan and follows the same convention throughout.
At 19 tools, the surface is slightly above the typical sweet spot but reasonable given the domain spans bills, bill text, legislators, committees, and meetings. Each tool appears to serve a specific role, though a few could potentially be consolidated.
Coverage is strong for a legislative bill server: metadata, history, documents, text access, fiscal notes, search, passed bills, bill requests, legislators, committees, and meetings are all represented. Minor gaps may exist around version comparison or detailed roll-call lookup, but core workflows are covered.