Wsdot MCP Server

@cyanheads/wsdot-mcp-server Query WA highway conditions, ferry schedules, vessel locations, toll rates, border waits, and alerts via MCP. STDIO or Streamable HTTP. 12 Tools • 1 Skill Resource

Public Hosted Server: https://wsdot.caseyjhand.com/mcp

Overview

Washington State roads and ferries from WSDOT. Check mountain passes, travel times, tolls, border waits, alerts, and traffic cameras, and track ferry schedules, vessel locations, and terminal space.

Tools

Resources

Capability reference

skill://wsdot-guide/SKILL.md resource

• Ferry trip guidance for combining schedules, service alerts, live vehicle space, and vessel positions. Also included in plugin installs as wsdot-guide.

wsdot_get_mountain_passes tool

• No input — current conditions for all 16 WA mountain passes (Snoqualmie, Stevens, White, Blewett, Cayuse, and others) in one call
• Each pass carries road condition, weather, temperature, elevation, and up to two directional traction/travel restrictions

wsdot_search_alerts tool

• Optional stateRoute, region (Northwest, Olympic, Southwest, South Central, North Central, Eastern), and startMilepost / endMilepost — an alert matches when its extent overlaps the range; omit all for every statewide alert. Ordered by alertId, paged (default 20, max 500)
• An unknown region fails as invalid_region and a start above the end as invalid_milepost_range, each with a recovery hint

wsdot_get_travel_times tool

• Optional route — a route ("I-5", "SR 520") returns every corridor measured on it, any other text matches corridor names ("Everett"); paged (default 50, max 500)
• Each corridor reports current and average minutes — current above average means congestion, and the delta is the delay. A reversible express-lane corridor closed in the queried direction omits its figures rather than reporting zero

wsdot_get_toll_rates tool

• Covers SR 99 (WSDOT Tunnel), SR 167 HOT Lanes, I-405 Express Lanes, the SR 509 tolled segment, and the SR 520 Bridge. Optional stateRoute matches the posted designation ("I-405", "SR 520"); a route with no tolled facility returns an empty page whose notice names the tolled routes. Paged (default 50, max 500)
• Each row leads with its startLocationName → endLocationName segment. stateRoute is the feed's bare zero-padded number ("099") and travelDirection the feed's code, which SR 99, SR 509, and SR 520 fix per facility — read direction from the segment's ends

wsdot_get_border_waits tool

• No input — eleven lane entries in crossings[] across I-5 (Peace Arch), SR 543 (Pacific Highway), SR 539 (Lynden), and SR 9 (Sumas): a general-purpose and a Nexus lane at each, plus truck lanes at SR 539 and SR 543
• crossingName is a route code (I5, SR543Trucks) and location.description the readable name; a lane with no current data omits waitTimeInMinutes

wsdot_search_cameras tool

• Optional stateRoute, region code (NW, SW, OL, ER, SC, NC, OS for the Oregon TripCheck cameras, WA for airport cameras), startMilepost / endMilepost, and titleContains (every word, any order). Ordered by cameraId, paged (default 50, max 500)
• Returns metadata and image URLs, not image bytes (camera images are copyright WSDOT). An unknown region fails as invalid_region and a reversed range as invalid_milepost_range

wsdot_get_ferry_terminals tool

• No input — all 20 WSF terminals, each with its numeric ID, abbreviation, and latitude/longitude
• Resolves names ("Bainbridge Island", "Seattle") to the IDs wsdot_get_ferry_schedule and wsdot_get_terminal_space take

wsdot_get_ferry_routes tool

• Optional tripDate (YYYY-MM-DD, default today); a date outside the range WSF has published fails as invalid_date stating that range
• Each route carries its ID (the impactedRouteIds of wsdot_get_ferry_alerts), abbreviation, description, and terminalPairs — the departing → arriving pairs wsdot_get_ferry_schedule accepts that day

wsdot_get_ferry_schedule tool

• Requires departingTerminalId and arrivingTerminalId (a pair from terminalPairs on wsdot_get_ferry_routes); optional tripDate (default today) and remainingOnly (future departures only, today only)
• Each sailing carries departureTime / arrivalTime in ISO 8601 UTC (tripDate is the Pacific service day), vesselId, loadingRule, and indexes into the pair's annotations. There is no cancellation flag — WSF drops a cancelled sailing, so check wsdot_get_ferry_alerts
• A pair with no schedule that day fails as invalid_terminal_pair and a date with none as invalid_date, never as an empty schedule

wsdot_get_vessel_locations tool

• No input — position, speed, heading, ETA, and dock status for every active WSF vessel
• Positions may lag 30–60 seconds; many fields are absent for a vessel not in service, and one between assignments reports opRouteAbbrev as none reported

wsdot_get_terminal_space tool

• Optional departingTerminalId (from wsdot_get_ferry_terminals), else every terminal; paged by terminal (default 5, max 20), with every sailing of a returned terminal included
• driveUpSpaceCount is the key field — zero means the drive-up lane is full, and an oversubscribed sailing's negative upstream count floors to zero. arrivingTerminalIds chains into wsdot_get_ferry_schedule

wsdot_get_ferry_alerts tool

• No input — active WSF disruptions, delays, and bulletins, each with alertTitle, a one-line alertDescription, and the full bulletinText (detail such as a replacement sailing appears only in the body)
• impactedRouteIds map to wsdot_get_ferry_routes; affectsAllRoutes: true marks a fleet-wide alert, whose empty route list then means every route

Features

Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.

WSDOT-specific:

• Dual API integration — WSDOT Traffic API and WSF Ferry API share a single WSDOT_ACCESS_CODE
• Cross-tool linking built into tool descriptions — ferry tools point to wsdot_get_ferry_terminals / wsdot_get_ferry_routes for ID resolution before a lookup
• Normalized response shapes across both APIs — sparse upstream fields surface as optional rather than omitted or defaulted
• Stable pagination — the alert and camera feeds return the same set in more than one row order upstream, so results are sorted by ID to keep a given offset reproducible
• Paged list tools take offset / limit, and a page also ends early at a 24,000-byte response budget, with the notice naming the next offset
• Route filters take the forms people write — "I-90", "90", "090", "SR 520" — and every text filter accepts at most 200 characters

Agent-friendly output:

• Typed failure — invalid_access_code and api_unavailable errors carry an explicit recovery hint distinguishing configuration faults from transient upstream ones
• driveUpSpaceCount: 0 and congestion delta fields (delayInMinutes) give agents actionable signal without string parsing
• Plain text from HTML — alert descriptions, sailing notes, and bulletins arrive from upstream as HTML and are returned as text, with links inline as link text (url)
• Partial data preserved — sparse upstream payloads surface null/undefined rather than synthetic defaults (e.g. an omitted waitTimeInMinutes, an absent arrivalTime)
• content[] and structuredContent carry the same values, not just the same fields