
Wsdot Mcp Server
Wire Washington State travel data—highways, ferries, tolls, border waits—into agent-built apps and assistants for Pacific Northwest users.
Overview
WSDOT MCP Server is a MCP server for the Build phase that exposes Washington highway, ferry, toll, and border-wait traveler data to coding agents.
What is this MCP server?
- Highway conditions, ferry schedules, vessel locations, toll rates, and border wait times
- Hosted streamable-http at wsdot.caseyjhand.com/mcp plus local stdio via @cyanheads/wsdot-mcp-server
- Requires WSDOT_ACCESS_CODE from wsdot.wa.gov/Traffic/api registration
- Optional local streamable-http on http://localhost:3010/mcp
- MCP_LOG_LEVEL for debug through warn output control
- Five capability areas: highways, ferries, vessels, tolls, border waits
- Package version 0.1.9
- Default local HTTP MCP port 3010 when self-hosting
Community signal: 1 GitHub stars.
What problem does it solve?
Building a Northwest travel feature means hunting WSDOT API docs and access codes instead of letting your agent fetch live conditions in one call.
Who is it for?
Indie builders shipping commute, ferry, or cross-border products aimed at Washington residents and visitors.
Skip if: Builders outside WSDOT coverage who need national traffic or who cannot obtain a Traveler API access code.
What do I get? / Deliverables
After registration and MCP install, agents can pull ferry positions, road alerts, and border waits into your app code or support flows.
- Agent-callable WSDOT highway, ferry, toll, and border endpoints
- Faster WA-specific feature prototyping without bespoke API glue per resource
Recommended MCP Servers
Journey fit
Integration-focused MCP belongs in Build when you connect a product or internal tool to authoritative regional transportation APIs. Integrations subphase covers third-party API bridges; WSDOT Traveler API access code unlocks live conditions and schedules in one MCP surface.
How it compares
Regional transportation MCP integration, not a generic maps skill or World Bank macro dataset.
Common Questions / FAQ
Who is WSDOT MCP Server for?
Developers using AI agents to integrate official Washington DOT traveler feeds into apps, chatbots, or ops dashboards.
When should I use WSDOT MCP Server?
Use it while building backend or agent features that must show current WA highway conditions, ferry schedules, or Canadian border wait times.
How do I add WSDOT MCP Server to my agent?
Register at wsdot.wa.gov/Traffic/api for WSDOT_ACCESS_CODE, then add @cyanheads/wsdot-mcp-server stdio or https://wsdot.caseyjhand.com/mcp in your MCP settings.