Wsdot Mcp Server

io.github.cyanheadsPublished by GitHub account cyanheadsv0.6.0Updated Nov 12, 2026

WA highway conditions, ferry schedules and fares, vessel locations, tolls, and border waits via MCP.

VerifiedStreamable HTTPWeb executableLocation & LifestyleWeb Search & Scraping

Overview

AI-generated overview

Washington State travel data via MCP: highway conditions, tolls, border waits, cameras, and WSF ferry schedules, fares, vessel positions and terminal space.

What you can do
  • Check mountain pass conditions, active highway alerts, corridor travel times, toll rates, border waits and camera metadata
  • Look up ferry terminals, routes operating on a date, departure schedules and fare line items
  • Track live vessel positions and drive-up or reservable space at terminals
  • Read active ferry service disruptions and bulletins
  • Follow a bundled ferry trip guide resource that combines schedules, fares, alerts, space and vessel positions
When to use it
Useful when planning or answering questions about driving and ferrying in Washington State: whether a pass is open, how congested a corridor is, what a toll or ferry fare costs, how long a border crossing takes, or whether a sailing still has space.
Requirements
Either the hosted HTTP endpoint or a local process via npx (Node.js) or Docker. A WSDOT Traveler API access code is required in WSDOT_ACCESS_CODE, obtained by registering with WSDOT; the hosted instance needs no install. Optional settings cover transport type, HTTP host, port and endpoint path, auth mode, log level and limit clamping.
Before you install
The WSDOT_ACCESS_CODE credential is required and must be kept private. All tools are read-only lookups against public WSDOT and WSF feeds; no data is written or sent elsewhere by the server. Upstream text such as alert bodies, bulletins and sailing notes is third-party data and should not be treated as instructions. Live positions and space figures can lag or be missing.

Installation

In SourceWeft

  1. Open Wsdot Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.cyanheads%2Fwsdot-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "wsdot": {
      "type": "http",
      "url": "https://wsdot.caseyjhand.com/mcp"
    }
  }
}

README

@cyanheads/wsdot-mcp-server

Query WA highway conditions, ferry schedules and fares, vessel locations, toll rates, border waits, and alerts via MCP. STDIO or Streamable HTTP.

13 Tools • 1 Skill Resource


Overview

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

Tools

ToolDescription
wsdot_get_mountain_passesCurrent conditions for all WA mountain passes: status, road condition, traction laws, temperature, elevation.
wsdot_search_alertsActive highway alerts — incidents, construction, closures — filterable by state route, WSDOT region, and milepost range.
wsdot_get_travel_timesCurrent vs. average travel times for named WA highway corridors (I-5, I-90, SR 520, etc.) with congestion delay.
wsdot_get_toll_ratesDynamic 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_waitsCurrent vehicle wait times at all WA/Canada land border crossings.
wsdot_search_camerasHighway camera metadata and image URLs, filterable by state route, region, milepost range, and title words.
wsdot_get_ferry_terminalsAll WSF ferry terminals with numeric IDs needed for schedule, fare, and space lookups, plus coordinates.
wsdot_get_ferry_routesWSF 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_scheduleDeparture times for a specific WSF route — today-remaining or full-day future mode — with each sailing's vessel, loading rule, and notes.
wsdot_get_ferry_faresWSF fares for a terminal pair on a date — passenger, vehicle and driver by length, motorcycle, bicycle, and multi-ride card line items, one way or round trip, with WSF's statement of which terminal collects which fares.
wsdot_get_vessel_locationsReal-time AIS positions, speed, heading, ETA, and dock status for all active WSF vessels.
wsdot_get_terminal_spaceDrive-up and reservable vehicle space available for upcoming sailings, at the terminals WSF reports space for.
wsdot_get_ferry_alertsActive WSF service disruptions and bulletins with impacted route IDs.

Resources

ResourceDescription
skill://wsdot-guide/SKILL.mdFerry trip guidance for combining schedules, fares, alerts, space, and vessel positions.

