Skip to main content
Give your robotics agent access to Cerulion in one client configuration. The hosted server drives cloud instances and recording analysis. The local server drives the full Cerulion CLI in your workspace and analyzes local MCAP files.
The hosted server requires you to sign in with the Cerulion account you use at app.cerulion.com. Your client opens the OAuth sign-in flow when it connects for the first time.

Hosted: mcp.cerulion.com

Use the hosted server when your agent needs Cloud Studio instance and DCV control or Hindsight analysis of a public recording, a presigned recording URL, or a private library bag.
Run:
Ask Claude Code:
Open https://bags.example.com/2026-09-03/run.mcap and tell me why the lidar dropped out.
Hosted Hindsight tools do not remember a recording between calls. Pass source="https://..." on every Hindsight call. A signed-in private library bag can use its bag id instead.

Local: cerulion_mcp over stdio

Use the local server when your agent needs workspace, node, graph, topic, schema, bag, replay, robot, or job tools. It also exposes the Hindsight tools for local MCAP files. Install the server from the cerulion-mcp workspace:
Point Claude Code at the workspace you want the agent to operate on:
Ask Claude Code:
Run graphs/perception.yaml for 10 seconds and show the camera and lidar topic rates.
The local server finds cerulion on PATH. Use --bin /path/to/cerulion when the CLI is elsewhere, or set CERULION_MCP_BIN to that path. Use --source recordings/run.mcap to preselect a local recording, or set HINDSIGHT_BAG_DIR for local recording discovery.

What the agent can do

Hosted tools

cloud_instance_connect returns a short-lived DCV authToken, not a durable API credential.

Local tool families

Local jobs are scoped to the workspace that started them. Use that same workspace when you inspect, list, read, or stop a job.

Gotchas

  • Hosted Hindsight calls require a source on every call. The hosted server has no filesystem access to your local paths.
  • The local server needs cerulion on PATH, or an explicit --bin path.
  • OAuth sign-in appears on first hosted use.
  • cloud_instance_connect returns a short-lived DCV token. Treat it as session access, not a reusable credential.