12 tools split across two domains — traffic (WSDOT Traveler API) and ferries (WSF Ferry API):

Current road conditions for all WA mountain passes.

• Covers all ~12 passes: Snoqualmie, Stevens, White, Blewett, Cayuse, and others
• Fields include status (Open/Closed/Caution), road surface, active traction law, temperature, and elevation
• Use for "is the pass open?", traction law checks, or winter driving planning

Active WA highway alerts — incidents, construction, closures, restrictions.

• Filter by state route (zero-padded 3-digit number: "005" for I-5, "090" for I-90, "520" for SR 520)
• Filter by WSDOT region: Northwest, Olympic, Southwest, South Central, North Central, Eastern
• Filter by milepost range to scope to a corridor
• Omit all filters to return all current statewide alerts

Current vs. average travel times for named WA highway corridors.

• Covers I-5, I-90, SR 520, SR 99, I-405, SR 167, and others
• Filter by partial route name (e.g. "I-5", "SR 520") to narrow results
• When current time exceeds average, the corridor is congested; the delta is the delay

Current dynamic toll rates for WA tolled facilities.

• SR 99 (WSDOT Tunnel), SR 520 Bridge, I-405 Express Lanes, I-90 Two-Way Express Lanes, SR 167 HOT Lanes
• Rates are time-banded and change dynamically based on traffic conditions

Current vehicle wait times at WA/Canada land border crossings.

• Covers I-5 (Peace Arch & Pacific Highway, Blaine), SR 539 (Lynden), and SR 9 (Sumas), including Nexus-lane variants
• crossingName is a route code (e.g. I5, SR539); location.description holds the readable name
• Wait times in minutes; a crossing reporting no current data is omitted; updateTime is ISO 8601

WSDOT highway camera metadata and image URLs.

• Filter by state route, WSDOT region, or milepost range; omit to list all cameras statewide
• Returns metadata and image URLs — camera images are copyright WSDOT, not fetched as bytes
• Potentially hundreds of results statewide; use filters to scope

All WSF ferry terminals with numeric IDs.

• ~22 terminals; the list rarely changes
• Call this first to resolve human-readable names (e.g. "Bainbridge Island", "Seattle", "Kingston") to the numeric IDs required by wsdot_get_ferry_schedule and wsdot_get_terminal_space

WSF ferry routes operating on a given date.

• Returns terminal ID pairs and crossing times for each route
• Route IDs correspond to impactedRouteIds in wsdot_get_ferry_alerts
• Use to discover which routes are running and get terminal IDs for schedule lookups

Departure times for a specific WSF ferry route.

• Requires numeric terminal IDs — use wsdot_get_ferry_terminals first
• remainingOnly: true returns only future departures for today (useful for "next ferry" queries)
• For future dates, all sailings for that day are returned

Real-time AIS positions for all active WSF vessels.

• Fields include position, speed, heading, ETA, and dock status
• Use for "where is the ferry now?" or checking if a specific vessel is in service
• Position data may lag 30–60 seconds; many fields are null for vessels not currently operating

Real-time vehicle space availability at WSF terminals for upcoming sailings.

• DriveUpSpaceCount is the key field — zero means the drive-up lane is full
• Filter to a specific terminal by ID (from wsdot_get_ferry_terminals)
• Use for "will I make the ferry?" or "how full is the next sailing?" queries

Active WSF ferry service disruptions, delays, and bulletins.

• Each alert includes impactedRouteIds — cross-reference with wsdot_get_ferry_routes to map route IDs to names

Built on @cyanheads/mcp-ts-core:

• Declarative tool definitions — single file per tool, framework handles registration and validation
• Unified error handling across all tools
• Pluggable auth (none, jwt, oauth)
• Swappable storage backends: in-memory, filesystem, Supabase, Cloudflare KV/R2/D1
• Structured logging with optional OpenTelemetry tracing
• STDIO and Streamable HTTP transports

WSDOT-specific:

• Dual API integration — WSDOT Traffic API and WSF Ferry API from a single access code
• Retry, timeout, and HTML-detection guards on all upstream requests
• Normalized response shapes across both APIs — sparse upstream fields surfaced as optional rather than omitted

Agent-friendly output:

• Cross-tool linking built into descriptions — ferry tools document which tool to call first for terminal and route ID resolution
• DriveUpSpaceCount: 0 and congestion delta fields give agents actionable signal without string parsing
• Partial data preserved — sparse upstream payloads surface null/undefined rather than synthetic defaults

Add the following to your MCP client configuration file. You'll need a WSDOT Traveler API access code — register at wsdot.wa.gov/Traffic/api/.

{
  "mcpServers": {
    "wsdot-mcp-server": {
      "type": "stdio",
      "command": "bunx",
      "args": ["@cyanheads/wsdot-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio",
        "MCP_LOG_LEVEL": "info",
        "WSDOT_ACCESS_CODE": "your-access-code"
      }
    }
  }
}

Or with npx (no Bun required):

{
  "mcpServers": {
    "wsdot-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@cyanheads/wsdot-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio",
        "MCP_LOG_LEVEL": "info",
        "WSDOT_ACCESS_CODE": "your-access-code"
      }
    }
  }
}

Or with Docker:

{
  "mcpServers": {
    "wsdot-mcp-server": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "MCP_TRANSPORT_TYPE=stdio",
        "-e", "WSDOT_ACCESS_CODE=your-access-code",
        "ghcr.io/cyanheads/wsdot-mcp-server:latest"
      ]
    }
  }
}

For Streamable HTTP, set the transport and start the server:

MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 WSDOT_ACCESS_CODE=your-access-code bun run start:http
# Server listens at http://localhost:3010/mcp

• Bun v1.3.0 or higher (or Node.js v24+).
• A WSDOT Traveler API access code. Register at wsdot.wa.gov/Traffic/api/ — registration is free.

1. Clone the repository:

git clone https://github.com/cyanheads/wsdot-mcp-server.git

2. Navigate into the directory:

cd wsdot-mcp-server

3. Install dependencies:

bun install

4. Configure environment:

cp .env.example .env
# edit .env and set WSDOT_ACCESS_CODE

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

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

• Build and run:

  # One-time build
  bun run rebuild
  
  # Run the built server
  bun run start:stdio
  # or
  bun run start:http

• Run checks and tests:

  bun run devcheck   # Lint, format, typecheck, security
  bun run test       # Vitest test suite
  bun run lint:mcp   # Validate MCP definitions against spec

docker build -t wsdot-mcp-server .
docker run --rm -e WSDOT_ACCESS_CODE=your-access-code -p 3010:3010 wsdot-mcp-server

The Dockerfile defaults to HTTP transport, stateless session mode, and logs to /var/log/wsdot-mcp-server. OpenTelemetry peer dependencies are installed by default — build with --build-arg OTEL_ENABLED=false to omit them.

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

Issues and pull requests are welcome. Run checks and tests before submitting:

bun run devcheck
bun run test

Apache-2.0 — see LICENSE for details.