Capability reference

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

  • Ferry trip guidance for combining schedules, fares, 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; a larger limit returns at most 500 with a notice)
  • headlineDescription and extendedDescription render in content[] one line at a time, each trimmed and escaped, with a run of blank lines becoming one paragraph break; the headline's first line is the alert's heading. structuredContent keeps the raw text
  • 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 designation ("I-5", "5", "SR 520") returns corridors that start or end on that route or write it in their name ("via 520"), never digits inside another number ("5" does not match I-405 or SR 522); other text matches corridor names ("Everett", "1A"), and the first number in it, read as a route, also matches every corridor that starts or ends on that route, in both directions — "I-405 southbound" returns northbound I-405 corridors too, since the direction word is not applied. A designation that matches nothing gets a notice saying so. Paged (default 50; a larger limit returns at most 500 with a notice)
  • 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; a larger limit returns at most 500 with a notice)
  • 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; a larger limit returns at most 500 with a notice)
  • A milepost bound matches the feed's milePost or the milepost written in the title (titleMilePost); a camera with no milePost is always included. On the Airports road name, milePost is a position in WSDOT's airport list (1 = Anacortes, 4 = Bellingham), not a milepost
  • Returns metadata and image URLs, not image bytes. Each image belongs to the owner the camera lists (owner, ownerUrl), and to WSDOT when none is listed. 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, wsdot_get_ferry_fares, 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 and wsdot_get_ferry_fares accept that day. The whole call runs under a 50-second deadline; one that spends it fails as retry_deadline_exceeded with a retry hint

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) beside departureTimeLocal / arrivalTimeLocal, the same instant with its Pacific offset (2026-11-05T05:30:00.000-08:00); content[] renders <local> (<UTC>). Each also has serviceDate, 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
  • With remainingOnly, a query before 03:00 Pacific also lists the previous service day's sailings still to depart, first, each carrying that day's serviceDate. When that day's schedule can't be read, a notice says so and the list holds today's sailings only
  • 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. The whole call runs under a 50-second deadline; one that spends it fails as retry_deadline_exceeded with a retry hint

wsdot_get_ferry_fares tool

  • Requires departingTerminalId and arrivingTerminalId (a pair from terminalPairs on wsdot_get_ferry_routes); optional tripDate (default today) and roundTrip (WSF's round-trip total for a trip starting at the departing terminal; default one way)
  • Returns every fare line item — passenger, senior and youth, vehicle and driver by length, motorcycle, bicycle, multi-ride cards — with amountInDollars as WSF gives it, in WSF's order
  • WSF collects most fares at one terminal only, so a line reads 0 on a leg whose departing terminal doesn't collect it. collectionDescription is WSF's statement of which terminal collects which fares, and it leads content[]; read it before quoting a 0 as free travel, and query the reverse direction to see where the fare is charged. If that statement can't be read, the fares still return and a notice says so
  • A pair with no fares that day fails as invalid_terminal_pair and a date WSF has no fares for as invalid_date. The whole call runs under a 50-second deadline; one that spends it fails as retry_deadline_exceeded with a retry hint

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
  • leftDock, eta, scheduledDeparture, and timestamp stay in UTC beside leftDockLocal, etaLocal, scheduledDepartureLocal, and timestampLocal, the same instants in Pacific time

wsdot_get_terminal_space tool

  • Optional departingTerminalId (from wsdot_get_ferry_terminals), else every terminal WSF reports space for; paged by terminal (default 5; a larger limit returns at most 20 with a notice), with every sailing of a returned terminal included
  • WSF publishes space for select terminals only (12 of 20 on 2026-11-12), and at times for none. A terminal missing from the feed has unconfirmed space rather than a wrong ID: an empty feed and an uncovered terminal ID each return an empty page whose notice says which, the second listing the terminals the feed covers. Departure times carry a departureLocal Pacific sibling
  • 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)
  • publishDate carries a publishDateLocal Pacific sibling; 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; a page ends only at limit or at the end of the set, and a notice names the next offset. A limit above a tool's maximum returns the maximum with a notice, or is rejected when WSDOT_CLAMP_LIMITS=false
  • 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 — a false flag, an empty list, and one populated half of a coordinate pair all render rather than dropping out of the markdown surface that some clients read; a blank or whitespace-only upstream string is absent from both, and a populated one arrives trimmed

Getting started

Connect to the hosted instance, no install:

sh
claude mcp add --transport http wsdot-mcp-server https://wsdot.caseyjhand.com/mcp

Or run it locally:

sh
claude mcp add wsdot-mcp-server -e WSDOT_ACCESS_CODE=your-access-code -- npx -y @cyanheads/wsdot-mcp-server

For other clients, add this to the MCP config file:

json
{  "mcpServers": {    "wsdot-mcp-server": {      "command": "npx",      "args": ["-y", "@cyanheads/wsdot-mcp-server"],      "env": {        "WSDOT_ACCESS_CODE": "your-access-code"      }    }  }}

Get a free access code at wsdot.wa.gov/Traffic/api/. For Docker or a source build, see Running the server.

Configuration

