odse-mcp
This server provides MCP tools to convert raw OEM energy telemetry into ODS-E records and validate them, using the installed odse Python package.
ConvertToODSE: Convert CSV or JSON telemetry data (provided directly as a text payload or via a file path relative to
ODSE_WORKSPACE) into ODS-E energy time-series records usingodse.transformer.transform. Supports explicitsource(e.g.,huawei,enphase) or auto-detection from payload content. Optional parameters:asset_id,timezone, andtimeout(up to 600,000 ms).ListSupportedOEMs: Retrieve the list of OEM source keys supported by the installed
odsepackage, along with theodseversion.ValidateODSERecord: Validate a JSON array of ODS-E records (provided as a JSON string) using
odse.validate_batch, with an optional validationlevel(default:schema).
All tools return JSON responses. The server communicates over MCP via stdio, requiring Node.js ≥22 and Python 3 with the odse package installed.
Provides tools for converting Huawei telemetry payloads into ODS-E energy records and validating them according to the odse schema.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@odse-mcp Convert this telemetry payload to ODS-E"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ODS-E Conversion
MCP server for ODS-E energy telemetry conversion. AI coding/data agents call its tools over the Model Context Protocol to convert OEM payloads into ODS-E records and validate them via the published odse Python package.
The installed odse package is the source of truth for OEM support, transform behavior, and validation semantics.
Quick start
Set ODSE_WORKSPACE to an absolute path used when resolving relative payload_file values. If omitted, the server uses its process working directory. The server speaks MCP over stdio (no HTTP port).
Prerequisite: python3 on PATH must be able to import odse (pip install odse).
Cursor
Add to ~/.cursor/mcp.json or the project .cursor/mcp.json:
{
"mcpServers": {
"odse": {
"command": "npx",
"args": ["-y", "@asobacloud/odse-mcp"],
"env": {
"ODSE_WORKSPACE": "/absolute/path/to/your/data"
}
}
}
}Restart Cursor (or reload MCP servers), then ask the agent to convert or validate ODS-E data.
Claude Code
CLI (user scope):
claude mcp add --transport stdio --scope user \
--env ODSE_WORKSPACE=/absolute/path/to/your/data \
odse -- npx -y @asobacloud/odse-mcpOr put the same JSON under mcpServers in project .mcp.json (team-shared) or ~/.claude.json (user-wide):
{
"mcpServers": {
"odse": {
"command": "npx",
"args": ["-y", "@asobacloud/odse-mcp"],
"env": {
"ODSE_WORKSPACE": "/absolute/path/to/your/data"
}
}
}
}Verify with claude mcp list. Project .mcp.json servers need approval the first time you open the repo in Claude Code.
Codex
CLI:
codex mcp add odse --env ODSE_WORKSPACE=/absolute/path/to/your/data -- npx -y @asobacloud/odse-mcpOr edit ~/.codex/config.toml (or project .codex/config.toml in a trusted project):
[mcp_servers.odse]
command = "npx"
args = ["-y", "@asobacloud/odse-mcp"]
[mcp_servers.odse.env]
ODSE_WORKSPACE = "/absolute/path/to/your/data"Codex CLI, the IDE extension, and the ChatGPT desktop Codex host share this config.
Run directly
pip install odse
npx -y @asobacloud/odse-mcpRelated MCP server: data-bs-mcp
Tools
Tool | Runtime | What it does |
|
| Returns OEM source keys from the installed |
|
| Calls |
|
| Calls |
ConvertToODSE
Argument | Description |
| Raw telemetry text (CSV or JSON) |
| Path to a telemetry file (relative paths resolve against |
| OEM key (e.g. |
| Optional asset id forwarded to |
| Optional timezone forwarded to |
| Timeout in ms (default |
Example (explicit source):
{
"name": "ConvertToODSE",
"arguments": {
"source": "huawei",
"payload": "Time,Active Power(kW),Inverter State\n2024-01-01 12:00:00,12.0,0\n"
}
}Successful responses are JSON on the tool text channel, for example:
{
"records": [
{
"timestamp": "2024-01-01T12:00:00Z",
"kWh": 1.0,
"error_type": "normal",
"error_code": "0"
}
],
"count": 1,
"source": "huawei",
"odse_version": "0.8.2"
}Live-fetch arguments (url, headers, body, …) are rejected: not part of this release.
ValidateODSERecord
Pass records as a JSON string of an array of objects. Optional level is forwarded to odse.validate_batch (default schema).
{
"name": "ValidateODSERecord",
"arguments": {
"records": "[{\"timestamp\":\"2024-01-01T12:00:00Z\",\"kWh\":1.0,\"error_type\":\"normal\"}]"
}
}Validation follows odse.validate_batch package semantics (not a separate JSON Schema checker). Extra properties and numeric bounds behave as the installed odse version defines them.
Tool exit code 1 becomes isError: true on the MCP result. Unexpected crashes are reported as errors.
Requirements
Runtime | Required for |
Node.js ≥ 22 | MCP server |
Python 3 + | All tools ( |
Architecture
rules/*.json → tool schemas + execution specs
scripts/*.py → odse wrappers (list / convert / validate)
src/loader.ts → bundled rules
src/runner.ts → spawn, timeouts, exit-code → isError
src/index.ts → MCP stdio server
bin/cli.js → npx / bin entrypointDevelopment
git clone https://github.com/AsobaCloud/odse-mcp.git
cd odse-mcp
python3 -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install odse
npm install
npm run build
npm testScript | Purpose |
| Compile TypeScript → |
| E2E via real MCP |
| Run the server on stdio |
|
|
Local MCP config (instead of npx):
{
"mcpServers": {
"odse": {
"command": "node",
"args": ["/absolute/path/to/odse-mcp/dist/index.js"],
"env": {
"ODSE_WORKSPACE": "/absolute/path/to/your/data",
"PATH": "/absolute/path/to/odse-mcp/.venv/bin:/usr/bin:/bin"
}
}
}
}Ensure the PATH (or environment) makes python3 resolve to an interpreter that can import odse.
Releasing
CI runs build + E2E on every push/PR (Node 22 + pip install odse). To publish a new version:
Bump
versioninpackage.jsonCommit, push, and create a GitHub Release (
gh release create vX.Y.Z --generate-notes).github/workflows/publish.ymlpublishes to npm (Trusted Publisher / OIDC, orNPM_TOKENif configured)
License
MIT © Asoba
Available Tools
3 toolsConvertToODSEA
Convert raw OEM energy telemetry (CSV/JSON text or file) into ODS-E energy-timeseries records using odse.transformer.transform. Optionally auto-detect the OEM when source is omitted.
Inputs: source, payload, timeout, asset_id, +2 more.
ListSupportedOEMsA
List OEM source keys supported by the installed odse package, plus the odse package version.
Inputs: timeout.
ValidateODSERecordB
Validate a JSON array of ODS-E records using odse.validate_batch (package semantics).
Inputs: records (required), level, timeout.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: conversion, listing supported OEMs, and validation. There is no functional overlap between them, making misselection unlikely.
All tool names follow the same Verb+Object pattern (ConvertTo, ListSupported, Validate) with consistent PascalCase. The naming convention is uniform and predictable.
With 3 tools, the server is well-scoped for its stated purpose of converting and validating ODS-E records. Each tool is necessary and the count is within the ideal 3-15 range.
The tool surface covers the core workflow: convert data, list supported sources, and validate output. There are no obvious missing operations for the declared domain of ODS-E conversion and validation.
Maintenance
Related MCP Connectors
MCP server for the Seline Analytics API
MCP compatibility and transport verification server.
MCP compatibility and transport verification server.
MCP compatibility and transport verification server.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Odoo/ODX resources via ODXProxy, enabling programmatic access for MCP-compatible clients.1MIT
- FlicenseAqualityBmaintenanceMCP server for querying Huwise/Opendatasoft data portals. Enables dataset search, metadata retrieval, record filtering with ODSQL, and data export.53-
- FlicenseAqualityDmaintenanceRead-only MCP server for querying solar generation, consumption, and DER telemetry from SolarNetwork via the SolarQuery API. Zero-config against a public demo node.5-
- AlicenseCqualityDmaintenanceMCP server for COBie Excel validation, updates, and PDF extraction.631MIT