Log inSubmit server
Wsdot MCP Server logo

Wsdot MCP Server

Queries Washington highway, ferry, toll, border, camera, and traffic data through 12 MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Wsdot MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "wsdot-mcp-server": {
      "command": "bunx",
      "args": [
        "@cyanheads/wsdot-mcp-server@latest"
      ],
      "env": {
        "WSDOT_ACCESS_CODE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

bunx @cyanheads/wsdot-mcp-server@latest

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Overview

The wsdot-mcp-server MCP server connects MCP clients to Washington State transportation data from the WSDOT Traveler API and WSF Ferry API. It provides tools for mountain passes, highway alerts, travel times, toll rates, border waits, cameras, ferry schedules, vessel positions, terminal capacity, and service alerts. Run it over stdio, as a local Streamable HTTP server, or through the hosted endpoint. Reach for it when an agent needs current Washington travel or ferry information rather than static route data.

Use cases

  • Check mountain-pass conditions before a winter drive
  • Find active highway closures along a route
  • Compare current and average corridor travel times
  • Plan a ferry trip using schedules and terminal space
  • Monitor Washington border waits and ferry disruptions

Key features

  • Mountain-pass and highway-condition queries
  • Route-filtered alerts, cameras, and travel times
  • Dynamic toll-rate and border-wait lookups
  • Ferry route, schedule, capacity, and alert data
  • Real-time WSF vessel locations
  • stdio and Streamable HTTP deployment

Tools12

What Wsdot MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~396 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @cyanheads/wsdot-mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads945Package downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed12Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Wsdot MCP Server works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Wsdot MCP Server

wsdot-mcp-server is an MCP server that connects AI clients to the WSDOT Traveler API and WSF Ferry API. Its main tools query Washington highway conditions, alerts, travel times, tolls, border waits, cameras, ferry schedules, terminal space, service alerts, and live vessel locations.

Install it through the repository's Claude Desktop, Cursor, or VS Code links, or run it with `npx -y @cyanheads/wsdot-mcp-server`. Configure `WSDOT_ACCESS_CODE` in the client environment. The server also supports stdio and Streamable HTTP deployment.

Yes, wsdot-mcp-server works with Cursor. The repository provides a Cursor installation link that configures the npm package command and a `WSDOT_ACCESS_CODE` environment variable.

Yes, it provides ferry schedules for a specific WSF route, including departure times, vessel names, loading rules, and notes. Use the ferry route tool first when you need to discover route IDs or terminal pairs.

Related MCP servers

All in Travel & Transportation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWsdot MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/wsdot-mcp-server?style=directory)](https://allmcps.com/mcp/wsdot-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/wsdot-mcp-server"><img src="https://allmcps.com/api/badge/wsdot-mcp-server?style=directory" alt="Wsdot MCP Server on AllMCPs" /></a>