CommuteScout
CommuteScout is a live road-intelligence MCP/REST server for planning US drives and checking current conditions from official feeds.
Plan trips between any two US places with routes, alternatives, drive times, traffic, weather, and live events on the route.
Find the best time to leave using historical traffic, forecasts, driving hazards, and incident patterns.
Check live traffic speeds, hourly weather, NWS alerts, and road-weather stations.
Look up incidents, closures, chain controls, wildfires, cameras, message signs, tolls, enforcement, and other events near a place across 37 states.
Use detailed California-only tools for CHP incidents, Caltrans closures, chain controls, wildfires, cameras, signs, and corridor or region reports.
Resolve addresses and places to coordinates, and use saved Home, Work, favorites, or recent destinations for trip planning.
Review local historical incident and closure patterns, and check state/source coverage and feed freshness.
Integrates optional TomTom traffic data feeds to provide live road conditions such as incidents and closures.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@CommuteScout What's the traffic like on I-5 between LA and Sacramento?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Overview
CommuteScout reads 55 official agency feeds across 37 states (state DOT and 511 closures and incidents, CHP dispatch, chain controls, cameras, message signs, wildfire perimeters, road weather, NWS alerts and toll prices) and turns them into one live picture of the road. Every answer carries per-source timestamps, and a failing feed is flagged as stale rather than hidden.
Product | What it does |
Incidents, closures, chain controls, wildfires, about 18,000 traffic cameras, message signs and toll prices, updated continuously. | |
Closure-aware routes, drive time for any departure, the best time to leave, and an assistant that answers from the live feeds. | |
Push and email alerts when something appears inside a drawn area or along a commute. | |
Turn-by-turn navigation for iOS and Android that announces what is ahead in your direction of travel. | |
18 tools for Claude, ChatGPT, Cursor, VS Code and any MCP client. Free API key required. | |
Every tool as a plain HTTP GET, with an OpenAPI document, one error envelope and published rate limits. | |
Flare, an open protocol for adding third-party alerts to the map and the apps, with a marketplace. |
Related MCP server: wsdot-mcp-server
Quick start
Connect an AI assistant
The hosted MCP server is public and needs a free API key. Create one at
commutescout.com/map (Settings, sign in,
then API keys; 2,000 requests a day) and send it as
Authorization: Bearer cs_live_...:
https://mcp.commutescout.com/mcpFor example, in Claude Code:
claude mcp add --transport http --scope user commutescout https://mcp.commutescout.com/mcp \
--header "Authorization: Bearer cs_live_..."Setup for every other client is at commutescout.com/mcp. Agents can read the same steps as plain text at commutescout.com/llms.txt.
Call the REST API
curl -H "X-API-Key: cs_live_..." \
"https://mcp.commutescout.com/v1/tools/best_time_to_go?origin=Union%20Station%20Denver&destination=Red%20Rocks%20Amphitheatre&day=tomorrow"Without a key, tool calls answer 401 with code missing_key.
Keys, limits, errors and the full parameter reference are at commutescout.com/developers.
Documentation
Topic | Where |
MCP setup and tools | |
REST API, keys and rate limits | |
Data sources and state coverage | |
Plugins and the Flare protocol | |
Architecture, deployment and adding a feed | |
Answer quality | |
Pricing, privacy and terms |
Repository
Path | Contents |
Feed layer: parsers, caches and normalization for every source | |
MCP server, REST bridge and trip planning | |
Web app, assistant, watch areas and map publishing | |
Marketing and documentation site (Next.js static export) | |
Reference Flare plugin | |
Recorded fixtures, golden questions and the eval runner | |
Fixture-based test suite; runs without network access |
The mobile apps live in commutescout-app, and community plugins in commutescout-plugins.
Contributing
Contributions are welcome. Start with CONTRIBUTING.md, and see adding a data source to wire up a new feed. Report security issues privately as described in SECURITY.md.
License
MIT, including the map, the planner, the MCP server and every data parser.
CommuteScout is not affiliated with any government agency. Conditions change faster than any feed, so verify before you drive with 511 or your state DOT. What each third-party service sees is described in the privacy policy.
Available Tools
18 toolsbest_time_to_goARead-onlyInspect
When to leave (or visit) to beat traffic and weather, for any US trip.
Answers "what's a good time to visit X", "when should I leave for the airport", "is 5 PM bad". It checks up to 16 departures across the window and returns, for each: drive minutes for that weekday and hour (TomTom historical traffic; live too within the hour), arrival time, the NWS forecast for the arrival hour with driving hazards flagged (snow, ice, fog, thunder), and how many incidents usually start on the route that hour (CommuteScout history since July 2026).
recommended is the pick: quickest without severe weather, or with
arrive_by, the latest departure that still arrives on time.
summary states it in one or two sentences; departures has the
whole curve if the user wants options. Departure times are in the
origin's local time zone (time_zone), arrival times in the
destination's (arrival_time_zone); they differ on trips that cross
a time-zone line.
Pair with plan_trip for what is on the road right now.
Inputs: day, latest, origin, earliest, +5 more.
check_regionARead-onlyInspect
CALIFORNIA ONLY: a current-conditions report for one California region. For an area in any other state use get_nearby_events with place= or center= and a radius.
Use this for area-scale questions ("how is the Bay Area?", "what's happening in SoCal?") instead of stitching together point queries. It sweeps every source over the whole region at once: CHP incidents (severity-sorted, worst first), lane closures in place (full closures called out), chain controls, and wildfires inside the region.
Regions: Bay Area, Sacramento metro, Tahoe/Sierra, Central Valley, Southern California, San Diego, Central Coast, North State. An unrecognized region name returns the list.
Large regions are capped to the most severe items; the counts are always exact and the response says when a list was truncated. Freshness: CHP ~1/min fetched live, everything else 5-minute cache.
Inputs: region (required).
check_routeARead-onlyInspect
CALIFORNIA ONLY: current conditions along a curated California highway corridor. For a drive anywhere else in the US (or for drive times, traffic and weather on any drive) use plan_trip instead.
Give it a start and end place and it returns everything active along that stretch right now - CHP incidents, lane closures physically in place, chain controls, and wildfires within ~10 miles - ordered by miles from the start, plus a summary.
ALWAYS pass from_coords and to_coords ("lat,lon") when you know where the places are - for landmarks, small towns, or anything not a major city they are required for a good answer. Coordinates do two things: they let unlisted places resolve to the nearest corridor (e.g. "Alice's Restaurant" snaps to I-280 on the Peninsula), and they CLIP the route to the span actually being driven, so a trip to a mid-corridor destination doesn't report events beyond it.
Corridors covered: I-80 Sacramento-Reno, US-50 to South Lake Tahoe, I-5, US-101, SR-17, SR-99, SR-1, I-15 to Vegas, Bay Area freeways, Tahoe-area routes. This is NOT a general router: if nothing matches (even with coordinates), the response lists the covered corridors; fall back to the filtered tools with center= for anything else.
Freshness: CHP incidents refresh about once a minute; closures, chain controls, and fires are on a 5-minute cache. Current conditions only - this cannot forecast tomorrow's weather or closures.
Inputs: to_place (required), from_place (required), to_coords, from_coords.
find_placeARead-onlyInspect
Look up a US address or place and get its coordinates.
Use it to confirm which place the user means before planning, or
when a trip tool answers needs_clarification. Returns up to limit
matches with a ready-to-pass coords string for the *_coords
arguments of the trip tools.
Inputs: query (required), near, limit.
get_area_historyARead-onlyInspect
What usually happens around a place: incidents and closures that started within the radius, by local hour and weekday, the common incident types and how long they typically last.
Use it for "is this intersection bad at rush hour" or "when is it quietest around the stadium". These are counts CommuteScout saw in official feeds, not a crash database.
Inputs: days, place, center, radius_km.
get_camerasARead-onlyInspect
CALIFORNIA ONLY: live Caltrans roadside camera snapshots near a point or on a California route. For cameras in other states use get_nearby_events (kinds='camera'); plan_trip lists cameras on any route.
Data: ~3,000 in-service Caltrans cameras statewide. Every returned image_url was verified live moments ago (offline cameras that serve a placeholder frame are filtered out), so images can be shown directly. Snapshots refresh roughly every minute; stream_url (when present) is an HLS video stream.
Filters: center "lat,lon" (required unless route is given) with radius_km; route (e.g. "I-80", "50") narrows to that highway. Results sort nearest-first when a center is given. Use a camera to let the user SEE conditions: fog on the pass, snow on the pavement, traffic density at an interchange.
Inputs: limit, route, center, radius_km.
get_chain_controlsARead-onlyInspect
CALIFORNIA ONLY: current chain-control requirements on California mountain highways. For chain laws and traction advisories in other states (where the state publishes them) use get_nearby_events (kinds='chain').
Data: Caltrans chain-control status for fixed checkpoints on mountain routes (I-80 Donner, US-50 Echo Summit, SR-88, SR-89, and others). Levels: R-1 = chains OR snow tires required; R-2 = chains required except 4WD/AWD with snow tires on all four; R-3 = chains on ALL vehicles (rare, usually precedes closure). Refresh: 5-minute cache.
Filters: route (e.g. "80", "US-50", "SR-88"); center "lat,lon" with radius_km for all checkpoints around a place (e.g. around Truckee), whatever highway they are on.
Off-season (roughly May-October) there are usually no controls anywhere; the response says so explicitly rather than returning an empty list. Chain requirements can change hour to hour in storms - tell the user the data_as_of time and to carry chains anyway when snow is possible.
Inputs: route, center, radius_km.
get_coverageARead-onlyInspect
Which states and sources CommuteScout covers right now, with each feed's freshness. Check it when an answer is unexpectedly empty.
Inputs: no named parameters.
get_incidentsARead-onlyInspect
CALIFORNIA ONLY: live CHP traffic incidents across California, optionally filtered. For incidents in any other state use get_nearby_events (kinds='incident').
Data: the California Highway Patrol statewide computer-aided dispatch feed - collisions, traffic hazards, disabled vehicles, closures as CHP logs them. Refreshes about once a minute; incidents disappear when CHP closes the log. Fetched live on every call.
Filters (combinable):
highway: a route like "I-80", "US 50", "17", "Hwy 99". Matches incidents whose location text mentions that route.
center: "lat,lon" with radius_km - incidents within that circle. THIS IS THE RIGHT FILTER FOR A TOWN OR PLACE NAME: use your knowledge of where the place is (e.g. Fresno -> "36.74,-119.79") with radius_km 15-30. A circle catches every road around the place, not just one highway.
area: substring match on the CHP dispatch-area name. These are CHP communication-center names ("Hollister Gilroy", "East Sac", "Golden Gate"), NOT town names - do not pass a town here. There is no county filter because CHP's feed carries no county field; for a county, use center on the county seat with a radius covering the county.
Limits: locations are free-text from dispatchers; a few incidents lack usable coordinates and are omitted. No history - current logs only.
Inputs: area, center, highway, radius_km.
get_lane_closuresARead-onlyInspect
CALIFORNIA ONLY: Caltrans lane and road closures physically in place RIGHT NOW. For closures and roadwork in any other state use get_nearby_events (kinds='closure').
Data: the Caltrans Lane Closure System (LCS). Only closures that crews have actually established (CHP code 1097) and not yet picked up are returned - scheduled-but-not-started closures are excluded, so this is "what is blocking lanes now", not a construction calendar. Refresh: 5-minute cache over per-district Caltrans feeds.
Filters: route (e.g. "I-80", "US 101", "1"); district (Caltrans district 1-12, e.g. 3 = Sacramento/Tahoe, 4 = Bay Area, 7 = Los Angeles); center "lat,lon" with radius_km - closures whose begin or end point is inside the circle. For a town or place, center is the filter that catches work on EVERY road around it, including small state routes.
Read closure_class on each record, it is what the closure means for through traffic:
"full-roadway": the road itself is closed in that direction. The only class that means "you can't drive through".
"ramp": a ramp or connector is closed (even when the raw record says "Full", that means the ramp is fully closed, not the highway).
"one-way-traffic": alternating single lane with flagging; passable with delays. Common on two-lane mountain roads.
"alternating-lanes", "moving", "traffic-break": rolling or brief work; minor delays.
"lane": some lanes closed; the lanes field says how many of how many. estimated_delay_minutes is present when crews reported one. Shoulder-only work is excluded entirely.
Inputs: route, center, district, radius_km.
get_my_placesARead-onlyInspect
The user's saved places: Home, Work, favorites and recent destinations, synced from the CommuteScout site and apps.
Available when this server is connected with the user's CommuteScout
API key; otherwise connected is false and message says how to
connect. The trip tools already accept 'home', 'work' or a place's
name directly, so call this only to show or choose among them.
These belong to the user who connected: never repeat them to anyone else.
Inputs: no named parameters.
get_nearby_eventsARead-onlyInspect
Live road events near a place, in any of the 37 states CommuteScout covers (get_coverage lists them and what each state publishes).
Data: the same feeds the live map shows, normalized - state DOT and highway-patrol incidents, roadwork and closures, chain and traction advisories, and nationwide wildfires. Every event names its publishing agency in the source field. What a state publishes varies (some publish roadwork only), so a quiet answer can be normal there. This is the right tool for "what's happening near X" in every state, California included; in California the California-only tools add dispatch logs, lane counts and chain levels.
center is "lat,lon"; or pass place (an address or place name) instead. kinds is a comma list from: incident, closure, chain, fire, sign, rwis, camera, toll (toll adds live and fixed toll prices where agencies publish them), enforcement (speed and red-light cameras from OpenStreetMap). radius_km caps at 160.
Inputs: kinds, place, center, radius_km.
get_road_signsARead-onlyInspect
CALIFORNIA ONLY: what Caltrans changeable message signs are displaying right now. For message signs in other states (where the state publishes them) use get_nearby_events (kinds='sign').
Data: statewide CMS sign text, blank and out-of-service signs already filtered - every record is a message a driver is physically seeing. Signs carry the road's operational truth ("CHAINS REQUIRED 10 MI AHEAD", "FULL CLOSURE HWY 96 DUE TO FIRE", "PREPARE TO STOP"), often before the event shows up in any other feed. Refresh: 150-second cache.
Filters: route (e.g. "I-80") and/or center "lat,lon" with radius_km. Quote sign text verbatim to the user - it is the most current and most local signal this server has.
Inputs: route, center, radius_km.
get_trafficARead-onlyInspect
Live traffic speed against free-flow speed on the road nearest each point, anywhere in the US (TomTom). Use it for "is the bridge backed up right now"; for a whole drive, plan_trip is better.
Inputs: place, center, points.
get_weatherARead-onlyInspect
Hourly NWS forecast, active alerts and nearby road-weather stations for any US place, with driving hazards flagged by hour.
Road-weather stations are state DOT sensors: pavement and air temperature, wind gusts and visibility, where a state publishes them.
Inputs: hours, place, center.
get_wildfiresARead-onlyInspect
CALIFORNIA ONLY: active California wildfires, flagged when close to a major California highway. For fires near a place in any other state use get_nearby_events (kinds='fire'); plan_trip lists fires near any route.
Data: the interagency WFIGS current-wildfire feed (NIFC) - name, size in acres, percent contained, discovery date. Points are each fire's ORIGIN, not its perimeter: a large fire can affect roads far from this point. Refresh: 5-minute cache; size/containment typically update once or twice a day. Small, fast-moving local fires may appear in CHP incident logs (get_incidents, type "FIRE-Report of Fire") before this feed has them.
Filters:
near_route (e.g. "I-5", "101") - only fires within ~10 miles of that highway's corridor line.
center "lat,lon" with radius_km - fires around a place, regardless of highway. Without either, every active CA fire is returned, each carrying a
near_highwayslist of major corridors within ~10 miles (empty = not near a covered major highway; it may still affect local roads).
This tool does NOT know about road closures caused by fires - cross-check get_incidents and get_lane_closures for the affected area.
Inputs: center, radius_km, near_route.
plan_tripARead-onlyInspect
Everything about one drive between any two US places, in one call.
Use this for "how's the drive to X", "how long to get to Y at 5", "anything on the way to Z". It returns:
the route (miles, main roads, alternatives) from the closure-aware planner the CommuteScout map uses: fully closed roads are avoided and routes are ranked by what is on them;
drive time for that departure: with traffic, typical for that weekday and hour, and with no traffic (TomTom historical speed profiles; live traffic too when leaving within the hour);
every live event ON the route, ordered by mile: incidents, closures, chain controls, message signs, cameras (with image URLs), road-weather stations, tolls, speed and red-light cameras, and wildfires near it;
NWS weather alerts along the route and the forecast at the destination for the arrival hour;
a one-paragraph
summaryto lead the answer with, andnotesfor anything missing or degraded.
Lead with summary, then the items that change the user's plan.
For WHEN to leave, call best_time_to_go instead. If the answer has
needs_clarification, ask the user which option they meant.
Inputs: origin, depart_at, preference, destination, +2 more.
rank_routesARead-onlyInspect
CALIFORNIA ONLY: which of 17 curated California corridors have the most going on right now.
Answers "what are the busiest routes in California", "which California highways should I avoid today". Not for other states: for a place elsewhere use get_nearby_events or get_traffic.
by="activity" ranks on live events (full closures weigh most, then incidents, lane closures, chain controls); by="congestion" ranks on measured speed vs free-flow at each corridor's midpoint and needs the traffic feed to be configured - if it is not, the ranking silently falls back to activity.
Each entry carries the counts and a one-line reason, so the answer can say WHY a corridor ranks where it does, not just list names.
Inputs: by, limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 18 tools
Descriptions are unusually disciplined, with explicit 'NOT for X, use Y instead' clauses that separate e.g. get_incidents from get_nearby_events(kinds='incident') and check_route from plan_trip. The one soft spot is that four tools (check_route, check_region, plan_trip, get_nearby_events) all answer 'what's happening along/around my drive,' and choosing between them requires reading paragraphs rather than glancing at names.
Nearly everything is snake_case verb_noun (get_incidents, check_route, rank_routes, plan_trip, find_place), so the set reads predictably. The only outlier is best_time_to_go, which breaks the verb_noun template and reads as a phrase rather than an operation.
18 tools is a bit above the comfortable 3-15 band, but the surface is genuinely broad: seven California-specific feeds, a national fallback, a trip planner, timing, history, coverage, and saved places. Each tool maps to a distinct feed or workflow, so nothing feels padded.
The lifecycle is covered end to end: discovery (find_place, get_coverage, get_my_places), live conditions per feed (incidents, closures, chains, fires, cameras, signs, traffic, weather), synthesis (plan_trip, check_route, check_region, rank_routes), and decision support (best_time_to_go, get_area_history). Missing pieces like fire-caused closures are explicitly cross-referenced to other tools rather than left as dead ends.
Maintenance
Related MCP Connectors
Geocoding, routing, isochrones, traffic, weather, and place search for AI agents. 19 MCP tools.
MCP observability. Query live traffic, errors, duration, and alerts from your AI agent.
Google Maps routes, ETAs, and turn-by-turn steps via the Apify Directions API, hosted MCP.
Hosted MCP for live place search, geocoding & turn-by-turn routes. No Maps API key to manage.
Related MCP Servers
- AlicenseAqualityCmaintenanceMCP server for ANWB traffic information, route planning, and location search in the Netherlands. Provides real-time traffic incidents, route calculation with turn-by-turn directions, and location search via natural language.69 npmMIT
- AlicenseNot gradedqualityBmaintenanceQuery WA highway conditions, ferry schedules, vessel locations, toll rates, border waits, and alerts via MCP.375 npm2Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to access Swiss public transport data including journey planning, real-time departures, disruptions, occupancy forecasts, ticket prices, and train formations via a standardized MCP interface.1167 PyPI7MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying real-time BART and SF Muni transit data, including departures, trip planning, fares, advisories, routes, alerts, vehicle positions, and schedules, from any MCP-compatible client.1MIT