Choose how to connect
If your assistant supports VS Code extension tools, enable Rivio in its tool picker. You can use Rivio’s native tools directly.
For an MCP connection, Rivio’s built-in setup supports Codex, Claude Code, Cursor, and VS Code. Both connections use the same Rivio tools and your open workspace.
Before you begin
Open your game folder in VS Code with Rivio enabled, trust the workspace, and sign in with an active Rivio subscription. Keep this project open while your assistant works.
MCP setup needs Node.js 18 or newer. Rivio detects it automatically. If it cannot find a compatible installation, setup lets you select an existing Node.js executable or install Node.js and try again.
Connect in a few clicks
No terminal command, extension-folder search, port selection, token editing, or separate MCP package is needed. Repeat Install MCP for each client and project you want to connect.
Rivio starts its workspace endpoint automatically when workspace trust and your active license are verified. It follows connection changes after Rivio restarts, so you do not need to copy new credentials.
- In Rivio’s Explorer, open the … menu beside Settings and choose Install MCP. You can also run Rivio: Install MCP from the Command Palette (Ctrl+Shift+P).
- If your workspace contains multiple folders, select the game project your assistant will work in.
- Choose Codex, Claude Code, Cursor, or VS Code. Rivio configures that client for the selected project.
- Restart your assistant or reload its MCP servers. Approve the Rivio server if your assistant asks, and keep the project open in Rivio.
Try your first request
Your assistant can discover project, source, Studio, playtest, capture, animation, scene, Blender, asset, and audio tools. Individual features still need their connected application or provider.
Rivio MCP connects your assistant to Rivio. For playtests, captures, and input, also enable Roblox Studio’s MCP server in Studio’s Assistant settings; live project synchronization uses the Rivio companion plugin.
- Ask your assistant: “Call rivio_discover with {} to see the available Rivio tools.”
- Then ask: “Inspect my connected project and summarize its top-level structure. Do not change anything.”
- For Studio operations, connect your place first. If several places are connected, name the one your assistant should use.
Control the connection
An enabled MCP connection can edit your trusted workspace, modify connected scenes, run playtests, take captures, and generate audio using your configured provider. Rivio does not show a separate approval dialog for every MCP operation; your assistant’s own approval controls still apply.
Review your assistant’s changes. Audio generation may spend your ElevenLabs credits. Source, tool results, and screenshots can be sent to your chosen AI provider under that provider’s settings and policies.
Run Rivio: Stop MCP to stop the connection for the current Rivio session. Run Rivio: Start MCP or Install MCP to start it again. Opening a new Rivio session attempts automatic startup when its requirements are met.
After updates or connection problems
If you move your project or Node.js, or an extension update changes Rivio’s installation folder, run Install MCP again from the project’s Rivio Explorer and restart your assistant.
If setup reports a conflicting Rivio entry, review that entry in your client’s MCP configuration. Setup preserves other servers and settings; it does not overwrite a conflicting entry. Use View Details on a setup error to see what needs attention.
Keep one Rivio window open for the intended workspace. If startup failed, check your active subscription and workspace trust, then run Rivio: Start MCP and reconnect your assistant.
If a long-running edit loses its connection, inspect the result before repeating the request. A disconnected assistant does not necessarily mean the operation was cancelled.