Washington State Legislature MCP Server
A Model Context Protocol (MCP) server that provides AI assistants with access to Washington State Legislature data, enabling civic engagement through conversational interfaces.
Overview
This MCP server connects AI assistants to the Washington State Legislative Web Services (WSLWS), providing tools for:
- Bill tracking and information retrieval
- Committee meeting schedules and agendas
- Legislator lookup and sponsor information
- Bill status and history tracking
- Legislative document access
Features
Core Tools
getBillInfo- Retrieve detailed information about specific billssearchBills- Search for bills using keywords and optional filteringgetBillsByYear- Retrieve all bills from a specific year with filtering optionsgetCommitteeMeetings- Get committee meeting schedules and agendasfindLegislator- Find legislators by district or lookup sponsorsgetBillStatus- Get current status and history of a billgetBillDocuments- Retrieve bill document metadata with linksgetBillContent- Retrieve the actual content of a bill in AI-friendly format
MCP Resources
bill://xml/{biennium}/{chamber}/{bill_number}- Access bill documents in structured XML formatbill://htm/{biennium}/{chamber}/{bill_number}- Access bill documents in HTML formatbill://pdf/{biennium}/{chamber}/{bill_number}- Get URLs for bill PDF documentsbill://document/{format}/{biennium}/{chamber}/{bill_number}- Generic format for accessing bill documents
Installation
Prerequisites
- Python 3.10+
- pip package manager
Development Installation
pip install -e ".[dev]"
Production Installation
pip install .
Quick Start
Local Development
# Test with MCP Inspector
mcp dev src/wa_leg_mcp/server.py
# Run with stdio transport
python src/wa_leg_mcp/server.py
Remote Deployment
For cloud deployment on AWS Lambda, you can use the mcp-remote adapter to enable Claude Desktop connectivity:
{
"mcpServers": {
"wa-leg": {
"command": "npx",
"args": [
"mcp-remote",
"https://your-api-gateway-url/sse"
]
}
}
}
Basic Configuration
Create a .env file:
WSL_API_TIMEOUT=30
WSL_CACHE_TTL=300
LOG_LEVEL=INFO
SERVER_NAME="Washington State Legislature MCP Server"
Repository Structure
wa-leg-mcp/
├── src/
│ ├── wa_leg_mcp/
│ │ ├── __init__.py
│ │ ├── server.py # Main MCP server implementation
│ │ ├── tools/ # Tool implementations
│ │ │ ├── __init__.py
│ │ │ ├── bill_tools.py
│ │ │ ├── committee_tools.py
│ │ │ └── legislator_tools.py
│ │ ├── resources/ # MCP resource implementations
│ │ │ ├── __init__.py
│ │ │ └── bill_resources.py # Bill document resources
│ │ ├── clients/ # API clients
│ │ │ ├── __init__.py
│ │ │ └── wsl_client.py # WA State Legislature API client
│ │ └── utils/ # Utility functions
│ │ ├── __init__.py
│ │ └── formatters.py
├── tests/ # Test suite
│ ├── __init__.py
│ ├── test_bill_tools.py
│ ├── test_bill_resources.py # Tests for bill resources
│ ├── test_committee_tools.py
│ ├── test_legislator_tools.py
│ ├── test_server.py
│ ├── test_utils_formatters.py
│ └── test_wsl_client.py
├── pyproject.toml # Project configuration and dependencies
├── Makefile # Development workflow commands
├── README.md
└── LICENSE
Development
Setting Up Development Environment
- Clone the repository:
git clone https://github.com/awalcutt/wa-leg-mcp.git
cd wa-leg-mcp
- Create virtual environment:
python -m venv venv
source venv/bin/activate # Or `venv\Scripts\activate` on Windows
- Install development dependencies:
pip install -e ".[dev]"
- Run tests:
make test
Adding New Tools
- Create a new file in
src/wa_leg_mcp/tools/ - Implement tool using the MCP decorator:
from mcp.server.fastmcp import Tool
@Tool("toolName", description="Tool description")
def tool_function(param1: str, param2: str = None):
# Implementation
return {"result": data}
- Register tool in server.py by adding it to the
get_default_tools()function - Add tests in
tests/
Deployment Options
Local Deployment
- Run directly with Python
- Use with MCP Inspector for development
Cloud Deployment
- AWS Lambda with API Gateway (supports remote connections via
mcp-remoteadapter) - Google Cloud Functions
- Azure Functions
Environment Variables
| Variable | Description | Default |
|---|---|---|
WSL_API_TIMEOUT |
API request timeout (seconds) | 30 |
WSL_CACHE_TTL |
Cache time-to-live (seconds) | 300 |
LOG_LEVEL |
Logging level | INFO |
SERVER_NAME |
Custom server name | Washington State Legislature MCP Server |
Usage Examples
With Claude Desktop
Add to Claude Desktop configuration:
{
"mcpServers": {
"wa-leg": {
"command": "python",
"args": ["path/to/src/wa_leg_mcp/server.py"],
"env": {
"WSL_CACHE_TTL": "600"
}
}
}
}
With Other AI Clients
# Example client integration
from mcp.client import ClientSession
import asyncio
async def connect_to_legislature_mcp():
async with ClientSession(server_command=["python", "src/wa_leg_mcp/server.py"]) as session:
# List available tools
tools = await session.list_tools()
# Call a tool
result = await session.call_tool("getBillInfo", {
"bill_number": "HB1234",
"biennium": "2025-26"
})
print(result)
# Access a resource
bill_xml = await session.read_resource(
"bill://xml/2025-26/House/1234"
)
print(f"Bill XML content length: {len(bill_xml)}")
asyncio.run(connect_to_legislature_mcp())
API Documentation
Tools
getBillInfo
Retrieves detailed information about a specific bill using the GetLegislation API.
Parameters:
bill_number(string, required): Bill number (e.g., "HB1234", "SB5678")biennium(string, required): Legislative biennium in format "2025-26"
Returns: Bill details including description, sponsor, status, fiscal notes, and companions
searchBills
Searches for bills using keywords and optional filtering via the WSL Search API.
Parameters:
query(string, required): Search query text (e.g., "climate change", "transportation")bienniums(array, optional): List of bienniums to search (format: "YYYY-YY"), defaults to currentagency(string, optional): Filter by originating agency ("House", "Senate", or "Both")max_results(integer, optional): Maximum number of total results to return (max 100)
Returns: List of bills matching the search criteria
getBillsByYear
Retrieves all bills from a specific year with optional filtering using the GetLegislationByYear API.
Parameters:
year(string, optional): Year in format "YYYY" (e.g., "2025"), defaults to currentagency(string, optional): Filter by originating agency ("House" or "Senate")active_only(boolean, optional): If True, only return active bills
Returns: List of bills matching the criteria
getCommitteeMeetings
Retrieves committee meetings and agendas using the GetCommitteeMeetings API.
Parameters:
start_date(string, required): Start date in YYYY-MM-DD formatend_date(string, required): End date in YYYY-MM-DD formatcommittee(string, optional): Filter by specific committee
Returns: List of committee meetings with dates, times, locations, and agenda items
findLegislator
Finds legislators using the GetSponsors API.
Parameters:
biennium(string, required): Legislative biennium in format "2025-26"chamber(string, optional): "house" or "senate"
Returns: List of legislators with ID, name, party, and contact information
getBillStatus
Gets current status and history using the GetCurrentStatus API.
Parameters:
bill_number(string, required): Bill number (e.g., "HB1234")biennium(string, required): Legislative biennium in format "2025-26"
Returns: Current status, history, action dates, and status descriptions
getBillDocuments
Retrieves bill documents metadata (functionality based on Document service endpoints).
Parameters:
bill_number(string, required): Bill numberbiennium(string, required): Legislative biennium in format "2025-26"document_type(string, optional): "bill", "amendment", "report"
Returns: Document metadata with links to HTML and PDF versions
getBillContent
Retrieves the actual content of a bill in an AI-friendly format.
Parameters:
bill_number(integer, required): Bill number as an integer (e.g., 1234 for HB1234)biennium(string, optional): Legislative biennium in format "2025-26" (defaults to current)chamber(string, optional): Chamber name - "House" or "Senate" (optional if bill_number is unique across chambers)bill_format(string, optional): Document format - "xml" (default), "htm", or "pdf"
Returns: For XML and HTM formats: Dict containing the document content and metadata. For PDF format: Dict containing the URL to access the PDF and metadata.
Resources
Bill Document Resources
The MCP server provides direct access to bill documents through URI templates:
bill://xml/{biennium}/{chamber}/{bill_number}
Access bill documents in structured XML format (recommended for AI processing).
Parameters:
biennium(string): Legislative biennium in format "YYYY-YY" (e.g., "2025-26")chamber(string): Chamber name - must be exactly "House" or "Senate"bill_number(string): Bill number as numeric string (e.g., "1234")
Returns: XML content of the bill document
bill://htm/{biennium}/{chamber}/{bill_number}
Access bill documents in HTML format with hyperlinks to referenced laws.
Parameters:
biennium(string): Legislative biennium in format "YYYY-YY"chamber(string): "House" or "Senate"bill_number(string): Bill number
Returns: HTML content of the bill document
bill://pdf/{biennium}/{chamber}/{bill_number}
Get URLs for bill PDF documents (content not fetched).
Parameters:
biennium(string): Legislative biennium in format "YYYY-YY"chamber(string): "House" or "Senate"bill_number(string): Bill number
Returns: Dictionary with URL to access the PDF document
bill://document/{format}/{biennium}/{chamber}/{bill_number}
Generic format for accessing bill documents in any supported format.
Parameters:
format(string): Document format - "xml", "htm", or "pdf"biennium(string): Legislative biennium in format "YYYY-YY"chamber(string): "House" or "Senate"bill_number(string): Bill number
Returns: Document content or URL based on format
Contributing
We welcome contributions! Please see our Contributing Guidelines for details.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for wa-leg-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| wa_leg_mcp-0.1.0.tar.gz | 42.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wa_leg_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.2 kB
Release files / wa_leg_mcp-0.1.0.tar.gz
| Download URL | wa_leg_mcp-0.1.0.tar.gz |
|---|---|
| Size | 42.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11f908436999ea20d59c176de6869f1871ac3651d1d6c8b0f76a56dc5d6f97c8
|
|
BLAKE2b-256 checksum How to use checksums |
b6afdc16f092f9db365e43c21fccdf104f05f4faab51a965e446529e28c04dcd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2025.
Transparency logRelease files / wa_leg_mcp-0.1.0-py3-none-any.whl
| Download URL | wa_leg_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 26.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b2286c47925ad285ffd3252589b96d003489599f6666ffcac868a566d7168bd
|
|
BLAKE2b-256 checksum How to use checksums |
61a8bcab9c3f9b4a4e2851e1b856aa7ff2bc9a676da787d3ed4803c9d93491d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2025.
Transparency logSecurity for wa-leg-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for wa_leg_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.