MCP Server Integration

Connect California road data to Claude, VS Code, Cursor, and other MCP-compatible tools

MCP Server URL

Use the following URL when adding to your MCP client:

Claude

  1. Click menu (top right)
  2. Select "Settings"
  3. Go to "Developer"
  4. Click "Add MCP Server"
  5. Enter name: california-road-data
  6. Paste MCP URL above
  7. Click "Add Server"
  8. Restart Claude

VS Code

Install MCP extension, then add to settings.json:

"mcp.servers": {
  "california-road-data": {
    "url": "https://californiaroaddata.com/mcp"
  }
}

Cursor

Create or edit .cursor/mcp.json:

{
  "mcpServers": {
    "california-road-data": {
      "url": "https://californiaroaddata.com/mcp"
    }
  }
}

15 Available Tools

Discovery

  • • List data types
  • • List districts
  • • Get district info

Data Retrieval

  • • Chain controls
  • • CCTV cameras
  • • Message signs
  • • Lane closures
  • • Weather stations
  • • Travel times

Search

  • • By location
  • • By route
  • • By county
  • • By coordinates
  • • Multi-type search

Data Coverage

Chain Controls

Mountain pass restrictions (R-0 to R-4)

CCTV Cameras

Traffic camera feeds across all districts

Message Signs

Highway alerts and information

Lane Closures

Current and scheduled closures

Weather Stations

Road and weather conditions

Travel Times

Route segment estimates

Coverage: All 12 California CalTrans districts • Real-time data • No authentication required

Example Queries

What chain controls are active in the Bay Area?

Find all data about Route 101

Show weather conditions near Mount Hamilton

What lane closures are in Los Angeles County?

Get travel times in District 08

Transport Details

The canonical endpoint uses MCP over Streamable HTTP with JSON request/response semantics.

Canonical Endpoint:

/mcp

Server Metadata

Use /api/mcp for machine-readable endpoint metadata and tool listings.

Compatibility Alias

/sse remains available for existing configs, but new clients should use /mcp.

The endpoint is stateless today, so GET requests return HTTP 405 unless standalone SSE support is added later.

Features

Real-time Data

Direct CalTrans API integration

Geo-aware

Distance-based searches

Smart Search

Multiple filter options

No Auth Needed

Public data access

Need more information?