le-bills-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@le-bills-mcp What happened to HB 1 in the 2026 Utah general session?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
le-bills-mcp
An MCP server for Utah State Legislature data from le.utah.gov: bills, bill text, votes, fiscal notes, legislators, committees and meetings. With a developer token it also covers the Utah Code, Constitution, legislative rules and meeting agendas.
It is built to keep LLM context small. Every tool has a character budget, long results page
with next_offset, and bill text stays on the server until you ask for a specific piece.
Setup
Requires Python 3.14+ and uv.
From the project folder, install the dependencies:
uv syncOptionally, copy .env.example to .env and add an LE_UTAH_TOKEN to enable the
Code, Constitution, Rules and agenda tools:
# macOS/Linux
cp .env.example .env
# Windows (PowerShell)
Copy-Item .env.example .env
# Windows (Command Prompt)
copy .env.example .envClaude Code
Replace the path with where you cloned the project:
# macOS/Linux
claude mcp add le-bills -- uv --directory /path/to/le-bills-mcp run le-bills-mcp
# Windows (forward slashes work and avoid quoting issues)
claude mcp add le-bills -- uv --directory C:/path/to/le-bills-mcp run le-bills-mcpClaude Desktop app
Find the full path to
uv. Desktop apps don't always see your shell'sPATH, so a bareuvmay fail to start.Windows (PowerShell):
(Get-Command uv).Source, e.g.C:\Users\you\.local\bin\uv.exemacOS/Linux:
which uv, e.g./Users/you/.local/bin/uv
Open the config file. In Claude Desktop, go to Settings → Developer → Edit Config. This opens
claude_desktop_config.jsonand creates it if it doesn't exist. If you'd rather open it yourself, it lives at:Windows (installer):
%APPDATA%\Claude\claude_desktop_config.jsonWindows (Microsoft Store):
%LOCALAPPDATA%\Packages\Claude_<id>\LocalCache\Roaming\Claude\claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Add the server under
mcpServers. If the file already has other servers, add thele-billsentry next to them rather than replacing the file.macOS/Linux:
{ "mcpServers": { "le-bills": { "command": "/Users/you/.local/bin/uv", "args": ["--directory", "/path/to/le-bills-mcp", "run", "le-bills-mcp"] } } }Windows:
{ "mcpServers": { "le-bills": { "command": "C:\\Users\\you\\.local\\bin\\uv.exe", "args": ["--directory", "C:\\path\\to\\le-bills-mcp", "run", "le-bills-mcp"] } } }In JSON, Windows paths need doubled backslashes (
C:\\path), or you can use forward slashes (C:/path).Optional: settings. The server reads
.envfrom the project folder, so a token you put there is picked up automatically. To keep settings in the app config instead, add anenvblock to the entry:"env": { "LE_UTAH_TOKEN": "your-token", "LE_MAX_RESPONSE_CHARS": "4000" }Fully quit and reopen Claude Desktop. Closing the window isn't enough. On Windows, quit from the system tray icon; on macOS, use Claude → Quit.
Check that it loaded. In a new chat, open the tools menu (the sliders icon in the message box) and look for
le-bills. Then try asking: "What happened to HB 1 in the 2026 Utah general session?"
If it doesn't show up:
Go to Settings → Developer. A failed server is listed there with its error.
Logs are in the
logsfolder next to the config file (mcp-server-le-bills.log). On macOS that is~/Library/Logs/Claude/.Run the same command in a terminal to see any error directly:
uv --directory /path/to/le-bills-mcp run le-bills-mcp(on Windows, useC:/path/to/le-bills-mcp). If it's working, it starts and then waits silently for input; press Ctrl+C to exit.Common causes are a wrong
uvor project path, single backslashes in the JSON, or a missing comma between servers.
Settings
Set these in .env in the project folder, or in your MCP client's env block.
Variable | Default | Purpose |
| unset | GLEN developer token. Enables |
|
| Default per-response character budget (500–20000). |
| unset (memory only) | Optional directory to save the bill search index in, so it survives restarts (about 1.2 MB per session). |
Related MCP server: Washington State Legislature MCP Server
Tools
Bills
get_bill: metadata and summary, withdetailset to brief, standard or full.get_bill_history: actions, votes and floor debates. By default it returns recent actions plus all votes.get_bill_documents: text versions, fiscal notes and committee reports, as URLs.get_fiscal_note: the fiscal note as plain text, paged.search_bills: keyword search over titles, subjects and summaries, with sponsor, subject and status filters.refresh_bill_index: updates the search index or reports its progress.list_bills,list_passed_bills,list_bill_requests.
Bill text workspace
load_billloads a bill's text into server memory and returns only a table of contents.read_bill_textreads a section, or pages through the whole bill. Amendments show as[+inserted+]and[-deleted-].find_in_billreturns matching snippets with their section ids.list_loaded_billsandunload_billmanage the workspace, which holds up to 10 bills (LRU).Resources:
bill://{session}/{bill}andbill://{session}/{bill}/section/{id}.
People and meetings
list_legislators,get_legislator,list_committees,get_committee,get_meeting_calendar.
Sessions are written as 2026 or 2026GS for a general session and 2025S1 for a special
session. Omit the session to use the current general session. Bill numbers accept HB 1,
H.B. 1, hb0001 and SJR3.
Search index and rate limits
le.utah.gov's bill list has no titles, and the site rate-limits bursts of requests (HTTP 429).
The first search_bills call for a session therefore does three things:
Seeds the index right away with titles from
passedlist.json.Fetches every bill's JSON in the background, one about every 0.6 s, so the first build takes about 10 minutes. It backs off on 429.
Refreshes it incrementally after that, refetching only bills whose
updatetimechanged.
By default the index is kept in memory only, so nothing is written to disk, and it is rebuilt
after each server restart. Set LE_CACHE_DIR to save it so later restarts skip the 10-minute
build. (A developer token doesn't help here: GLEN's bill list has no titles either.)
Searches during the build return partial results, and an index.building flag says so.
Development
uv run pytest # unit + fixture-based tool tests (offline)
uv run mcp dev src/le_bills_mcp/server.py # MCP Inspectortests/test_server.py checks that every tool stays within max_chars.
License
MIT. See LICENSE.
Available Tools
19 toolsfind_in_billARead-only
Search inside a bill's text and return only matching snippets with their section ids (loads the bill if needed). Use read_bill_text(section=..., offset=...) to read around a hit.
Inputs: bill (required), pattern (required), regex, session, +3 more.
get_billARead-only
Get a bill's metadata: title, sponsors, status, and (standard/full) its summary, subjects, affected code sections, versions. Does not include bill text - use load_bill for that.
Inputs: bill (required), detail, session, max_chars.
get_bill_documentsARead-only
List a bill's documents (bill text versions, fiscal notes, committee reports, transmittal letters) with absolute URLs.
Inputs: bill (required), session, max_chars.
get_bill_historyARead-only
Action history of a bill (committee referrals, readings, votes with tallies as yeas-nays-absent, governor action) plus floor debate dates. By default returns the last 10 actions plus every vote action, oldest first.
Inputs: bill (required), limit, offset, session, +2 more.
get_committeeARead-only
Get a committee's members (with positions) and scheduled meetings.
Inputs: committee (required), max_chars.
get_fiscal_noteARead-only
Read a bill's fiscal note (estimated revenue/expenditure impact) as plain text, paged.
Inputs: bill (required), offset, session, max_chars.
get_legislatorARead-only
Get one legislator by id or name. Returns candidates if the name is ambiguous.
Inputs: who (required), detail, max_chars.
get_meeting_calendarCRead-only
Upcoming legislative meetings (times in UTC; Utah is UTC-7/-6).
Inputs: limit, offset, end_date, committee, +2 more.
list_bill_requestsBRead-only
Unnumbered bill requests (drafts being prepared) for a session, with titles and sponsor ids.
Inputs: limit, query, offset, session, +2 more.
list_billsARead-only
List numbered bills in a session with last-update times (titles included when the search index has been built). Use get_bill or search_bills for details.
Inputs: sort, limit, offset, prefix, +3 more.
list_committeesBRead-only
List legislative committees with chair, member count and next meeting (UTC).
Inputs: limit, query, offset, max_chars.
list_legislatorsARead-only
List current Utah legislators, filterable by chamber, party, district or county.
Inputs: limit, party, county, detail, +4 more.
list_loaded_billsBRead-only
List bills currently loaded in working memory.
Inputs: no named parameters.
list_passed_billsBRead-only
Bills that passed the Legislature in a session (2016+), with governor action.
Inputs: limit, offset, session, max_chars, +1 more.
load_billARead-only
Load a bill's full text into the server's working memory and return only a table of contents (section ids, headings, sizes). The text stays server-side: read it piece by piece with read_bill_text or search it with find_in_bill. Up to 10 bills stay loaded.
Inputs: bill (required), refresh, session, version.
read_bill_textARead-only
Read a slice of a bill's text (loads the bill if needed). Amendments are marked [+inserted+] and [-deleted-]. Page with offset/next_offset.
Inputs: bill (required), offset, section, session, +1 more.
refresh_bill_indexARead-only
Update the local search index for a session (only changed bills unless full=True), or check on a background build's progress.
Inputs: full, session.
search_billsARead-only
Keyword search over bill titles, subjects and summaries for a session. With an empty query, lists bills matching the subject/sponsor/status filters. The first search of a session starts building a local index in the background (~10 min, rate-limited); until it finishes, results cover passed bills (titles only) plus whatever has been indexed so far.
Inputs: query (required), limit, offset, status, +5 more.
unload_billARead-only
Remove a bill from working memory.
Inputs: bill (required), session.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Search bills and speaker-attributed hearing transcripts across all 50 US state legislatures.
U.S. civic data for AI agents: reps, votes, bills, finance, lobbying, cited gov sources. 47 tools.
Bills, hearings, votes and legislators for all 50 US states, DC and Congress, from official sources.
Federal and 50-state legislative data for AI: bills, text, votes, members, and committees.
Related MCP Servers
- 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
- AlicenseAqualityDmaintenanceEnables AI assistants to access Washington State Legislature data for bill tracking, committee meetings, legislator lookup, and legislative document retrieval via conversational interfaces.91MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to query U.S. legislative data, including jurisdictions, legislators, and bills, via the OpenStates API.1-
- 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