RoIDE gives AI apps real tools for your Roblox game. They explore your scripts, write and edit code, and read Studio's Output, while every change syncs to Roblox Studio.
RoIDE's MCP server speaks Roblox, not just files. Through it, your AI app can:
The RoIDE app adds its MCP server to Claude Desktop, Claude Code and Cursor for you. Any other app that supports the Model Context Protocol connects the same way.
The server knows how Scripts, LocalScripts and ModuleScripts are named, which services sync, and how folders map to your game, and it gives the AI a guide to follow, so the code it writes is code Studio accepts.
Only scripts and their folders sync: the AI can't touch your map, models, terrain or UI. RoIDE runs on your computer, and every change is a file you can review or undo with git.
MCP (Model Context Protocol) is how AI apps like Claude and Cursor use outside tools. A Roblox MCP server gives them tools for your Roblox game: RoIDE lets them list, read, search, write and move your scripts and read Studio's Output.
Claude Desktop, Claude Code and Cursor are set up in one click from the RoIDE app. Any other app that supports MCP can connect the same way.
For changes to show up live, yes: open your place and the RoIDE plugin connects on its own. Without Studio, your AI still works on the script files, and the plugin's push and pull bring Studio up to date when you open the place.
RoIDE only syncs scripts and the folders that hold them. Parts, models, terrain and UI are never touched, and every script is a file you can review or roll back with git.
RoIDE keeps your scripts on your computer and talks to Studio and your AI apps locally. The AI app you connect sends what it reads to its own provider under its own terms.