Skip to main content

Connect'O — MCP & OAuth agents

Connect'O exposes Wast-O data to agents (Cursor, SI automations) through a dedicated MCP server, authenticated with OAuth2 client_credentials.

Versus the public API

The public /public API stays anonymous and citizen read-only.
Connect'O = machine credentials bound to one cityGroupId, scopes, audit, and optional bounded writes.

Endpoints​

URL
MCP (Streamable HTTP)https://mcp.wast-o.com/mcp
Healthhttps://mcp.wast-o.com/health
OAuth tokenhttps://api.wast-o.com/oauth/token
Who am IGET https://api.wast-o.com/oauth/me

Get credentials​

  1. Wast-O console → Settings → Connect'O.
  2. Enable Connect'O on the city group if needed.
  3. New client → copy client_id / client_secret (shown once).
  4. Scopes: wasto.mcp.read (default), optional wasto.mcp.write.

Token​

curl -s -X POST https://api.wast-o.com/oauth/token \
  -H 'Content-Type: application/json' \
  -d '{
    "grant_type": "client_credentials",
    "client_id": "wasto_cc_…",
    "client_secret": "…"
  }'

Do not reuse a console user JWT for agents.

See also​