Commutescout

io.github.nicglazkovPublished by GitHub account nicglazkovv2.134.0Updated Nov 6, 2026

Trip planning and best time to leave, with live road data from 37 US states, traffic, weather.

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

CommuteScout is a hosted MCP server that gives an assistant live US road data — incidents, closures, cameras, weather and traffic — plus trip planning and…

What you can do
  • Plan a drive between any two US places: route, drive time for a departure, and what is live along the line by mile
  • Compare departure times to find the best time to leave or visit, and resolve ambiguous addresses to coordinates
  • Check conditions around one place: nearby road events, hourly NWS forecast and alerts, live traffic speed, and typical incident history by hour and weekday
  • California deep dive: corridor trip checks, regional reports, CHP incidents, active lane closures, chain controls, wildfires, roadside camera snapshots, message signs and corridor rankings
  • Look up saved places such as home and work, and list which states and feeds are covered with their freshness
When to use it
Useful when someone asks how a drive looks right now, when to leave to beat traffic or weather, or what is happening on the roads around a place in the US. The California-specific tools add depth for corridor and mountain-pass questions.
Requirements
A remote streamable HTTP endpoint; no local install or package. Works without a key; an optional CommuteScout API key sent as an Authorization bearer header unlocks saved places and per-key limits. Network access to the hosted server.
Before you install
The optional API key is a secret sent in the Authorization header. The server cannot see the user's device, so location must be supplied explicitly. Data comes from third-party agency feeds that can be stale or failing, and the service is not affiliated with any government agency; users should verify before driving.

Installation

In SourceWeft

  1. Open Commutescout in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.nicglazkov%2Fcommutescout/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "commutescout": {
      "type": "http",
      "url": "https://mcp.commutescout.com/mcp"
    }
  }
}

README

Overview

CommuteScout reads 53 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.

ProductWhat it does
Live mapIncidents, closures, chain controls, wildfires, about 18,000 traffic cameras, message signs and toll prices, updated continuously.
Trip planningClosure-aware routes, drive time for any departure, the best time to leave, and an assistant that answers from the live feeds.
Watch areasPush and email alerts when something appears inside a drawn area or along a commute.
Mobile appsTurn-by-turn navigation for iOS and Android that announces what is ahead in your direction of travel.
MCP server18 tools for Claude, ChatGPT, Cursor, VS Code and any MCP client. No key required.
REST APIEvery tool as a plain HTTP GET, with an OpenAPI document, one error envelope and published rate limits.
PluginsFlare, an open protocol for adding third-party alerts to the map and the apps, with a marketplace.

Quick start

Connect an AI assistant

The hosted MCP server is public and works without a key:

https://mcp.commutescout.com/mcp

For example, in Claude Code:

sh
claude mcp add --transport http --scope user commutescout https://mcp.commutescout.com/mcp

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

sh
curl "https://mcp.commutescout.com/v1/tools/best_time_to_go?origin=Union%20Station%20Denver&destination=Red%20Rocks%20Amphitheatre&day=tomorrow"

Keys, limits, errors and the full parameter reference are at commutescout.com/developers.

Documentation

TopicWhere
MCP setup and toolscommutescout.com/mcp · docs/mcp.md
REST API, keys and rate limitscommutescout.com/developers · OpenAPI
Data sources and state coveragecommutescout.com/data-sources · docs/state-coverage.md
Plugins and the Flare protocolcommutescout.com/plugins · docs/flare.md
Architecture, deployment and adding a feeddocs/
Answer qualityEVALS.md
Pricing, privacy and termsPricing · Privacy · Terms

Repository

PathContents
src/ca_roadsFeed layer: parsers, caches and normalization for every source
src/ca_roads_mcpMCP server, REST bridge and trip planning
src/ca_roads_demoWeb app, assistant, watch areas and map publishing
siteMarketing and documentation site (Next.js static export)
examples/flare-pluginReference Flare plugin
evalsRecorded fixtures, golden questions and the eval runner
testsFixture-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.

Source: README.md at commit 7b83c87

Tools

18

check_route

Check a route

Check current conditions along a major California highway corridor. The flagship trip-check tool: 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.

