The Roblox Studio MCP plugin (Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Chrrxs/robloxstudio-mcp/llms.txt
Use this file to discover all available pages before exploring further.
MCPPlugin.rbxmx) is a Studio-side bridge that polls the MCP server every 500 ms for queued tool calls, executes them using Studio APIs, and returns the results. The plugin must be present in Studio’s Plugins folder and loaded before the agent can communicate with a live session. There are four ways to install it — pick the one that fits your workflow.
Method 1 — Auto-install (recommended)
The simplest approach: pass--auto-install-plugin when wiring up the MCP server. Every time the server process starts, it copies the .rbxmx bundled with that npm release into Studio’s Plugins folder, keeping the plugin version in sync with the server automatically.
Studio loads plugins only at startup. A full quit-and-reopen is required after the first install or after any plugin update.
Method 2 — Manual CLI install
Run the install command once from any terminal to copy the plugin into the default Plugins folder without starting the MCP server:Method 3 — Roblox Creator Store
Open https://create.roblox.com/store/asset/132985143757536 in your browser while logged into your Roblox account.
Method 4 — Direct file download
Custom Plugins folder
If your Roblox Plugins folder is in a non-standard location, set theMCP_PLUGINS_DIR environment variable before running either --auto-install-plugin or --install-plugin. This works on Windows, macOS, and WSL.
Version mismatch
If the Studio plugin and the running MCP server were installed from different releases, the plugin stays connected but displays a yellow warning banner. Theget_connected_instances response, /health, and /status endpoints also report pluginVersion, serverVersion, and versionMismatch: true.
The connection remains usable, but some newer tool parameters may not be understood by the older plugin. To resolve:
This overwrites the plugin file in the Plugins folder with the version that matches the running server package.
Connecting multiple Studio places
You can open several Studio place files and connect all of them to the same MCP server — there is no need to run separate server instances. Callget_connected_instances to list every connected place and obtain each one’s instance_id, then pass that ID to any tool call to route it to the correct game window.