Can my AI check for traffic incidents on a specific highway like I-405 in California?

Yes! Use the `get_events` tool with road=I-405 and jurisdiction=CA to filter incidents specifically on that highway. You can further filter by type (incidents, construction, closures) and severity (minor, moderate, major, critical). The results include incident descriptions, affected lanes, estimated clearance times, and alternate route suggestions. For mapping visualization, use `get_events_geojson` to get the same data in GeoJSON format ready for Mapbox or Leaflet.

How do I find traffic cameras and EV charging stations along my route?

Use the `get_features` tool with type=cameras to find all traffic cameras in a jurisdiction, or type=ev_chargers for EV charging stations. You can filter by bounding box (bbox) or by radius from a lat/lon point. For mapping applications, use `get_features_geojson` which returns data in GeoJSON format ready for direct integration with mapping libraries. Camera features include live stream URLs and road conditions include surface status and weather impacts.

Can I analyze traffic incident trends to understand if traffic is getting worse in my state?

Absolutely! Use `get_trends` with your jurisdiction code (e.g., jurisdiction=CA for California) to get time-series incident data showing whether incidents are increasing, decreasing, or stable over time. Use `get_clearance` to understand how quickly incidents are being resolved (P50 median and P95 resolution times). Combined with `get_summary` for current snapshot data, you can build comprehensive traffic safety and efficiency reports. This is perfect for transportation planning, resource alloca

Road511 MCP Server for Mastra AI 8 tools — connect in under 2 minutes

Name: Road511
Availability: InStock
Author: Vinkius

docs.mastra.ai/docs/agents/mcp-tools

Built by Vinkius GDPR 8 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Road511 through the Vinkius and Mastra agents discover all tools automatically — type-safe, streaming-ready, and deployable anywhere Node.js runs.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

typescript

import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token — get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "road511": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Road511 Agent",
    instructions:
      "You help users interact with Road511 " +
      "using 8 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Road511?"
  );
  console.log(result.text);
}

main();

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Road511 MCP Server

Connect your Road511 real-time traffic data API to any AI agent and take full control of North American traffic monitoring, incident tracking, infrastructure awareness, and operational analytics through natural conversation.

Mastra's agent abstraction provides a clean separation between LLM logic and Road511 tool infrastructure. Connect 8 tools through the Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution — deployable to any Node.js host in one command.

What you can do

Traffic Incidents — Track real-time incidents, construction, closures, special events, and weather advisories across all 50 US states and 13 Canadian provinces
Traffic Cameras — Access live traffic camera feeds for visual traffic monitoring across North America
Road Conditions — Check current road conditions, surface status, and weather impacts on roadways
EV Charging — Find electric vehicle charging stations across the US and Canada for trip planning
Rest Areas — Locate rest areas, weigh stations, and ferry terminals along major corridors
Weather Stations — Access road-side weather station data for weather-aware routing
Geospatial Mapping — Get all data in GeoJSON format for direct mapping and GIS integration
Incident Analytics — Analyze traffic incident trends, resolution times, and operational metrics
System Health — Monitor API health and data source status across 65 jurisdictions

The Road511 MCP Server exposes 8 tools through the Vinkius. Connect it to Mastra AI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Road511 to Mastra AI via MCP

Follow these steps to integrate the Road511 MCP Server with Mastra AI.

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save to agent.ts and run with npx tsx agent.ts

Explore tools

Mastra discovers 8 tools from Road511 via MCP

Why Use Mastra AI with the Road511 MCP Server

Mastra AI provides unique advantages when paired with Road511 through the Model Context Protocol.

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure — add Road511 without touching business code

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

TypeScript-native: full type inference for every Road511 tool response with IDE autocomplete and compile-time checks

One-command deployment to any Node.js host — Vercel, Railway, Fly.io, or your own infrastructure

Road511 + Mastra AI Use Cases

Practical scenarios where Mastra AI combined with the Road511 MCP Server delivers measurable value.