All configuration is validated at startup via Zod schemas in src/config/server-config.ts. Key environment variables:

VariableDescriptionDefault
WSDOT_ACCESS_CODERequired. WSDOT Traveler API access code. Register at wsdot.wa.gov/Traffic/api/.—
WSDOT_CLAMP_LIMITSOptional. Clamp a paged tool's limit above its maximum (500; 20 for wsdot_get_terminal_space) to that maximum, with a notice. false rejects it instead and advertises maximum in tools/list. Each clamp increments the wsdot.limit.clamps counter and writes one Clamped limit log line.true
MCP_TRANSPORT_TYPETransport: stdio or http.stdio
MCP_HTTP_PORTHTTP server port.3010
MCP_HTTP_HOSTHTTP server hostname.127.0.0.1
MCP_HTTP_ENDPOINT_PATHHTTP endpoint path./mcp
MCP_PUBLIC_URLPublic origin for TLS-terminating reverse-proxy deployments.—
MCP_SESSION_MODESession handling: auto, stateful, or stateless. The schema default auto resolves to stateful; this server sets stateless explicitly.stateless
MCP_AUTH_MODEAuthentication: none, jwt, or oauth.none
MCP_LOG_LEVELLog level (debug, info, notice, warning, error).info
LOGS_DIRDirectory for log files (Node.js only).<project-root>/logs
STORAGE_PROVIDER_TYPEStorage backend: in-memory, filesystem, supabase, cloudflare-kv/r2/d1.in-memory
LOG_TOOL_FAILURE_PAYLOADSLog each failed tool call's arguments and result (key-name redaction only).false
OTEL_ENABLEDEnable OpenTelemetry instrumentation (spans, metrics, completion logs).false
OTEL_EXPORTER_OTLP_ENDPOINTOTLP base URL; traces go to /v1/traces, metrics to /v1/metrics.—
OTEL_EXPORTER_OTLP_LOGS_ENDPOINTOpt-in OTLP log export; the base endpoint never enables it.—

See .env.example for the full list of optional overrides.

Running the server

Local development

Requires Bun v1.4.4 or higher (or Node.js v24+).

  • Clone and install:

    sh
    git clone https://github.com/cyanheads/wsdot-mcp-server.gitcd wsdot-mcp-server && bun installcp .env.example .env   # set WSDOT_ACCESS_CODE
  • Build and run:

    sh
    # One-time buildbun run rebuild
    # Run the built serverbun run start:stdio# orbun run start:http
  • Run checks and tests:

    sh
    bun run devcheck   # Lint, format, typecheck, securitybun run test       # Vitest test suitebun run lint:mcp   # Validate MCP definitions against spec

Docker

sh
docker run --rm -e WSDOT_ACCESS_CODE=your-access-code -p 3010:3010 ghcr.io/cyanheads/wsdot-mcp-server:latest

The image defaults to HTTP transport, stateless session mode, and logs to /var/log/wsdot-mcp-server. For stdio, use docker run -i --rm -e MCP_TRANSPORT_TYPE=stdio -e WSDOT_ACCESS_CODE=your-access-code ghcr.io/cyanheads/wsdot-mcp-server:latest. To build locally, run docker build -t wsdot-mcp-server .; OpenTelemetry peer dependencies are installed by default — build with --build-arg OTEL_ENABLED=false to omit them.

Project structure

DirectoryPurpose
src/index.tscreateApp() entry point — registers all 13 tools and initializes services.
src/configServer-specific environment variable parsing and validation with Zod.
src/mcp-server/toolsTool definitions (*.tool.ts) — 6 traffic tools, 7 ferry tools.
src/services/trafficWSDOT Traffic API service (mountain passes, alerts, travel times, toll rates, border waits, cameras).
src/services/ferryWSF Ferry API service (terminals, routes, schedule, fares, vessel locations, space, alerts).
skills/Published ferry trip guide, also served as an MCP skill resource.
tests/Unit and integration tests, mirroring the src/ structure.

Development guide

See CLAUDE.md for development guidelines and architectural rules. The short version:

  • Handlers throw, framework catches — no try/catch in tool logic
  • Use ctx.log for request-scoped logging, ctx.state for tenant-scoped storage
  • Register new tools in the createApp() arrays in src/index.ts
  • Wrap external API calls: validate raw → normalize to domain type → return output schema; never fabricate missing fields

Contributing

Issues are welcome. Run checks and tests before submitting:

sh
bun run devcheckbun run test

License

Apache-2.0 — see LICENSE for details.

