What is Rerun Viewer MCP?
Rerun Viewer MCP is the viewer-mcp subcommand of the rerun command-line tool, made by Rerun, the company behind the open-source viewer for robotics, spatial and multimodal data. It speaks MCP over stdio and connects over gRPC to a Viewer that is already running, by default at 127.0.0.1:9876. An agent can open and close recordings, move the time cursor, read and rewrite the blueprint (Rerun's layout), read recording and dataset schemas, run command palette commands and save screenshots.
It first shipped in Rerun 0.34 on 6 July 2026 and has grown in most releases since; the current version is 0.43.2, released on 13 November 2026. The rerun-io/rerun repository has about 11,830 stars and is dual-licensed MIT and Apache-2.0.
How to install Rerun Viewer MCP
claude mcp add rerun -- rerun viewer-mcpIs Rerun Viewer MCP worth it?
The strongest argument for Rerun Viewer MCP is that the Viewer's maker ships it. It lives in the rerun binary, needs no extra package, and is generated from the same viewer_control.proto service that drives the Viewer, so the high-level rerun_* tools follow each release. Rerun's own launch note pitched it at a loop that is otherwise tedious: an agent writes logging code, sends the recording to the Viewer, looks at the result and fixes what does not show up.
The tool set is specific. rerun_open and rerun_close handle recordings and datasets, rerun_set_time_cursor and rerun_set_location navigate, rerun_get_blueprint and rerun_set_blueprint read and edit the layout in full or partial mode, rerun_save_screenshot captures the view, and rerun_get_logs and per-view warnings tell the agent what went wrong. Since 0.39 the agent can also list and run any command palette command. Lower-level UI tools that click widgets exist as a fallback, and the docs warn they are slow on context and break when the layout changes.
The catch: the docs publish no authentication for the Viewer's gRPC server, and the examples connect in plaintext. The CLI manual gives 0.0.0.0 as the default bind address for the Viewer's port 9876, which also receives logged data, while the gRPC reference says the control service only accepts connections from the local machine. In practice any local process can drive your Viewer, and a recording you open is read and screenshotted for your model provider.
Our take: if your team already logs robot or perception data to Rerun, this is a cheap win for debugging and building layouts, and it runs headless in CI. It is a viewer remote, not a data pipeline, so it complements rather than replaces a ROS or database server.
Where it earns its place
A perception engineer at a 30-person robotics start-up
Find out why a point cloud does not appear in the Viewer
Have the agent run the logging script, open the recording, then read per-view warnings, rerun_get_logs and the recording schema to spot the wrong entity path or missing transform. It replaces a round of clicking and guessing; the fix still goes through code review.
A research lab sharing driving logs with a partner
Build a standard layout for every dataset
Ask the agent to set up views with rerun_set_blueprint in partial mode, check the result with rerun_save_screenshot and save the blueprint for the team. Free apart from model tokens.
An ML platform team running nightly evaluations
Attach screenshots of failure cases to a CI report
Start the Viewer with rerun --headless, connect viewer-mcp with --endpoint, and have the agent jump to flagged timestamps and save screenshots for the report.
Before you commit
- Setup
- Install the rerun CLI, start a Viewer, then register the server with claude mcp add rerun -- rerun viewer-mcp (or codex mcp add). Add --endpoint http://127.0.0.1:9876 to tie it to one Viewer; otherwise the agent picks one with rerun_connect.
- Integrations
- stdio MCP to the client, gRPC ViewerControlService to the Viewer. Documented for Claude Code, Codex and any client that reads an mcp.json entry. Recordings and datasets on a connected Rerun server can be opened directly.
- Data and privacy
- Runs locally; what the agent reads, including screenshots, goes to your model provider. The Viewer's gRPC port 9876 binds to 0.0.0.0 by default and no authentication is published; the control service accepts only local connections. Closing a recording leaves files on disk alone but drops unsaved blueprint edits.
- Cost at scale
- Free; included in the open-source rerun CLI. The only running cost is model tokens.
- Limits
- Needs a running Viewer, headless or not. Low-level UI tools use a lot of context and break when the layout changes. Tool names still change between releases, as when 0.41 renamed rerun_get_viewer_state to rerun_get_state.
What’s good
- Built into the rerun CLI by the Viewer's maker
- Typed tools for recordings, time cursor, blueprints and screenshots
- Works against a headless Viewer in CI
- Frequent releases, 0.43.2 on 13 November 2026
What’s not
- No published authentication on the Viewer's gRPC server
- Viewer port binds to all interfaces by default
- Low-level UI tools are slow and brittle
- Only useful if your data is already in Rerun
Best for
Robotics, perception and spatial-computing engineers who already log to Rerun and want an agent to inspect recordings, debug logging code and set up layouts.
Rerun Viewer MCP alternatives
Rerun Viewer MCP: common questions
- Is Rerun Viewer MCP worth it?
- A first-party way to let an agent look at the same robot data you do, and check its own logging code against it. We rate it 4.2 out of 5.
- How much does Rerun Viewer MCP cost?
- Free and open source (MIT or Apache-2.0); included in the rerun CLI.
- What are the downsides of Rerun Viewer MCP?
- No published authentication on the Viewer's gRPC server; viewer port binds to all interfaces by default; low-level UI tools are slow and brittle; only useful if your data is already in Rerun.
- Who is Rerun Viewer MCP best for?
- Robotics, perception and spatial-computing engineers who already log to Rerun and want an agent to inspect recordings, debug logging code and set up layouts.
- How much does Rerun Viewer MCP cost for a team or in production?
- Free; included in the open-source rerun CLI. The only running cost is model tokens.
- Is Rerun Viewer MCP safe for company data?
- Runs locally; what the agent reads, including screenshots, goes to your model provider. The Viewer's gRPC port 9876 binds to 0.0.0.0 by default and no authentication is published; the control service accepts only local connections. Closing a recording leaves files on disk alone but drops unsaved blueprint edits.
- What are the best Rerun Viewer MCP alternatives?
- The closest alternatives we have reviewed are ROS MCP Server and Grafana MCP Server.
Answers checked Nov 18, 2026.