Yatis MCP Server

What is Yatis MCP Server?

A Node.js-based local MCP server that integrates Yatis Telematics APIs with AI agents like Cursor, VS Code, and Claude Desktop. It enables accessing vehicle, device, location, and EV battery data via natural language.

How to use Yatis MCP Server?

Install Node.js 20+, obtain a Yatis API key from your sales manager, then configure your MCP client (VS Code, Cursor, or Claude Desktop) with the path to Node, the server.js file, and the API key. The server runs locally over stdio.

Key features of Yatis MCP Server

• Retrieve all groups associated with the API token
• Get vehicles, devices, and meta information
• Access location data
• Fetch EV battery information (voltage, SoC)
• Query distance traveled and power consumed
• Calculate distance between coordinates using Haversine

Use cases of Yatis MCP Server

• Ask an AI agent for real-time vehicle locations and device status
• Monitor EV battery health and charge levels via natural language
• Analyze historical distance and power consumption
• Find distances between points for logistics or route planning
• List all groups and vehicles in the fleet with a single query

FAQ from Yatis MCP Server

What are the requirements to run Yatis MCP Server?

Node.js version 20 or above is required. You also need a valid Yatis API key (contact your sales manager) and the @modelcontextprotocol/sdk npm package.

How do I integrate Yatis MCP Server with VS Code?

Create a .vscode/mcp.json file in your workspace (or use ~/.vscode for global access) with the server configuration, specifying the node path, server.js path, and YATIS_API_KEY environment variable.

Does Yatis MCP Server work with Cursor or Claude Desktop?

Yes. The same configuration files work for Cursor (using .cursor/ directories). For Claude Desktop, add the server to claude_desktop_config.json, typically located in ~/Library/Application Support/Claude/.

What data does the server access and where does it run?

The server runs locally and accesses Yatis Telematics cloud APIs using the provided API key. All data stays within your local MCP client session and is not stored permanently by the server.

Are there any external dependencies besides the MCP SDK?

No. The README states no other dependencies beyond the @modelcontextprotocol/sdk npm package.