Vega Telematics REST API & Model Context Protocol (MCP) Reference
Integrate real-time GPS tracking data, vehicle telemetry, geofence breaches, and report generation directly into your custom ERP (SAP, Odoo), Transportation Management Systems (TMS), or connect autonomous AI agents (Claude Desktop, Cursor, Antigravity) with zero manual tool-coding.
Model Context Protocol (MCP) Integration
Connect Cursor, Claude Desktop, Antigravity, and autonomous AI agents directly to live vehicle telemetry. The Vega MCP server uses automated OpenAPI 3.0 reflection across 627+ endpoints with a token-safe Meta Mode.
https://api.vegagps.online/mcp/sse
1-Click Client Setup Snippets
{
"mcpServers": {
"vega-fleet": {
"url": "https://api.vegagps.online/mcp/sse",
"headers": {
"Authorization": "Bearer YOUR_VEGA_API_KEY_OR_JWT"
}
}
}
}
{
"mcpServers": {
"vega-fleet": {
"url": "https://api.vegagps.online/mcp/sse",
"headers": {
"Authorization": "Bearer YOUR_VEGA_API_KEY_OR_JWT"
}
}
}
}
Pre-Configured Core Tools
Authentication & API Keys
All requests to the Vega REST API require a Bearer token or API key passed in the Authorization header:
/auth/login
Authenticate user credentials and retrieve a 30-day persistent JWT token.
// Request Payload{ "email": "user@org.com", "password": "YourPassword123!" }
/api/devices
Fetch all active vehicles, SIM details, ignition state, and last seen timestamps for the organization.
// Sample cURL Requestcurl -X GET "https://api.vegagps.com/api/devices" \
-H "Authorization: Bearer YOUR_TOKEN"
/api/positions?imei={imei}&from={startDate}&to={endDate}
Query historical location trail, speed records, course heading, and sensor telemetry values.
/v1/integration/*
High-throughput integration endpoints designed specifically for automated B2B server-to-server data syncing.