Just talk to your agent
Connect the server, click the MCP button in Studio, then describe what you want. The agent picks the right tools, runs them in your open session, screenshots the result to check its own work, and iterates while you watch.
Build a glassy settings panel with a volume slider and a close button, then animate it sliding in.
Scatter 30 trees across the terrain, avoiding the water, and add soft evening lighting with fog.
Read this screenshot and rebuild this shop UI pixel-for-pixel.
Sync the whole place to disk so I can edit scripts in my editor, two-way and live.
Built for real Studio work
29 focused tools, not one giant "run code" hammer.
29 focused tools
Instances, properties, scripts, raw Luau, UI, terrain, lighting, effects, tweens, camera, animation, audio, physics, marketplace assets, spatial queries, bulk edits, playtests, screenshots.
Two-way sync
Mirror the live DataModel to local files and back. Edit scripts in your own editor; changes flow both ways. Multiple Places sync at once, each on its own engine.
Multi-agent
Claude Code, Codex and Antigravity can all drive the same Studio session concurrently through one shared broker.
It sees what it builds
capture_studio screenshots the real viewport, so the agent closes the loop instead of building blind.
Live dashboard
Watch connected agents, plugin status, the command queue and sync state in real time at 127.0.0.1:3690.
Zero maintenance
npx … @latest auto-updates the server; the Studio plugin and agent skills self-install on startup.
Up and running in two steps
You never start the server by hand; your AI agent launches it with the command you register.
claude mcp add roblox-mcp-pro -- npx -y roblox-mcp-pro@latest
codex mcp add roblox-mcp-pro -- npx -y roblox-mcp-pro@latest
gemini mcp add roblox-mcp-pro npx -y roblox-mcp-pro@latest
Paste into the client's MCP config (Claude Desktop, Cursor, Windsurf, Cline). Add the entry inside the existing mcpServers object, not the whole file.
{
"mcpServers": {
"roblox-mcp-pro": {
"command": "npx",
"args": ["-y", "roblox-mcp-pro@latest"]
}
}
}Register the server
Use the command above for your client. npx downloads & runs the package on demand (no clone, no build). @latest keeps it auto-updated.
Install the Studio plugin
Auto-installs on first run, or do it now: npx roblox-mcp-pro@latest install-plugin. Windows → %LOCALAPPDATA%\Roblox\Plugins, macOS → ~/Documents/Roblox/Plugins.
Connect & verify
In Studio click the Roblox MCP Pro toolbar button (so it's highlighted), then ask your agent to call system_info. You should see pluginConnected: true.
Optional environment variables
| Variable | Default | Meaning |
|---|---|---|
ROBLOX_MCP_PORT | 3690 | Bridge port (the plugin must match). |
ROBLOX_MCP_TOKEN | none | Shared secret; also set it in the plugin. |
ROBLOX_MCP_NO_PLUGIN_AUTOINSTALL | off | 1 disables auto-installing the plugin. |
ROBLOX_MCP_NO_SKILL_AUTOINSTALL | off | 1 disables auto-installing agent skills. |
ROBLOX_MCP_NO_OPEN_DASHBOARD | off | 1 stops the dashboard opening on startup. |
29 tools
Each does one job well; the agent composes them.
Core
Read and change the DataModel.
World & visuals
Shape the scene and how it looks.
Content
Author UI, audio, scripts and assets.
Sync, sessions & Studio
Move data to disk, route agents, run playtests.
How it works
Three processes, two hops, and several agents on one Studio session.
AI Agent A ─MCP stdio─▶ MCP client ─┐ AI Agent B ─MCP stdio─▶ MCP client ─┼─HTTP 127.0.0.1:3690─▶ Broker ◀─long-poll─ Studio Plugin (Luau) AI Agent C ─MCP stdio─▶ MCP client ─┘ queue + dashboard dispatch handlers
MCP client
Exposes the tools over stdio. Each AI agent spawns its own.
Broker
One shared localhost process owns port 3690, queues commands, talks to the plugin. The first client auto-spawns it; the rest just connect, so several agents drive one Studio session at once.
Studio plugin
Long-polls the broker, runs each command in Studio, and posts the result back.