# Oddessy MCP

> Governed, tenant-scoped, read-only access to Oddessy industrial edge fleet context. The production Streamable HTTP endpoint is `https://mcp.oddessy.io/mcp`.

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

## Connect

- [MCP quickstart](https://docs.oddessy.io/mcp): Create an expiring token and configure a client.
- [OpenClaw and learning pathways](https://docs.oddessy.io/pathways): Guided agent, beginner and cross-industry setup.
- [Tools](https://docs.oddessy.io/mcp/tools): Nine live tools and their input contracts.
- [Resources and prompts](https://docs.oddessy.io/mcp/resources): Canonical context resources and guided reviews.
- [Full Oddessy context](https://docs.oddessy.io/llms-full.txt): Product, API, deployment and trust context.
- [Protected-resource metadata](https://mcp.oddessy.io/.well-known/oauth-protected-resource): Authentication metadata.

## Live read-only tools

- `fleet.list_devices`
- `fleet.get_device`
- `release.list_approved`
- `model.list_provenance`
- `status.get_hosted_services`
- `integration.list`
- `iot.list_devices`
- `iot.list_recent_events`
- `docs.get_page`

## Live resources

- `oddessy://docs/overview`
- `oddessy://docs/safety-boundary`
- `oddessy://docs/model-provenance`
- `oddessy://status/hosted`

## Live prompts

- `inspect_fleet_health`
- `review_model_provenance`

## Boundaries

MCP v1 cannot write PLC values, execute a shell, enrol devices, mutate deployments, approve releases, return artifact download credentials, retrieve secrets or actuate machinery. Tool calls are tenant-scoped and audited.

## Operations

- [Hosted status](https://status.oddessy.io)
- [Machine-readable status](https://status.oddessy.io/api/status)
- [Security](https://docs.oddessy.io/security)
- [Privacy](https://docs.oddessy.io/privacy)
- Contact: info@oddessy.io