A Roblox Studio MCP server.
Roqer’s Studio tools are an open-source MCP server and Studio plugin. Connect them to Claude Code, Codex, Cursor, or any other MCP client, and your own agent can inspect, edit, and playtest the place you have open.
What it can do
Inspect and edit a place
- Inspect place identity, instances, properties, attributes, project structure, scripts, and connected Studio instances.
- Apply atomic property updates and revision-aware script replacements or localized edits.
- Run custom Luau in edit mode when a structured operation is not enough.
Debug and automate playtests
- Run Luau in live server and client VMs.
- Start and stop solo or multi-client sessions, inspect each peer, capture logs, and record breakpoint hits without pausing.
- Simulate network and device conditions, inspect runtime UI, and interact with it by selector or bounded input.
Collect evidence and diagnose performance
- Capture Studio screenshots, script and micro-profiler recordings, memory breakdowns, and scene-cost analysis.
- Export and import
.rbxmfiles through explicit paths. - Search, preview, sanitize, and insert Creator Store assets.
Read Roblox references
- Fetch the official engine and Luau documentation from inside the session.
Set it up
You need Node.js 20 or newer and Roblox Studio. Build the server and plugin from the repository:
git clone https://github.com/S4US/Roqer.git
cd Roqer
npm install
npm run build:all
Then add it to your client, replacing C:\path\to\Roqer with where you cloned it. --auto-install-plugin installs the matching Studio plugin whenever the client starts the server. Fully close and reopen Studio after the first install.
Claude Code
claude mcp add robloxstudio -- node C:\path\to\Roqer\packages\robloxstudio-mcp\dist\index.js --auto-install-plugin --plugin-path C:\path\to\Roqer\studio-plugin\MCPPlugin.rbxmx
Codex
codex mcp add robloxstudio -- node C:\path\to\Roqer\packages\robloxstudio-mcp\dist\index.js --auto-install-plugin --plugin-path C:\path\to\Roqer\studio-plugin\MCPPlugin.rbxmx
Cursor and other JSON-configured clients
{
"mcpServers": {
"robloxstudio-mcp": {
"command": "node",
"args": [
"C:\\path\\to\\Roqer\\packages\\robloxstudio-mcp\\dist\\index.js",
"--auto-install-plugin",
"--plugin-path",
"C:\\path\\to\\Roqer\\studio-plugin\\MCPPlugin.rbxmx"
]
}
}
}
If the client cannot find node, give it the absolute path to the Node executable instead. The plugin and server must come from the same build.
Several places at once
Connect every open Studio place to the same server. The client lists them with get_connected_instances and passes an instance_id to choose which place a call acts on, so a write never lands in the wrong game.
A read-only edition
The inspector edition exposes only read tools and keeps the place read-only, for an agent you want looking but not touching. It installs the same way from packages/robloxstudio-mcp-inspector.
Security
The bridge between the server and Studio listens on 127.0.0.1 only, and every HTTP endpoint that can run a tool requires a token the server creates on first run. Nothing is exposed to your network unless you configure it.