Integrations

MCP

R3NE ships a Model Context Protocol (MCP) server that lets any MCP-compatible client, Claude Desktop, Claude Code, Codex, or your own agent, inspect the live graph and propose edits that R3NE applies on the next frame.

How it works

The R3NE app exposes a local HTTP API on localhost:19780 while it’s running. The r3ne MCP server is a small Node program that speaks MCP over stdio to your client and forwards each tool call to that local API. Pointing any MCP client at the server is enough to give the model live access to your composition.

Install

In Claude Code it’s a plugin you add with two commands; Claude Desktop, Codex and other clients point at the same bundled server. The Install the MCP guide walks through each client step by step.

/plugin marketplace add FranciscoOutonB/r3ne-app
/plugin install r3ne@r3ne-app

Tools the model can call

  • health, ping the app to confirm the API is reachable.
  • get_graph, full state of the live graph: nodes, parameters, connections, shader sources.
  • list_node_types, every node category R3NE can spawn.
  • create_node / delete_node, add or remove a node.
  • connect_nodes / disconnect, wire ports together.
  • set_params, change parameter values, with optional easing.
  • create_shader / edit_shader / get_shader_errors, author MSL fragments; compile errors come back to the model.
  • list_presets, built-in preset compositions to seed off of.
  • create_composition, bundle a whole graph in a single call. The nodes are arranged left to right with the Output on the right.
  • arrange_graph, tidy an existing canvas the same way, keeping the order of stacked Post-FX.
  • get_node / snapshot, read one node’s ports and values, or grab its rendered image so the model can see the result.
  • import_mesh / look_at, bring a 3D model into a scene and aim cameras and lights at a point.
  • save_project / open_project, save the composition or open another .r3d.
  • clear_graph, wipe the canvas back to a fresh Root.

Try it

With the server connected and R3NE open, try a prompt like:

Make the camera feel like a chrome ball lit by neon.
Add bloom, a feedback trail, and pull the saturation up.

The model calls the tools in sequence and the graph updates live — new nodes appear on the canvas and the output changes on the next frame.

Safety

  • The API listens on localhost only. Expose it remotely only behind a tunnel you control (ngrok, Tailscale, etc.).
  • Every mutation is undoable, ⌘Z rolls back the last batch of model edits as a single step.
  • Quit R3NE and the API server goes down with it, there’s no background process left running.