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.
- Claude Code
- Claude Desktop / claude.ai
- Codex
- Cursor
- Windsurf
- VS Code
Run:Ask Claude Code:
Open https://bags.example.com/2026-09-03/run.mcap and tell me why the lidar dropped out.
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:
- Claude Code
- Claude Desktop
- Codex
- Cursor
- Windsurf
- VS Code
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
Gotchas
- Hosted Hindsight calls require a
sourceon every call. The hosted server has no filesystem access to your local paths. - The local server needs
ceruliononPATH, or an explicit--binpath. - OAuth sign-in appears on first hosted use.
cloud_instance_connectreturns a short-lived DCV token. Treat it as session access, not a reusable credential.