Automated workflows: build multi-step agents that query Road511, process results, and trigger downstream actions in a typed pipeline

SaaS integrations: embed Road511 as a first-class tool in your product's AI features with Mastra's clean agent API

Background jobs: schedule Mastra agents to query Road511 on a cron and store results in your database automatically

Multi-agent systems: create specialist agents that collaborate using Road511 tools alongside other MCP servers

Road511 MCP Tools for Mastra AI (8)

These 8 tools become available when you connect Road511 to Mastra AI via MCP:

get_clearance

Returns average resolution times by incident type, severity, jurisdiction, and time period. Essential for operational efficiency analysis, resource planning, performance benchmarking, and understanding how quickly traffic incidents are resolved in different regions. AI agents should use this when users ask "what is the median resolution time for incidents in California", "how long do major incidents take to clear in Texas", or need performance metrics for traffic incident management analysis. Get incident resolution time metrics (P50/P95) for operational analysis

get_events

Returns event type, severity (minor, moderate, major, critical, info), jurisdiction, road affected, start and end times, lifecycle status, geometry (line/point), and detailed descriptions. Supports filtering by jurisdiction (e.g., CA), type (incidents, construction, closures, events, advisories), severity, road name, status, and geographic area (bbox, lat/lon/radius). Essential for real-time traffic awareness, route planning, delivery logistics, and commuter decision-making. AI agents should use this when users ask "what incidents are on I-405", "show construction in California", or need traffic event data for route optimization. Get traffic incidents, construction, closures, and events across US and Canada

get_events_geojson

Each feature contains event properties (type, severity, jurisdiction, road, times, status, descriptions) in the properties object and point/line geometry in the geometry object. Supports all the same filtering parameters as get_events. Essential for mapping applications, spatial analysis, GIS integration, and visualization dashboards. AI agents should use this when users need to plot traffic events on a map, perform spatial queries, or integrate with GeoJSON-based mapping tools. Get traffic events in GeoJSON format for mapping and spatial analysis

get_features

Returns type, jurisdiction, coordinates, status, and feature-specific details. Use when users ask about traffic cameras, EV chargers, rest areas, road conditions, or need infrastructure data for mapping. Get road infrastructure features including cameras, road conditions, weather stations, and more

get_features_geojson

Each feature includes properties (type, jurisdiction, status, camera URL, road condition, weather data, EV charger info) and point geometry. Supports all the same filtering parameters. Essential for mapping applications, GIS workflows, spatial databases, and visualization dashboards. AI agents should reference this when users need to plot infrastructure features on a map, integrate with GeoJSON tools, or perform spatial analysis on road infrastructure. Get road infrastructure features in GeoJSON format for mapping and GIS integration

get_health

Returns API availability, response times, data source connectivity (per jurisdiction), last update timestamps, and system alerts. Essential for monitoring API reliability, verifying data freshness, troubleshooting integration issues, and ensuring production system uptime. AI agents should use this as a diagnostic tool when users report missing data, when debugging integration issues, or as a periodic health check before making complex traffic data queries. Check API health and data source status

get_summary

Returns event counts by type and severity, active camera counts, data source status (healthy, degraded, down), refresh rates, and data freshness indicators. Essential for data quality monitoring, system health checks, understanding data coverage by region, and verifying API reliability before production use. AI agents should use this when users ask "how many active incidents are there nationwide", "is the California data source healthy", or need a system-wide overview of Road511 data quality and coverage. Get summary statistics and data source health across all jurisdictions

get_trends

Returns incident counts over time, severity distributions, trend directions (increasing, decreasing, stable), peak incident times, and comparative analysis between regions. Essential for traffic pattern analysis, operational planning, resource allocation, and understanding temporal traffic safety trends. AI agents should use this when users ask "are incidents increasing in Texas this week", "show me traffic incident trends for the past month", or need analytical data for traffic safety reporting. Get traffic incident trends and time-series analytics