ODS-E MCP Server
The official @asobacloud/odse-mcp npm package is a Model Context Protocol server that lets AI coding agents and data agents call ODS-E tools directly — no manual scripting required.
Published on the npm Registry as the primary distribution channel, it allows agents to run directly with npx -y @asobacloud/odse-mcp.
Agents can convert OEM telemetry payloads to ODS-E records, validate batches, list supported OEMs, and bridge SCADA data to pvlib structures, all via structured MCP tool calls backed by the published odse Python package.
Tools
| Tool | What it does |
|---|---|
ListSupportedOEMs |
Returns all OEM source keys from the installed odse transformer registry, plus odse.__version__. |
ConvertToODSE |
Converts raw CSV/JSON text (or a file path) to ODS-E records. Supports explicit source, auto-detection, asset_id, timezone, and timeout. |
ValidateODSERecord |
Runs odse.validate_batch on a JSON array of records. Accepts an optional level (schema or semantic). |
Requirements
| Runtime | Required for |
|---|---|
| Node.js ≥ 22 | MCP server process |
Python 3 + odse |
All tools (pip install odse) |
Quick Install
pip install odse
npx -y @asobacloud/odse-mcp
Set ODSE_WORKSPACE to an absolute directory path if you want agents to reference telemetry files by relative path. The server speaks MCP over stdio — no HTTP port needed.