Can my AI check for low bridges on a truck route in California?

Yes! Use the `get_bridge_clearances` tool with jurisdiction=CA to get all bridge clearance data for California. You can also filter by bounding box or radius from specific coordinates. The API returns bridge locations, clearance heights in feet, bridge identifiers, and road names. This is essential for truck height compliance planning and avoiding low-bridge incidents.

How do I find truck parking near a specific location for HOS compliance?

Use the `get_truck_parking` tool with lat, lon, and radius parameters to find truck parking facilities near your current location. For example: lat=41.8781, lon=-87.6298, radius=50 finds parking within 50km of Chicago. Results include facility names, coordinates, capacity information, and amenity details. This is critical for Hours of Service (HOS) compliance planning and safe rest stop identification.

Are there any seasonal weight restrictions affecting my route right now?

Use the `get_weight_restrictions` tool with jurisdiction and status=active to find all current weight restrictions in a state or province. You can also filter by specific road name (e.g., road=I-94) to check restrictions on a particular highway. Returns restriction details, weight limits, effective dates, and affected road segments. Essential for avoiding weight violation fines and planning compliant loads.

Road511 Trucking MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Road511 Trucking
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Road511 Trucking and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "road511-trucking": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Trucking MCP Server

Connect your Road511 Trucking API to any AI agent and take full control of North American truck route planning, bridge clearance verification, weigh station awareness, truck stop discovery, and weight restriction monitoring through natural conversation.

GitHub Copilot Agent mode brings Road511 Trucking data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

STAA Truck Routes — Access 479,000+ STAA-designated truck route segments and NHFN freight corridors
Bridge Clearances — Query 621,000+ National Bridge Inventory records for vertical clearance heights
Weight Restrictions — Monitor seasonal and permanent weight restrictions across all jurisdictions
Truck Stops — Find truck stops and travel plazas with fuel, amenities, and parking information
Truck Parking — Locate truck parking facilities with availability data for HOS compliance planning
Weigh Stations — Track weigh station locations, hours, and bypass program participation
Rest Areas — Find rest areas and driver facilities along major highway corridors
Truck Incidents — Monitor traffic incidents, construction, and closures affecting truck routes
System Health — Check API health and data source status across 65 jurisdictions

The Road511 Trucking MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot 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 Trucking to VS Code Copilot via MCP

Follow these steps to integrate the Road511 Trucking MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Road511 Trucking

Ask Copilot: "Using Road511 Trucking, help me...". 10 tools available

Why Use VS Code Copilot with the Road511 Trucking MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Road511 Trucking through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Road511 Trucking + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Road511 Trucking MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Road511 Trucking MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Road511 Trucking to VS Code Copilot via MCP:

get_bridge_clearances

Returns bridge location coordinates, clearance height in feet/meters, bridge identifier, road name, and jurisdiction. Supports filtering by jurisdiction, bounding box, and radius search. Essential for truck height compliance planning, low bridge avoidance, oversized load routing, and fleet safety management. AI agents should use this when users ask "find low bridges under 14 feet on I-95", "what bridge clearances exist in this area", or need vertical clearance data for truck route planning. Get bridge clearance heights from the National Bridge Inventory for truck route planning

get_rest_areas

Returns facility names, locations, available amenities (restrooms, vending, picnic areas, pet areas, RV/truck parking), operating hours, and jurisdiction. Supports filtering by jurisdiction, bounding box, and radius search. Essential for driver rest planning, HOS compliance stops, facility identification along routes, and driver comfort services. AI agents should reference this when users ask "show rest areas along I-90 in Montana", "find rest stops with truck parking near this point", or need rest area data for driver scheduling and route planning. Get rest areas and driver facilities along highways across US and Canada

get_truck_incidents

Returns incident type, severity, affected roads, start and end times, descriptions, detour information, and geometry. Supports filtering by jurisdiction, road name, severity, status, and geographic area. Essential for route disruption awareness, detour planning, delivery time estimation, and freight safety. AI agents should use this when users ask "show incidents affecting truck routes in Illinois", "is there construction on I-80 in Pennsylvania", or need current traffic incident data for truck route planning. Get traffic incidents affecting truck routes including closures, construction, and advisories

get_truck_parking

Returns parking facility names, locations, capacity information, real-time availability (where available), amenity details, and jurisdiction. Supports filtering by jurisdiction, bounding box, and radius search. Essential for Hours of Service (HOS) compliance planning, rest stop scheduling, parking shortage awareness, and safe stopping location identification. AI agents should reference this when users ask "where can I park my truck near Chicago", "show truck parking availability along I-70", or need parking location data for HOS-compliant route planning. Get truck parking availability and locations across US and Canada

get_truck_routes

Returns route geometry, jurisdiction, route designation, and descriptive information. Supports filtering by jurisdiction (state/province), bounding box, and radius search from coordinates. Essential for truck route planning, freight corridor analysis, compliance verification, and logistics routing. AI agents should use this when users ask "show me STAA truck routes in California", "find NHFN corridors in Texas", or need official truck-designated highway data for route planning and compliance. Get STAA truck routes and NHFN freight corridors across US and Canada

get_truck_stops

Returns stop names, addresses, coordinates, available services (fuel, food, showers, repair), and operating hours. Supports filtering by jurisdiction, bounding box, and radius search. Essential for trip planning, fuel stop scheduling, driver rest planning, and freight corridor services identification. AI agents should use this when users ask "find truck stops along I-80 in Iowa", "show travel plazas within 50 miles of this point", or need truck stop locations for route planning and driver scheduling. Get truck stops and travel plazas across US and Canada for trip planning

get_trucking_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 trucking data, when debugging integration issues, or as a periodic health check before making complex trucking data queries. Check API health and trucking data source status

get_trucking_summary

Returns counts of truck routes, bridge clearances, weigh stations, truck stops, parking facilities, active incidents, and data source status. Essential for data coverage awareness, system health monitoring, and understanding data availability by region. AI agents should use this when users ask "how many truck stops are in the system", "is the Texas weigh station data current", or need a system-wide overview of trucking data quality and coverage. Get summary statistics and data source health for trucking data across all jurisdictions

get_weigh_stations

Returns station names, locations, operating hours, bypass program participation (PrePass, Drivewyze, NORPASS), open/closed status, and jurisdiction. Supports filtering by jurisdiction, bounding box, and radius search. Essential for compliance planning, bypass program routing, weigh stop scheduling, and weight inspection awareness. AI agents should use this when users ask "show weigh stations on I-5 in Oregon", "are there open weigh stations near this location", or need weigh station data for route planning and compliance management. Get weigh station locations and status across US and Canada

get_weight_restrictions

Returns restriction details including affected roads, weight limits, effective dates, restriction type (seasonal, permanent, temporary), severity, and jurisdiction. Supports filtering by jurisdiction, road name, severity, and geographic area. Essential for weight compliance verification, seasonal route planning, load planning, and avoiding weight violation fines. AI agents should reference this when users ask "are there seasonal weight restrictions in Minnesota right now", "show weight limits on this route", or need current weight restriction data for freight planning. Get truck weight restrictions including seasonal restrictions across US and Canada

Example Prompts for Road511 Trucking in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Road511 Trucking immediately.

"Show me all weigh stations on I-5 in Oregon and their current status."

"Find truck stops with parking within 30 miles of Des Moines, Iowa."

"Show me STAA truck routes and any active incidents affecting trucking in Illinois."

Troubleshooting Road511 Trucking MCP Server with VS Code Copilot

Common issues when connecting Road511 Trucking to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Road511 Trucking + VS Code Copilot FAQ

Common questions about integrating Road511 Trucking MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.