wsdot-mcp-server 0.1.1

package/README.md

@@ -0,0 +1,364 @@
+<div align="center">
+  <h1>wsdot-mcp-server</h1>
+  <p><b>Query WA highway conditions, ferry schedules, vessel locations, toll rates, border waits, and alerts via MCP. STDIO or Streamable HTTP.</b>
+  <div>12 Tools</div>
+  </p>
+</div>
+
+<div align="center">
+
+[![Version](https://img.shields.io/badge/Version-0.1.1-blue.svg?style=flat-square)](./CHANGELOG.md) [![License](https://img.shields.io/badge/License-Apache%202.0-orange.svg?style=flat-square)](./LICENSE) [![Docker](https://img.shields.io/badge/Docker-ghcr.io-2496ED?style=flat-square&logo=docker&logoColor=white)](https://github.com/users/cyanheads/packages/container/package/wsdot-mcp-server) [![MCP SDK](https://img.shields.io/badge/MCP%20SDK-^1.29.0-green.svg?style=flat-square)](https://modelcontextprotocol.io/) [![npm](https://img.shields.io/npm/v/wsdot-mcp-server?style=flat-square&logo=npm&logoColor=white)](https://www.npmjs.com/package/wsdot-mcp-server) [![TypeScript](https://img.shields.io/badge/TypeScript-^5.9.3-3178C6.svg?style=flat-square)](https://www.typescriptlang.org/) [![Bun](https://img.shields.io/badge/Bun-v1.3.0+-blueviolet.svg?style=flat-square)](https://bun.sh/)
+
+</div>
+
+<div align="center">
+
+[![Install in Claude Desktop](https://img.shields.io/badge/Install_in-Claude_Desktop-D97757?style=for-the-badge&logo=anthropic&logoColor=white)](https://github.com/cyanheads/wsdot-mcp-server/releases/latest/download/wsdot-mcp-server.mcpb) [![Install in Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=wsdot-mcp-server&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIndzZG90LW1jcC1zZXJ2ZXIiXSwiZW52Ijp7IldTRE9UX0FDQ0VTU19DT0RFIjoieW91ci1hY2Nlc3MtY29kZSJ9fQ==) [![Install in VS Code](https://img.shields.io/badge/VS_Code-Install_Server-0098FF?style=for-the-badge&logo=visualstudiocode&logoColor=white)](https://vscode.dev/redirect?url=vscode:mcp/install?%7B%22name%22%3A%22wsdot-mcp-server%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22wsdot-mcp-server%22%5D%2C%22env%22%3A%7B%22WSDOT_ACCESS_CODE%22%3A%22your-access-code%22%7D%7D)
+
+[![Framework](https://img.shields.io/badge/Built%20on-@cyanheads/mcp--ts--core-67E8F9?style=flat-square)](https://www.npmjs.com/package/@cyanheads/mcp-ts-core)
+
+</div>
+
+---
+
+## Tools
+
+12 tools split across two domains — traffic (WSDOT Traveler API) and ferries (WSF Ferry API):
+
+| Tool | Description |
+|:---|:---|
+| `wsdot_get_mountain_passes` | Current conditions for all WA mountain passes: status, road condition, traction laws, temperature, elevation. |
+| `wsdot_search_alerts` | Active highway alerts — incidents, construction, closures — filterable by state route, WSDOT region, and milepost range. |
+| `wsdot_get_travel_times` | Current vs. average travel times for named WA highway corridors (I-5, I-90, SR 520, etc.) with congestion delay. |
+| `wsdot_get_toll_rates` | Dynamic toll rates for WA express lanes and tolled facilities: SR 99, SR 520, I-405, I-90 Two-Way, SR 167 HOT. |
+| `wsdot_get_border_waits` | Current vehicle wait times at all WA/Canada land border crossings. |
+| `wsdot_search_cameras` | Highway camera metadata and image URLs, filterable by state route, region, and milepost range. |
+| `wsdot_get_ferry_terminals` | All WSF ferry terminals with numeric IDs needed for schedule and space lookups. |
+| `wsdot_get_ferry_routes` | WSF routes operating on a given date with terminal ID pairs and crossing times. |
+| `wsdot_get_ferry_schedule` | Departure times for a specific WSF route — today-remaining or full-day future mode. |
+| `wsdot_get_vessel_locations` | Real-time AIS positions, speed, heading, ETA, and dock status for all active WSF vessels. |
+| `wsdot_get_terminal_space` | Drive-up and reservable vehicle space available at WSF terminals for upcoming sailings. |
+| `wsdot_get_ferry_alerts` | Active WSF service disruptions and bulletins with impacted route IDs. |
+
+### `wsdot_get_mountain_passes`
+
+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
+
+---
+
+### `wsdot_search_alerts`
+
+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
+
+---
+
+### `wsdot_get_travel_times`
+
+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
+
+---
+
+### `wsdot_get_toll_rates`
+
+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
+
+---
+
+### `wsdot_get_border_waits`
+
+Current vehicle wait times at WA/Canada land border crossings.
+
+- Covers Peace Arch (Blaine), Pacific Highway (Blaine), Sumas, Lynden, Oroville, and others
+- Wait times in minutes; `updateTime` shows when the reading was last updated
+
+---
+
+### `wsdot_search_cameras`
+
+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
+
+---
+
+### `wsdot_get_ferry_terminals`
+
+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`
+
+---
+
+### `wsdot_get_ferry_routes`
+
+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
+
+---
+
+### `wsdot_get_ferry_schedule`
+
+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
+
+---
+
+### `wsdot_get_vessel_locations`
+
+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
+
+---
+
+### `wsdot_get_terminal_space`
+
+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
+
+---
+
+### `wsdot_get_ferry_alerts`
+
+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
+
+---
+
+## Features
+
+Built on [`@cyanheads/mcp-ts-core`](https://www.npmjs.com/package/@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
+
+## Getting started
+
+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/](https://wsdot.wa.gov/Traffic/api/).
+
+```json
+{
+  "mcpServers": {
+    "wsdot": {
+      "type": "stdio",
+      "command": "bunx",
+      "args": ["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):
+
+```json
+{
+  "mcpServers": {
+    "wsdot": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "wsdot-mcp-server@latest"],
+      "env": {
+        "MCP_TRANSPORT_TYPE": "stdio",
+        "MCP_LOG_LEVEL": "info",
+        "WSDOT_ACCESS_CODE": "your-access-code"
+      }
+    }
+  }
+}
+```
+
+Or with Docker:
+
+```json
+{
+  "mcpServers": {
+    "wsdot": {
+      "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:
+
+```sh
+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
+```
+
+### Prerequisites
+
+- [Bun v1.3.0](https://bun.sh/) or higher (or Node.js v24+).
+- A WSDOT Traveler API access code. Register at [wsdot.wa.gov/Traffic/api/](https://wsdot.wa.gov/Traffic/api/) — registration is free.
+
+### Installation
+
+1. **Clone the repository:**
+
+```sh
+git clone https://github.com/cyanheads/wsdot-mcp-server.git
+```
+
+2. **Navigate into the directory:**
+
+```sh
+cd wsdot-mcp-server
+```
+
+3. **Install dependencies:**
+
+```sh
+bun install
+```
+
+4. **Configure environment:**
+
+```sh
+cp .env.example .env
+# edit .env and set WSDOT_ACCESS_CODE
+```
+
+## Configuration
+
+All configuration is validated at startup via Zod schemas in `src/config/server-config.ts`. Key environment variables:
+
+| Variable | Description | Default |
+|:---|:---|:---|
+| `WSDOT_ACCESS_CODE` | **Required.** WSDOT Traveler API access code. Register at [wsdot.wa.gov/Traffic/api/](https://wsdot.wa.gov/Traffic/api/). | — |
+| `MCP_TRANSPORT_TYPE` | Transport: `stdio` or `http`. | `stdio` |
+| `MCP_HTTP_PORT` | HTTP server port. | `3010` |
+| `MCP_HTTP_HOST` | HTTP server hostname. | `127.0.0.1` |
+| `MCP_HTTP_ENDPOINT_PATH` | HTTP endpoint path. | `/mcp` |
+| `MCP_PUBLIC_URL` | Public origin for TLS-terminating reverse-proxy deployments. | — |
+| `MCP_AUTH_MODE` | Authentication: `none`, `jwt`, or `oauth`. | `none` |
+| `MCP_LOG_LEVEL` | Log level (`debug`, `info`, `notice`, `warning`, `error`). | `info` |
+| `LOGS_DIR` | Directory for log files (Node.js only). | `<project-root>/logs` |
+| `STORAGE_PROVIDER_TYPE` | Storage backend: `in-memory`, `filesystem`, `supabase`, `cloudflare-kv/r2/d1`. | `in-memory` |
+| `OTEL_ENABLED` | Enable OpenTelemetry instrumentation (spans, metrics, completion logs). | `false` |
+
+See [`.env.example`](./.env.example) for the full list of optional overrides.
+
+## Running the server
+
+### Local development
+
+- **Build and run:**
+
+  ```sh
+  # One-time build
+  bun run rebuild
+
+  # Run the built server
+  bun run start:stdio
+  # or
+  bun run start:http
+  ```
+
+- **Run checks and tests:**
+
+  ```sh
+  bun run devcheck   # Lint, format, typecheck, security
+  bun run test       # Vitest test suite
+  bun run lint:mcp   # Validate MCP definitions against spec
+  ```
+
+### Docker
+
+```sh
+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.
+
+## Project structure
+
+| Directory | Purpose |
+|:---|:---|
+| `src/index.ts` | `createApp()` entry point — registers all 12 tools and initializes services. |
+| `src/config` | Server-specific environment variable parsing and validation with Zod. |
+| `src/mcp-server/tools` | Tool definitions (`*.tool.ts`) — 6 traffic tools, 6 ferry tools. |
+| `src/services/traffic` | WSDOT Traffic API service (mountain passes, alerts, travel times, toll rates, border waits, cameras). |
+| `src/services/ferry` | WSF Ferry API service (terminals, routes, schedule, vessel locations, space, alerts). |
+| `tests/` | Unit and integration tests, mirroring the `src/` structure. |
+
+## Development guide
+
+See [`CLAUDE.md`](./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 and pull requests are welcome. Run checks and tests before submitting:
+
+```sh
+bun run devcheck
+bun run test
+```
+
+## License
+
+Apache-2.0 — see [LICENSE](./LICENSE) for details.

package/changelog/0.1.x/0.1.0.md

@@ -0,0 +1,24 @@
+---
+summary: "Initial release — 12 WSDOT tools for WA traffic and WSF ferry data"
+breaking: false
+security: false
+---
+
+# 0.1.0 — 2026-05-23
+
+## Added
+
+- **`wsdot_get_mountain_passes`** — current conditions for all WA mountain passes (status, road condition, traction laws, temperature, elevation).
+- **`wsdot_search_alerts`** — active highway alerts, incidents, and construction notices; filterable by state route, WSDOT region, and milepost range.
+- **`wsdot_get_travel_times`** — current vs. average travel times for named WA highway corridors (I-5, I-90, SR 520, etc.) with congestion delay calculation.
+- **`wsdot_get_toll_rates`** — dynamic toll rates for WA express lanes and tolled facilities (SR 99, SR 520, I-405, I-90, SR 167).
+- **`wsdot_get_border_waits`** — vehicle wait times at all WA/Canada land border crossings.
+- **`wsdot_search_cameras`** — highway camera metadata and image URLs; filterable by state route, region, and milepost range.
+- **`wsdot_get_ferry_terminals`** — all WSF ferry terminals with numeric IDs for use in schedule and space lookups.
+- **`wsdot_get_ferry_routes`** — WSF routes operating on a given date with terminal ID pairs and crossing times.
+- **`wsdot_get_ferry_schedule`** — departure times for a specific WSF route; supports today-remaining and future-date modes.
+- **`wsdot_get_vessel_locations`** — real-time AIS positions, speed, heading, ETA, and dock status for all active WSF vessels.
+- **`wsdot_get_terminal_space`** — drive-up and reservable vehicle space availability for upcoming WSF sailings.
+- **`wsdot_get_ferry_alerts`** — active WSF service disruptions with impacted route IDs.
+- Traffic service (`TrafficApiService`) and ferry service (`FerryApiService`) with retry, timeout, and HTML-detection guards.
+- 64 tests covering all 12 tools: happy paths, filter behavior, format output, sparse upstream payloads.

package/changelog/0.1.x/0.1.1.md

@@ -0,0 +1,26 @@
+---
+summary: "WSDOT Traveler Information — 12 tools for WA traffic, ferries, mountain passes, toll rates, and border crossings"
+breaking: false
+security: false
+---
+
+# 0.1.1 — 2026-05-23
+
+Initial public release of wsdot-mcp-server, built on `@cyanheads/mcp-ts-core ^0.9.7`.
+
+## Added
+
+- **`wsdot_get_mountain_passes`** — current conditions for all WA mountain passes (status, road condition, traction laws, temperature, elevation).
+- **`wsdot_search_alerts`** — active highway alerts, incidents, and construction notices; filterable by state route, WSDOT region, and milepost range.
+- **`wsdot_get_travel_times`** — current vs. average travel times for named WA highway corridors (I-5, I-90, SR 520, etc.) with congestion delay.
+- **`wsdot_get_toll_rates`** — dynamic toll rates for WA express lanes and tolled facilities (SR 99, SR 520, I-405, I-90, SR 167).
+- **`wsdot_get_border_waits`** — vehicle wait times at all WA/Canada land border crossings.
+- **`wsdot_search_cameras`** — highway camera metadata and image URLs; filterable by state route, region, and milepost range.
+- **`wsdot_get_ferry_terminals`** — all WSF ferry terminals with numeric IDs for schedule and space lookups.
+- **`wsdot_get_ferry_routes`** — WSF routes operating on a given date with terminal ID pairs and crossing times.
+- **`wsdot_get_ferry_schedule`** — departure times for a specific WSF route; supports today-remaining and future-date modes.
+- **`wsdot_get_vessel_locations`** — real-time AIS positions, speed, heading, ETA, and dock status for all active WSF vessels.
+- **`wsdot_get_terminal_space`** — drive-up and reservable vehicle space availability for upcoming WSF sailings.
+- **`wsdot_get_ferry_alerts`** — active WSF service disruptions with impacted route IDs.
+- Traffic service (`TrafficApiService`) and ferry service (`FerryApiService`) with retry, timeout, and HTML-detection guards.
+- 64 tests covering all 12 tools: happy paths, filter behavior, format output, sparse upstream payloads.

package/changelog/template.md

@@ -0,0 +1,119 @@
+---
+# FORMAT REFERENCE — do not edit. Copy this file to
+# `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.8.x/0.8.6.md`)
+# to author a new release. Set that file's H1 to `# <version> — YYYY-MM-DD`
+# with a concrete date.
+
+# Required. One-line GitHub Release-style headline. 350 character cap.
+# Default short and scannable. Don't pad, don't stitch unrelated changes with
+# semicolons — pick the headline. Quotes required: unquoted YAML treats `: `
+# inside the value as a key separator and fails GitHub's strict parser.
+summary: ""
+
+# Set `true` when consumers must change code to upgrade: API removals,
+# signature changes, config renames, behavior changes that break existing
+# usage. Flagged as `Breaking` in the rollup.
+breaking: false
+
+# Set `true` if this release contains any security fix. Pairs with the
+# `## Security` section below. Flagged as `Security` in the rollup so
+# users can triage upgrade urgency at a glance.
+security: false
+---
+
+# <version> — YYYY-MM-DD
+
+<!--
+  AUTHORING GUIDE — applies to the new per-version file you create from this
+  template.
+
+  Audience: someone scanning release notes to decide what affects them. Lead
+  each bullet with the symbol or concept name in **bold** so they can skip
+  what's irrelevant and zoom in on what's not.
+
+  Tone: terse, fact-dense, not verbose. Default to one sentence per bullet —
+  name the symbol, state what changed, stop. Use a second sentence only when
+  it carries weight. If a bullet feels long, it is.
+
+  Cut: mechanism walkthroughs (those belong in JSDoc, AGENTS.md, or the
+  relevant skill), ceremonial framings ("This release introduces…",
+  backwards-compat paragraphs), file-by-file test enumerations, internal
+  implementation notes. Prefer code/symbol names over English re-explanations.
+
+  Narrative intro: skip by default. Add one short sentence only when the
+  release theme genuinely needs framing the bullets can't carry.
+
+  Sections: Keep a Changelog order — Added, Changed, Deprecated, Removed,
+  Fixed, Security. Include only sections with entries; delete the rest
+  (including the commented-out scaffolding below). Don't ship empty headers.
+
+  Include: every distinct fact a reader needs to adopt or audit the release —
+  new exports, signatures, lint rule IDs, env vars, breaking changes, version
+  bumps on shipped skills. Nothing more.
+
+  Links: link issues, PRs, docs, or skills where they help a reader jump to
+  context. Once per item per entry — don't re-link the same issue in summary,
+  narrative, and bullet. Skip links for inline symbol names; code spans speak
+  for themselves.
+
+  Issue/PR URLs: use full URLs. GitHub's bare `#NN` auto-link only resolves
+  inside its own UI, not in npm reads or local editors.
+
+      [#38](https://github.com/cyanheads/mcp-ts-core/issues/38)   ← issue
+      [#42](https://github.com/cyanheads/mcp-ts-core/pull/42)     ← PR
+
+  Verify numbers exist before linking (`gh issue view NN`, `gh pr view NN`).
+  Never speculate on a future number — `#42` for an upcoming PR silently
+  resolves to whatever real item already owns 42, and timeline previews pull
+  in that unrelated item's metadata.
+
+  TAG ANNOTATIONS — the annotated tag body renders as the GitHub Release body
+  via `gh release create --notes-from-tag`. The tag is a derivative of this
+  changelog entry — a condensed, scannable version, not a copy. Format:
+
+    <theme — omit version number, GitHub prepends it>
+                                                          ← blank line
+    <1-2 sentence context: what this release does>
+                                                          ← blank line
+    Dependency bumps:                                     ← section header
+                                                          ← blank line
+    - `@cyanheads/mcp-ts-core` ^0.9.1 → ^0.9.6          ← bullet
+                                                          ← blank line
+    Changed:                                              ← only sections with entries
+                                                          ← blank line
+    - `format()` output includes `query` in text mode
+                                                          ← blank line
+    Added:
+                                                          ← blank line
+    - `manifest.json` scaffolded for MCPB bundle support
+    - Install badges (Claude Desktop, Cursor, VS Code)
+                                                          ← blank line
+    <N> tests pass; `bun run devcheck` clean.             ← footer
+
+  Never a flat comma-separated string. Always structured markdown with
+  sections. The tag must scan well as a rendered GitHub Release page.
+-->
+
+## Added
+
+-
+
+## Changed
+
+-
+
+<!-- ## Deprecated
+
+- -->
+
+<!-- ## Removed
+
+- -->
+
+## Fixed
+
+-
+
+<!-- ## Security
+
+- -->

package/dist/config/server-config.d.ts

@@ -0,0 +1,12 @@
+/**
+ * @fileoverview Server-specific environment variable configuration for wsdot-mcp-server.
+ * @module config/server-config
+ */
+import { z } from '@cyanheads/mcp-ts-core';
+declare const ServerConfigSchema: z.ZodObject<{
+    accessCode: z.ZodString;
+}, z.core.$strip>;
+export type ServerConfig = z.infer<typeof ServerConfigSchema>;
+export declare function getServerConfig(): ServerConfig;
+export {};
+//# sourceMappingURL=server-config.d.ts.map

package/dist/config/server-config.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"server-config.d.ts","sourceRoot":"","sources":["../../src/config/server-config.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,wBAAwB,CAAC;AAG3C,QAAA,MAAM,kBAAkB;;iBAItB,CAAC;AAEH,MAAM,MAAM,YAAY,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,kBAAkB,CAAC,CAAC;AAI9D,wBAAgB,eAAe,IAAI,YAAY,CAK9C"}

package/dist/config/server-config.js

@@ -0,0 +1,19 @@
+/**
+ * @fileoverview Server-specific environment variable configuration for wsdot-mcp-server.
+ * @module config/server-config
+ */
+import { z } from '@cyanheads/mcp-ts-core';
+import { parseEnvConfig } from '@cyanheads/mcp-ts-core/config';
+const ServerConfigSchema = z.object({
+    accessCode: z
+        .string()
+        .describe('WSDOT Traveler API access code. Used for both traffic and ferry endpoints.'),
+});
+let _config;
+export function getServerConfig() {
+    _config ??= parseEnvConfig(ServerConfigSchema, {
+        accessCode: 'WSDOT_ACCESS_CODE',
+    });
+    return _config;
+}
+//# sourceMappingURL=server-config.js.map

package/dist/config/server-config.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"server-config.js","sourceRoot":"","sources":["../../src/config/server-config.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,wBAAwB,CAAC;AAC3C,OAAO,EAAE,cAAc,EAAE,MAAM,+BAA+B,CAAC;AAE/D,MAAM,kBAAkB,GAAG,CAAC,CAAC,MAAM,CAAC;IAClC,UAAU,EAAE,CAAC;SACV,MAAM,EAAE;SACR,QAAQ,CAAC,4EAA4E,CAAC;CAC1F,CAAC,CAAC;AAIH,IAAI,OAAiC,CAAC;AAEtC,MAAM,UAAU,eAAe;IAC7B,OAAO,KAAK,cAAc,CAAC,kBAAkB,EAAE;QAC7C,UAAU,EAAE,mBAAmB;KAChC,CAAC,CAAC;IACH,OAAO,OAAO,CAAC;AACjB,CAAC"}

package/dist/index.d.ts

@@ -0,0 +1,7 @@
+#!/usr/bin/env node
+/**
+ * @fileoverview wsdot-mcp-server MCP server entry point.
+ * @module index
+ */
+export {};
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;GAGG"}

package/dist/index.js

@@ -0,0 +1,33 @@
+#!/usr/bin/env node
+/**
+ * @fileoverview wsdot-mcp-server MCP server entry point.
+ * @module index
+ */
+import { createApp } from '@cyanheads/mcp-ts-core';
+import { getBorderWaits, getFerryAlerts, getFerryRoutes, getFerrySchedule, getFerryTerminals, getMountainPasses, getTerminalSpace, getTollRates, getTravelTimes, getVesselLocations, searchAlerts, searchCameras, } from './mcp-server/tools/definitions/index.js';
+import { initFerryApiService } from './services/ferry/ferry-service.js';
+import { initTrafficApiService } from './services/traffic/traffic-service.js';
+await createApp({
+    tools: [
+        getMountainPasses,
+        searchAlerts,
+        getTravelTimes,
+        getTollRates,
+        getBorderWaits,
+        searchCameras,
+        getFerryTerminals,
+        getFerryRoutes,
+        getFerrySchedule,
+        getVesselLocations,
+        getTerminalSpace,
+        getFerryAlerts,
+    ],
+    resources: [],
+    prompts: [],
+    instructions: 'WSDOT Traveler Information server for Washington State. Traffic tools (mountain passes, alerts, travel times, toll rates, border waits, cameras) use the WSDOT Traffic API. Ferry tools use the WSF Ferry API. For ferry schedule and space lookups, first call wsdot_get_ferry_terminals to resolve terminal names to numeric IDs. Ferry route IDs from wsdot_get_ferry_routes correspond to impactedRouteIds in wsdot_get_ferry_alerts.',
+    setup(core) {
+        initTrafficApiService(core.config, core.storage);
+        initFerryApiService(core.config, core.storage);
+    },
+});
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;GAGG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,wBAAwB,CAAC;AACnD,OAAO,EACL,cAAc,EACd,cAAc,EACd,cAAc,EACd,gBAAgB,EAChB,iBAAiB,EACjB,iBAAiB,EACjB,gBAAgB,EAChB,YAAY,EACZ,cAAc,EACd,kBAAkB,EAClB,YAAY,EACZ,aAAa,GACd,MAAM,yCAAyC,CAAC;AACjD,OAAO,EAAE,mBAAmB,EAAE,MAAM,mCAAmC,CAAC;AACxE,OAAO,EAAE,qBAAqB,EAAE,MAAM,uCAAuC,CAAC;AAE9E,MAAM,SAAS,CAAC;IACd,KAAK,EAAE;QACL,iBAAiB;QACjB,YAAY;QACZ,cAAc;QACd,YAAY;QACZ,cAAc;QACd,aAAa;QACb,iBAAiB;QACjB,cAAc;QACd,gBAAgB;QAChB,kBAAkB;QAClB,gBAAgB;QAChB,cAAc;KACf;IACD,SAAS,EAAE,EAAE;IACb,OAAO,EAAE,EAAE;IACX,YAAY,EACV,2aAA2a;IAC7a,KAAK,CAAC,IAAI;QACR,qBAAqB,CAAC,IAAI,CAAC,MAAM,EAAE,IAAI,CAAC,OAAO,CAAC,CAAC;QACjD,mBAAmB,CAAC,IAAI,CAAC,MAAM,EAAE,IAAI,CAAC,OAAO,CAAC,CAAC;IACjD,CAAC;CACF,CAAC,CAAC"}

package/dist/mcp-server/tools/definitions/get-border-waits.tool.d.ts

@@ -0,0 +1,28 @@
+/**
+ * @fileoverview Tool to fetch Canada border crossing wait times from the WSDOT Traffic API.
+ * @module mcp-server/tools/definitions/get-border-waits.tool
+ */
+import { z } from '@cyanheads/mcp-ts-core';
+import { JsonRpcErrorCode } from '@cyanheads/mcp-ts-core/errors';
+export declare const getBorderWaits: import("@cyanheads/mcp-ts-core").ToolDefinition<z.ZodObject<{}, z.core.$strip>, z.ZodObject<{
+    crossings: z.ZodArray<z.ZodObject<{
+        crossingName: z.ZodOptional<z.ZodString>;
+        waitTimeInMinutes: z.ZodOptional<z.ZodNumber>;
+        updateTime: z.ZodOptional<z.ZodString>;
+        location: z.ZodOptional<z.ZodObject<{
+            roadName: z.ZodOptional<z.ZodString>;
+            direction: z.ZodOptional<z.ZodString>;
+            milePost: z.ZodOptional<z.ZodNumber>;
+            latitude: z.ZodOptional<z.ZodNumber>;
+            longitude: z.ZodOptional<z.ZodNumber>;
+        }, z.core.$strip>>;
+    }, z.core.$strip>>;
+    totalCount: z.ZodNumber;
+}, z.core.$strip>, readonly [{
+    readonly reason: "api_unavailable";
+    readonly code: JsonRpcErrorCode.ServiceUnavailable;
+    readonly when: "WSDOT Traffic API is unreachable or returns a non-2xx response after retries.";
+    readonly retryable: true;
+    readonly recovery: "Retry in 30 seconds. If the issue persists, check wsdot.wa.gov for service status.";
+}]>;
+//# sourceMappingURL=get-border-waits.tool.d.ts.map

package/dist/mcp-server/tools/definitions/get-border-waits.tool.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"get-border-waits.tool.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/tools/definitions/get-border-waits.tool.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAQ,CAAC,EAAE,MAAM,wBAAwB,CAAC;AACjD,OAAO,EAAE,gBAAgB,EAAE,MAAM,+BAA+B,CAAC;AAGjE,eAAO,MAAM,cAAc;;;;;;;;;;;;;;;;;;;;GA4EzB,CAAC"}