LiveTrafficCam MCP Server
LocalAbout LiveTrafficCam MCP Server
LiveTrafficCam MCP Server exposes verified live US traffic-camera data from official state DOT feeds. It is for querying camera coverage, status, and uptime, with results that include source attribution.
Key features
- 01List states and camera coverage
- 02Find cameras by state and route
- 03Find cameras near named infrastructure
- 04Check verified status and last-live time
- 05Review state fleet uptime
Use cases
- 01Locate live cameras along a route
- 02Check whether a bridge camera is active
- 03Compare camera uptime by state
MCP support
The MCP server wraps LiveTrafficCam’s public JSON API and provides five tools for querying coverage, cameras, status, and uptime. Results include source URLs or official DOT attribution.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
5Saved tool list · updated 2w ago
This tool takes no parameters.
Details
From the project READMElivetrafficcam-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):
{
"mcpServers": {
"livetrafficcam": {
"command": "npx",
"args": ["-y", "livetrafficcam-mcp"]
}
}
}
Claude Code:
claude mcp add livetrafficcam -- npx -y livetrafficcam-mcp
Cursor (.cursor/mcp.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?" usesdonner-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:
- Camera uptime report — measured per-state uptime of official DOT cameras.
- Traffic camera statistics — how many official DOT traffic cameras exist, per state and agency.
- Donner Pass cameras — an example of the pass pages the entity tool points at.
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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.