Source: README.md at commit 3a17d0a

Tools

13

wsdot_get_mountain_passes

Get Mountain Pass Conditions

Returns current road conditions for all Washington State mountain passes: status, weather, road condition, traction laws, temperature, and elevation. Includes all 16 passes (Snoqualmie, Stevens, White, Blewett, Cayuse, etc.). Use for "is the pass open?", traction law status, or winter driving planning.

Takes no parameters.

wsdot_search_alerts

Search Highway Alerts

Returns active WA highway alerts: incidents, construction, closures, and restrictions. Filter by state route ("I-90", "90", "SR 520", or "520" all work), WSDOT region (Northwest, Olympic, Southwest, South Central, North Central, Eastern), or milepost range, matched against the alert's full extent. Omit all filters to return all current statewide alerts. Results are ordered by alertId and paged — pass offset/limit to page through the full set.

ParameterslimitoffsetregionstateRouteendMilepoststartMilepost

wsdot_get_travel_times

Get Travel Times

Returns current vs. average travel times for named WA highway corridors (I-5, I-405, I-90, SR 520, SR 167, and around Vancouver I-205 and SR 14). Use for "how congested is I-5?" or commute time estimates. A route designation filter ("I-5", "5", "SR 520") returns every corridor that starts or ends on that route or writes it in its name ("via 520"), never digits inside another number. Any other filter text matches corridor names ("Everett"), and the first number in it, read as a route, also matches every corridor that starts or ends on that route, in both directions — "I-405 southbound" returns northbound I-405 corridors too, since the direction word is not applied. When current time exceeds average, the corridor is congested. Results are paged — pass offset/limit to page through the full set.

Parameterslimitrouteoffset

wsdot_get_toll_rates

Get Toll Rates

Returns current dynamic toll rates for WA express lanes and tolled facilities: SR 99 (WSDOT Tunnel), SR 167 HOT Lanes, I-405 Express Lanes, SR 509 tolled segment, and the SR 520 Bridge. Rates are time-banded and change dynamically based on traffic conditions. Filter to one facility with stateRoute ("SR 520", "520", "I-405", or "405" all work). Each row reports stateRoute as the bare, zero-padded number the feed carries ("099", "405") — the posted designation is in the rendered text. Results are paged — pass offset/limit to page through the matching set.

ParameterslimitoffsetstateRoute

wsdot_get_border_waits

Get Border Wait Times

Returns current vehicle wait times at WA→Canada land border crossings: I-5 (Peace Arch, Blaine), SR 543 (Pacific Highway, Blaine), SR 539 (Lynden), and SR 9 (Sumas). Each crossing reports a general-purpose lane and a Nexus lane; SR 539 adds a truck lane and SR 543 adds truck and FAST truck lanes — eleven entries in crossings[], one per lane. crossingName is a route code (e.g. "I5", "I5Nexus", "SR543Trucks"); the readable name is in location.description. Wait times are in minutes. A crossing reporting no current data is still returned — only waitTimeInMinutes is omitted. Use for "how long is the border wait?" questions.

Takes no parameters.

wsdot_search_cameras

Search Highway Cameras

Returns WSDOT highway camera locations, descriptions, owners, and image URLs. Camera images belong to the owner each camera lists, and to WSDOT when none is listed — only metadata and image URLs are returned, not image bytes. Filter by state route ("I-90", "90", "SR 520", or "520" all work), WSDOT region, milepost range (matched against both the feed milepost and the milepost in the title), or words in the camera title ("Snoqualmie"). Results are ordered by cameraId and paged — pass offset/limit to page through the full set.

ParameterslimitoffsetregionstateRouteendMilepoststartMileposttitleContains

wsdot_get_ferry_terminals

Get Ferry Terminals

Returns all WSF ferry terminals with their numeric IDs, names, abbreviations, and coordinates. Call this first to resolve human-readable terminal names (e.g. "Bainbridge Island", "Seattle", "Kingston") to the numeric terminal IDs required by the schedule and space tools. The terminal list is small (20 terminals) and rarely changes.

Takes no parameters.

wsdot_get_ferry_routes

Get Ferry Routes

Returns the main WSF ferry routes operating on a given date, each with the directed terminal pairs it serves that day (terminalPairs) — departing and arriving terminal IDs and names, which are exactly the pairs wsdot_get_ferry_schedule accepts for that date. Route IDs correspond to impactedRouteIds in ferry alerts from wsdot_get_ferry_alerts, though some alert route IDs (seasonal, San Juan interisland, or Sidney B.C.) may not appear in this list. For the full terminal list with coordinates, use wsdot_get_ferry_terminals.

ParameterstripDate

wsdot_get_ferry_schedule

Get Ferry Schedule

Returns departure times for a specific WSF ferry route on a given date. Requires numeric terminal IDs — use wsdot_get_ferry_terminals to resolve terminal names to IDs; terminalPairs on wsdot_get_ferry_routes lists the pairs with service on a date. Set remainingOnly to true to show only future departures for today (useful for "next ferry" queries); a query after midnight also includes the previous service day's sailings still to depart, listed first. Each sailing's serviceDate names the service day whose schedule lists it. For future dates, all sailings for that day are returned. Each sailing carries its vessel ID, WSF's loading-rule code, and the pair's annotations that apply to it — notes such as "No interisland vehicles" that decide whether a sailing takes a car. Sailing times are ISO 8601 UTC, each beside a Local sibling (departureTimeLocal, arrivalTimeLocal) holding the same instant in Pacific time with its UTC offset — quote the Local form as the clock time. tripDate is the Pacific service day, so an evening sailing's UTC time carries the next calendar date. Cancellations are not carried here — WSF drops a cancelled sailing from the schedule instead of flagging it, so a listed sailing is not confirmation that it will run. Check wsdot_get_ferry_alerts for disruptions; those are scoped to a route, not an individual sailing.

ParameterstripDateremainingOnlyarrivingTerminalIdrequireddepartingTerminalIdrequired

wsdot_get_ferry_fares

Get Ferry Fares

Returns WSF's fares for one ferry trip between two terminals on a date: every fare line item — passenger, senior and youth, vehicle and driver by length, motorcycle, bicycle, and multi-ride cards — with its amount in dollars, plus WSF's statement of which terminal collects which fares. Requires numeric terminal IDs — use wsdot_get_ferry_terminals to resolve terminal names to IDs; terminalPairs on wsdot_get_ferry_routes lists the pairs with service on a date, the same pairs wsdot_get_ferry_schedule accepts. WSF collects most fares in one direction only, so a line reads 0 on a leg whose departing terminal does not collect it: read collectionDescription before quoting a 0 as free travel, and query the reverse direction for where that fare is charged.

ParameterstripDateroundTriparrivingTerminalIdrequireddepartingTerminalIdrequired

wsdot_get_vessel_locations

Get Vessel Locations

Returns real-time AIS positions, speed, heading, ETA, and dock status for all active WSF vessels. Use for "where is the ferry now?", vessel tracking, or checking if a vessel is in service. Position data may lag by 30–60 seconds. Many fields are absent for vessels not currently operating.

Takes no parameters.

wsdot_get_terminal_space

Get Terminal Space

Returns real-time drive-up and reservable vehicle space available at WSF terminals for upcoming sailings. Use for "will I make the ferry?" or "how full is the next sailing?" questions. WSF publishes space for select terminals only, and at times for none: a terminal missing from the result has unconfirmed space, not a wrong ID — wsdot_get_ferry_schedule and wsdot_get_ferry_alerts still show its sailings. Optionally filter to a specific terminal by ID (use wsdot_get_ferry_terminals for the ID). driveUpSpaceCount is the key field — zero means the drive-up lane is full. Destinations are arrivingTerminalIds, not the itineraryLabel string: a sailing can serve several terminals, and those IDs are what wsdot_get_ferry_schedule accepts. Results are paged by terminal (default 5, at most 20 per page): offset/limit select whole terminals and totalCount counts matching terminals, not sailings — every sailing of a returned terminal is included, so page size varies with how many departures each terminal carries.

ParameterslimitoffsetdepartingTerminalId

wsdot_get_ferry_alerts

Get Ferry Alerts

Returns active WSF ferry service disruptions, delays, and bulletins. Each alert carries a one-line summary plus the bulletin title, kind, and full body — the body is where detail such as a replacement sailing appears. Each alert includes impacted route IDs — cross-reference with wsdot_get_ferry_routes to resolve route IDs to human-readable route names. Some IDs (seasonal, San Juan interisland, or international Sidney B.C. routes) may not appear in wsdot_get_ferry_routes for a given date.

Takes no parameters.

Version history

7
  1. v0.6.0LatestNov 12, 2026
  2. v0.5.0Oct 29, 2026
  3. v0.4.2Oct 25, 2026
  4. v0.4.1Oct 9, 2026
  5. v0.4.0Sep 25, 2026
  6. v0.2.6Sep 21, 2026
  7. v0.2.5Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts