# wsdot-mcp-server [Health: Active]

**Category:** 🚆 Travel & Transportation  
**Repository:** https://github.com/cyanheads/wsdot-mcp-server  
**GitHub Stars:** 1  
**npm Downloads (last month):** 945  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/wsdot-mcp-server

## Description
WA highway conditions, ferry schedules, vessel locations, toll rates, and border waits via MCP.

## Tools
Capabilities this server exposes over MCP:

- **wsdot_get_mountain_passes** — Current conditions for all WA mountain passes: status, road condition, traction laws, temperature, elevation.
- **wsdot_search_alerts** — Active highway alerts — incidents, construction, closures — filterable by state route, WSDOT region, and milepost range.
- **wsdot_get_travel_times** — Current vs. average travel times for named WA highway corridors (I-5, I-90, SR 520, etc.) with congestion delay.
- **wsdot_get_toll_rates** — Dynamic toll rates for WA express lanes and tolled facilities — SR 99, SR 167 HOT, I-405 Express, SR 509, SR 520 — filterable by route.
- **wsdot_get_border_waits** — Current vehicle wait times at all WA/Canada land border crossings.
- **wsdot_search_cameras** — Highway camera metadata and image URLs, filterable by state route, region, milepost range, and title words.
- **wsdot_get_ferry_terminals** — All WSF ferry terminals with numeric IDs needed for schedule and space lookups, plus coordinates.
- **wsdot_get_ferry_routes** — WSF routes operating on a given date — route ID, abbreviation, description, and the terminal pairs each serves, for route discovery, schedule lookups, and ferry-alert cross-reference.
- **wsdot_get_ferry_schedule** — Departure times for a specific WSF route — today-remaining or full-day future mode — with each sailing's vessel, loading rule, and notes.
- **wsdot_get_vessel_locations** — Real-time AIS positions, speed, heading, ETA, and dock status for all active WSF vessels.
- **wsdot_get_terminal_space** — Drive-up and reservable vehicle space available at WSF terminals for upcoming sailings.
- **wsdot_get_ferry_alerts** — Active WSF service disruptions and bulletins with impacted route IDs.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `bunx` (confidence: high):

```json
"mcpServers": {
  "wsdot-mcp-server": {
    "command": "bunx",
    "args": ["@cyanheads/wsdot-mcp-server@latest"],
    "env": {
      "WSDOT_ACCESS_CODE": ""
    }
  }
}
```

**Requires environment variables:** `WSDOT_ACCESS_CODE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What wsdot-mcp-server does

The wsdot-mcp-server MCP server exposes Washington State transportation data through the Model Context Protocol. Its sources are the WSDOT Traveler API and the WSF Ferry API, covering road conditions, incidents, congestion, toll facilities, Canadian border crossings, highway cameras, ferry operations, and vessel movement.

The road tools can return current conditions for Washington mountain passes, active alerts, corridor travel times, toll rates, border wait times, and camera metadata with image URLs. Ferry tools provide terminal identifiers and coordinates, route information, sailing schedules, available vehicle space, active service notices, and live AIS data for active WSF vessels.

## How it works

An MCP client calls one of 12 focused tools. Several tools accept route, region, milepost, title, or date filters. Route inputs support common forms such as `I-90`, `90`, and `SR 520` where applicable. Alert, travel-time, toll, and camera results support pagination; responses can also stop at a 24,000-byte budget and report the next offset.

Ferry lookups are intended to be chained when needed: terminal data supplies numeric IDs, route discovery identifies operating routes and terminal pairs, and schedule or space queries provide sailing details. Schedule results can cover the remaining departures for today or a full future day. The server reports live or current feed data, so returned availability and conditions can change.

## Setup and configuration

The wsdot-mcp-server MCP server supports a stdio process, a local Streamable HTTP server, and a public hosted Streamable HTTP endpoint at `https://wsdot.casey...com/mcp`.

The repository provides installation links for Claude Desktop, Cursor, and VS Code. Its Cursor and VS Code configurations use `npx -y @cyanheads/wsdot-mcp-server` and pass the `WSDOT_ACCESS_CODE` environment variable. Configure that access code according to the server's installation instructions before starting the process.

## Tools and capabilities

- Check all Washington mountain passes, including status, road condition, weather, temperature, elevation, and traction restrictions.
- Search highway incidents, construction, and closures by route, WSDOT region, or overlapping milepost range.
- Compare current and average travel times and identify congestion delay on measured corridors.
- Read dynamic rates for SR 99, SR 167 HOT, I-405 Express, SR 509, and SR 520.
- Retrieve vehicle waits at Washington-Canada crossings, including applicable general, Nexus, truck, and FAST lanes.
- Find highway cameras by route, region, milepost range, or title words.
- Discover ferry terminals and routes, query departures, check drive-up or reservable space, read service alerts, and track vessel position, speed, heading, ETA, and dock status.

## Limitations and notes

Data is limited to the Washington transportation systems covered by the two source APIs. A ferry schedule requires a specific WSF route, while route discovery is available separately. Some ferry and traffic values are live feed values and may be absent or change between requests.

Reversible express-lane corridors omit travel-time figures when the queried direction is closed; they do not report those cases as zero minutes. Border results still include crossings without current data, but the wait-time field is omitted. Toll route matching follows the posted designation, and the feed's travel-direction code should not automatically be interpreted as the direction of a trip.

_Full upstream README: https://allmcps.com/mcp/wsdot-mcp-server/readme_