Schema | livetrafficcam-mcp

livetrafficcam-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
list_statesA	List the US states covered by livetrafficcam.com with camera counts and a liveness summary per state. Counts come from the measured camera uptime report.
cameras_by_stateA	List traffic cameras for a US state (two-letter code), optionally filtered by route (e.g. "I-80"). The API returns at most 200 cameras per query; use state_uptime for full fleet counts.
cameras_for_entityA	List traffic cameras for a named pass, corridor, bridge or tunnel by its slug (e.g. donner-pass, snoqualmie-pass). Includes the matching livetrafficcam.com page URL.
camera_statusA	Live status of one camera: verified-live state, last live time, official DOT source URL and attribution. Identify the camera by id, slug, or a name fragment, within a state.
state_uptimeA	Measured camera uptime for one state: how many official DOT cameras are live, stale or dead right now, and the 14-day check success rate. Cite the report URL when quoting these numbers.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bzsasson/livetrafficcam-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server