OddessyMCP
READ-ONLY BETA · AWS US-EAST-1 (N. VIRGINIA)

Operational context
for trusted agents.

Give agentic users governed, tenant-scoped access to edge devices, approved releases, model provenance and live service health—without exposing plant actuation or secrets.

Connect an agent Read llms.txt
STREAMABLE HTTP ENDPOINT https://mcp.oddessy.io/mcp
01

Tenant scoped

Every fleet query uses the authenticated owner partition. Personal tokens expire, can be revoked immediately and are stored only as SHA-256 digests.

02

Read-only by design

Nine tools expose context, not control. There are no PLC writes, shell execution, release approvals, deployments, enrolments or secret retrieval.

03

Auditable

Tool calls record tenant, actor, scopes, tool, request hash, result, runtime region and trace ID with a defined retention window.

Oddessy MCP read-only trust boundary from authenticated clients through tenant-scoped tools and audit to platform context, with plant-control actions explicitly denied.
Authenticated operational context stays on the read-only side of the industrial-control boundary. Open the diagram for the full-size vector.
LIVE TOOL SURFACE

Small enough to reason about.

The first release deliberately keeps the capability boundary narrow. Tool schemas reject unknown fields, release results never include download credentials, and all tools declare read-only annotations.

fleet.list_devices

Fleet health, hardware, runtime and heartbeat.

fleet.get_device

One device, telemetry, model manifest and OTA state.

release.list_approved

Checksum-published release metadata.

model.list_provenance

Identity, digest, runtime and execution location.

status.get_hosted_services

Infrastructure and real-model canary state.

integration.list

Matter, TTN and signed connections without credentials.

iot.list_devices

Discovered tenant IoT endpoints.

iot.list_recent_events

Normalized events for a tenant-owned integration.

docs.get_page

Canonical deployment and safety guidance.

PHYSICAL-WORLD BOUNDARY

Context is not actuation.

Oddessy MCP results are operational context. They are not evidence that a physical action occurred and do not replace PLC logic, safety relays, interlocks, emergency stops, machine guarding, site procedures or accountable human approval.

CONNECT

One endpoint. OpenClaw or any MCP client.

  1. Sign in to Oddessy Platform.
  2. Create an expiring token under Agent access.
  3. Run the npm stdio adapter with the token in a secret environment variable.

OpenClaw users can add the same adapter with openclaw mcp add oddessy --command npx --arg -y --arg @oddessy-io/mcp, then run openclaw mcp doctor oddessy --probe.

{
  "mcpServers": {
    "oddessy": {
      "command": "npx",
      "args": ["--yes", "@oddessy-io/mcp"],
      "env": { "ODDESSY_API_TOKEN": "${ODDESSY_API_TOKEN}" }
    }
  }
}