Parametersto_placerequiredto_coordsfrom_placerequiredfrom_coords

check_region

Check a region

Full current-conditions report for a California region. 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.

Parametersregionrequired

get_incidents

Live incidents

Live CHP traffic incidents statewide, optionally filtered. 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. Coyote, CA -> "37.22,-121.74") 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.

Parametersareacenterhighwayradius_km

get_lane_closures

Lane closures

Caltrans lane and road closures physically in place RIGHT NOW. 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.

Parametersroutecenterdistrictradius_km

get_chain_controls

Chain controls

Current chain-control requirements on California mountain highways. 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.

Parametersroutecenterradius_km

get_wildfires

Wildfires

Active California wildfires, flagged when close to a major highway. 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_highways` list 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.

Parameterscenterradius_kmnear_route

rank_routes

Rank busiest routes

Which major corridors have the most going on right now. Answers broad questions like "what are the busiest routes", "where is traffic worst", or "which highways should I avoid today" across all 17 tracked corridors. 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.

Parametersbylimit

get_cameras

Highway cameras

Live Caltrans roadside camera snapshots near a point or on a 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.

Parameterslimitroutecenterradius_km

get_road_signs

Message signs

What Caltrans changeable message signs are displaying right now. 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: ~2-minute 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.

Parametersroutecenterradius_km

get_nearby_events

Nearby events (nationwide)

Live road events near a point anywhere CommuteScout covers, not just California: 37 states today (get_coverage lists them). Data: the same multi-state feeds the live map shows, normalized - state DOT incidents, roadwork and closures, chain and traction advisories, and nationwide wildfires. Every event names its publishing agency in the source field. Coverage varies by state (some publish roadwork only; docs/state-coverage.md has the matrix); states added later appear here automatically. For CALIFORNIA questions prefer the dedicated tools above (richer detail: dispatch logs, lane counts, chain levels). Use THIS tool for any location outside California, near a state border, or as a supplement when a California tool comes back empty. 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.

Parameterskindsplacecenterradius_km

get_my_places

My saved places

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.

Takes no parameters.

find_place

Find a place

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.

Parametersnearlimitqueryrequired

plan_trip

Plan a trip

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 `summary` to lead the answer with, and `notes` for 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.

Parametersorigindepart_atpreferencedestinationorigin_coordsdestination_coords

best_time_to_go

Best time to go

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. Times are in the origin's local time zone (`time_zone`). Pair with plan_trip for what is on the road right now.

Parametersdaylatestoriginearliestarrive_bydestinationstep_minutesorigin_coordsdestination_coords

get_weather

Weather for drivers

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.

Parametershoursplacecenter

get_traffic

Traffic speeds

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.

Parametersplacecenterpoints

get_area_history

Area history

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.

Parametersdaysplacecenterradius_km

get_coverage

Coverage

Which states and sources CommuteScout covers right now, with each feed's freshness. Check it when an answer is unexpectedly empty.

Takes no parameters.

Version history

25
  1. v2.134.0LatestNov 6, 2026
  2. v2.133.2Oct 30, 2026
  3. v2.133.1Oct 30, 2026
  4. v2.132.0Oct 29, 2026
  5. v2.128.0Oct 25, 2026
  6. v2.127.0Oct 23, 2026
  7. v2.126.1Oct 7, 2026
  8. v2.126.0Oct 4, 2026
  9. v2.125.0Oct 3, 2026
  10. v2.122.3Oct 3, 2026
  11. v2.122.1Oct 2, 2026
  12. v2.121.3Oct 2, 2026
  13. v2.120.0Oct 2, 2026
  14. v2.118.0Oct 1, 2026
  15. v2.117.0Sep 30, 2026
  16. v2.116.0Sep 27, 2026
  17. v2.115.0Sep 26, 2026
  18. v2.114.0Sep 26, 2026
  19. v2.110.0Sep 25, 2026
  20. v2.109.0Sep 25, 2026
  21. v2.108.0Sep 23, 2026
  22. v2.105.0Sep 21, 2026
  23. v2.104.0Sep 21, 2026
  24. v2.101.0Sep 21, 2026
  25. v2.24.0Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts