LiveTrafficCam MCP Server

io.github.bzsassonPublished by GitHub account bzsassonv1.0.0Updated Oct 25, 2026

Live US traffic cameras from state DOT feeds with verified live status, via livetrafficcam.com

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

A local MCP server that lets an assistant look up verified-live US traffic cameras from state DOT feeds via the LiveTrafficCam public API.

What you can do
List covered states with camera counts and a liveness summary, and find cameras by two-letter state code with an optional route filter, or by a named pass, corridor, bridge or tunnel slug. Check a single camera's verified-live status, last live time and official DOT source, and read measured fleet uptime per state, including live, stale and dead counts and a 14-day check success rate. Results come back as compact JSON with a source URL and agency attribution, cached for 60 seconds.
When to use it
Useful when someone asks about current road conditions, whether a specific highway, pass, bridge or tunnel camera is up, or how reliable a state's traffic camera coverage is. It is read-only lookup, not navigation or routing.
Requirements
Runs locally over stdio via npx, so Node.js 20 or newer is needed. No API keys, environment variables or headers are declared. It makes network requests to the livetrafficcam.com public API on each tool call.
Before you install
Read-only lookups; no accounts, payments or writes are involved. Data is aggregated from third-party state DOT feeds, so accuracy and freshness depend on those agencies. Camera results carry an agency attribution line that should be kept when displaying data, and uptime figures should cite the uptime report. A query returns at most 200 cameras.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

livetrafficcam-mcp

MCP (Model Context Protocol) server for LiveTrafficCam, a directory of live US traffic cameras built on official state DOT feeds. Every camera is checked on a rolling schedule with real HTTP requests, so "live" means a verified current image, not a listing.

The server wraps the site's public JSON API. It sends one request per tool call, caches responses for 60 seconds, and returns compact JSON with a source_url you can cite.

Install

Requires Node 20 or newer.

Claude Desktop (claude_desktop_config.json):

json
{  "mcpServers": {    "livetrafficcam": {      "command": "npx",      "args": ["-y", "livetrafficcam-mcp"]    }  }}

Claude Code:

bash
claude mcp add livetrafficcam -- npx -y livetrafficcam-mcp

Cursor (.cursor/mcp.json):

json
{  "mcpServers": {    "livetrafficcam": {      "command": "npx",      "args": ["-y", "livetrafficcam-mcp"]    }  }}

Tools

  • list_states — states covered, camera counts, and a liveness summary per state. Example: "Which states have traffic camera coverage?"
  • cameras_by_state — cameras for a two-letter state code, with an optional route filter. Example: "Show live cameras on I-90 in Washington."
  • cameras_for_entity — cameras for a named pass, corridor, bridge or tunnel slug. Example: "What do the Donner Pass cameras show?" uses donner-pass.
  • camera_status — one camera's verified-live status, last live time, and official DOT source. Example: "Is the I-90 floating bridge camera up?"
  • state_uptime — measured uptime for a state's camera fleet: live, stale and dead counts plus the 14-day check success rate. Example: "How reliable are Washington's traffic cameras?"

The camera API returns at most 200 cameras per query; tool output says so when a state has more. Fleet counts come from the camera uptime report.

Data source and attribution

All data comes from livetrafficcam.com's public API, which aggregates official state DOT camera feeds (WSDOT, Caltrans, UDOT, and others). Every camera result carries the attribution line for its agency; keep it when you display the data. Uptime numbers should cite the uptime report.

More from the same data:

Also available

A Home Assistant integration puts a pass, bridge, tunnel, airport or highway on a dashboard: one camera entity per camera, a verified-live sensor each, and reported disruptions. No API keys.

License

MIT

Source: README.md at commit be6839b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts