IndagateDOCUMENTATION
AGENTIC ACCESS Beta

Connect an agent to Indagate

Use governed Streamable HTTP MCP to inspect fleet, monitoring, determinations, integrations, outbound delivery, hosted status and canonical docs.

Last updated 27 July 2026 · Documentation version 2026.07
Read-only beta

Indagate MCP exposes context and operational reads. It cannot enrol a device, deploy software, retrieve secrets, execute a shell command, write a PLC tag or bypass an approval.

Indagate MCP trust boundary from OpenClaw and other clients through token and schema validation to tenant-scoped read-only tools, platform context and audit
The MCP hard-deny boundary excludes plant writes, shell execution, enrolment, deployment, approval and secret retrieval.

Endpoint

https://mcp.indagate.ai/mcp

The hosted service implements stateless Streamable HTTP with JSON responses and negotiates MCP protocol 2025-11-25 while retaining compatibility with selected earlier protocol versions.

1. Create a token

  1. Sign in to Indagate Platform.
  2. Open Account → Personal API tokens.
  3. Create a named token with the shortest practical expiry and copy it once.
  4. Store it in your MCP client secret configuration as a Bearer token.

2. Preview the npm stdio adapter

The adapter is a release candidate pending npm registry publication. Native remote HTTP clients can connect to the live hosted endpoint directly today.

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

After publication, the adapter will forward to https://mcp.indagate.ai/mcp. Use secret injection rather than committing the literal token.

3. OpenClaw

The command below applies after the release-candidate adapter is published. Store ODDESSY_API_TOKEN in the OpenClaw Gateway or agent process secret environment. The token is inherited by the adapter and is not placed in the command.

openclaw mcp add oddessy   --command npx   --arg -y   --arg @oddessy-io/mcp

openclaw mcp doctor oddessy --probe

OpenClaw clients that support remote Streamable HTTP MCP can connect directly to the live endpoint. Keep the static token in the client's secret configuration rather than a literal checked-in header.

4. Start with a safe question

List my Indagate devices that need attention. Separate observed
telemetry from inference, identify stale heartbeats, and do not
claim that any physical action occurred.

Authorization discovery

The MCP service publishes RFC 9728 protected-resource metadata at the well-known resource URL. Personal tokens provide immediate beta access; delegated OAuth client onboarding is being expanded for supported enterprise clients.