An MCP server and Roblox Studio plugin that enables AI assistants to edit places, run Luau code, drive playtests, and manage assets within Roblox Studio.
Also known as zrob407/studio-bridge, @zrob407/studio-bridge
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 2, 2026
- License
- —
What is Studio Bridge MCP?
Studio Bridge is an MCP server and Roblox Studio plugin that enables AI assistants to edit places, run Luau code, drive playtests, and manage assets within Roblox Studio.
Summary generated from the project's README
About Studio Bridge MCP server
Roblox developers can automate complex game creation tasks by connecting AI assistants like Claude Code directly to Roblox Studio. This MCP server and plugin combination allows an AI to read and edit place files, execute Luau code, and manage assets without manual clicking. It is designed for Windows users running Node 22 or newer, providing a bridge between the coding assistant and the Studio environment through a local connection on port 3010.
Beyond simple scripting, the server provides specialized tools for terrain generation, lighting adjustments, and UI responsiveness testing. Developers can use it to perform bulk asset publishing, run automated playtests with keyboard and mouse input, and conduct deep audits of their place to find risky code or unowned assets. While the core functionality is free for commercial use, a Pro version offers additional capabilities like dead-code detection and localization. The system is built to be efficient, using batch commands to minimize token usage and prevent timeouts during long-running tasks.
What you can do with it
- 1Automated asset managementAn AI can export and publish multiple animations or audio files to a group in a single operation.
- 2Automated playtesting and QAThe assistant can drive a character through a game and report errors found during the session.
- 3UI responsiveness auditingDevelopers can check if their user interfaces scale correctly across different mobile and console devices.
- 4Security and code auditingThe server can scan a project to identify risky scripts or assets that the developer does not own.
Written from the project's README. Every use case is checked against a quote from it.
How to install Studio Bridge MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Studio Bridge MCP in Claude Code
$ claude mcp add studio-bridge -- npx -y @zrob407/studio-bridgeInstall Studio Bridge MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"studio-bridge": {
"command": "npx",
"args": [
"-y",
"@zrob407/studio-bridge"
]
}
}
}Install Studio Bridge MCP in VS Code
.vscode/mcp.json
{
"servers": {
"studio-bridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@zrob407/studio-bridge"
]
}
}
}Install Studio Bridge MCP in VS Code CLI
$ code --add-mcp '{"name":"studio-bridge","type":"stdio","command":"npx","args":["-y","@zrob407/studio-bridge"]}'Install Studio Bridge MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"studio-bridge": {
"command": "npx",
"args": [
"-y",
"@zrob407/studio-bridge"
]
}
}
}Install Studio Bridge MCP in Codex
$ codex mcp add studio-bridge -- npx -y @zrob407/studio-bridgeInstall Studio Bridge MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.studio-bridge] command = "npx" args = ["-y", "@zrob407/studio-bridge"]
Install Studio Bridge MCP in Gemini CLI
$ gemini mcp add -s user studio-bridge npx -- -y @zrob407/studio-bridgeInstall Studio Bridge MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"studio-bridge": {
"command": "npx",
"args": [
"-y",
"@zrob407/studio-bridge"
]
}
}
}Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablezrob407/studio-bridge is public and reachablegithub.com/zrob407/studio-bridge ↗Pass
- Package names this repository as its source@zrob407/studio-bridge names zrob407/studio-bridge as sourcenpmjs.com/package/@zrob407/studio-bridge ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @zrob407/studio-bridgenpmjs.com/package/@zrob407/studio-bridge/v/0.6.13#provenance ↗Pass
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-02github.com/zrob407/studio-bridge ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @zrob407/studio-bridgePass
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubStudio Bridge
An MCP server and Roblox Studio plugin that let an AI coding assistant such as Claude Code read and edit a place, run Luau, drive playtests, take screenshots and publish assets. Free to use, including for commercial games, under the Studio Bridge License (source-available, see License below); no dependencies beyond Node 22.
New: Studio Bridge Pro. Paid add-on packs are now available, Snapshots and diffs, QA playtests, a place audit report, a dead-code finder and localization. The free program is unchanged. Pro has its own separate license; see Studio Bridge Pro.
Studio Bridge speaks standard MCP, so it is not tied to one assistant. It is used and tested with Claude Code. Setup for OpenAI's Codex CLI is included (see Install), but it has not yet been tried with Codex itself.
Quick start
npm install -g @zrob407/studio-bridge
studio-bridge install
Restart Claude Code and Roblox Studio, then allow HTTP requests and Script Injection for "Studio Bridge" if Studio asks. Run studio-bridge doctor if anything looks wrong. Windows, Node 22 or newer, Roblox Studio and Claude Code are required (Codex CLI setup is included but untested). macOS is supported but untested, and Linux works through Wine and is untested; see the macOS and Linux sections.
Everyday time-savers
These are the things that take the most clicking by hand and the least time with Studio Bridge.
- Publish assets in bulk.
asset_publish_instancesexports many instances at once (for example every KeyframeSequence in a rig's AnimSaves folder) and uploads them all, named "{name} {rig}".asset_upload_batchuploads many files at once, skips anything already uploaded in the last 24 hours so an interrupted run resumes instead of duplicating, and writes the results to a file instead of flooding the chat. After re-uploading,animation_idsandaudio_manageswap every old id in the place for the new one in a single call. - Audit the whole place in seconds.
asset_auditlists every asset id the place references and who owns each, so you find the ones that will break or that you do not own.script_scanranks risky code (require by id, loadstring, obfuscation, DataStore, teleports),script_dependenciesfinds unused modules andrequire(assetId)calls, andphysics_reportandaudio_reportcatch loose parts, void parts, missing sounds and duplicates. - Edit hundreds of things in one step.
batchruns up to 50 edits as one undo.instance_bulksets, adjusts (add or multiply relative to the current value) or deletes across everything that matches a filter, with dry runs.instance_rename,instance_duplicate(rows, grids and circles of copies),snap_gridandinstance_pivotreplace a lot of dragging. - Build a world quickly.
terraingenerates hills with a biome, water level and seed, then smooths, fills and recolors;environmentswitches lighting between day, sunset, night, fog and more;scatterdrops trees, rocks or props across the ground with spacing, slope alignment and random scale;spatial_findfinds flat spots, free space and spawn points;spatial_checktells you whether something floats or overlaps, what it touches, and how much of an area a character can walk on. - UI that fits every device.
ui_buildmakes a whole GUI from one description,ui_autoscaleconverts a pixel-based GUI to responsive Scale (respecting padding, anchors and layouts), andui_responsive_checklays it out on real phones, tablets and consoles through Studio's device emulator and reports what runs off the screen, is too small to tap or has tiny text.device_emulatorswitches devices for screenshots. - Playtest without touching the keyboard.
character_movewalks the character to a spot with pathfinding,input_keyboardandinput_mousesend real key and mouse input,gui_clickpresses buttons by path, andrun_testand screenshots report what happened. - Find and insert assets safely.
asset_searchlooks through the free Creator Store andasset_insertbrings a model in after scanning it; scripts are removed unless you keep them, because free models can hide malicious code.generate_modelmakes a model from a text prompt using Roblox's own generation. - Animation without the editor.
animation_createbuilds keyframes from a description,animation_editretimes, reverses and adds markers,animation_playpreviews it on a rig while you screenshot, andanimation_posefreezes any frame. - Documentation at hand.
roblox_docssearches and reads the official Roblox documentation, so answers come from the current API reference. - Keep the AI's context small.
studio-bridge settings tools coreoffers only the 28 everyday tools and adds groups on demand (see Tool groups).
What you can ask for
- "Export every animation in this rig's AnimSaves folder and publish them to my group."
- "Find every script that uses DataStore and list the risky ones."
- "List every asset this place uses that I do not own."
- "Generate a rocky island with a beach, scatter palm trees on it, and switch the lighting to sunset."
- "Build a main menu, make it responsive, and check it on an iPhone, an iPad and an Xbox."
- "Run a playtest, walk the character to the shop door, click Buy and tell me what errors show up."
- "Rename these 40 parts, space them out in a circle, and snap them to the grid."
Studio Bridge exposes seventy-nine tools, listed under Tools below. Roblox's own Studio MCP server is a separate server, so you can register both (they have not been tested together). As of this writing it has 26 tools centered on scripts, search, playtesting and generation; Studio Bridge adds terrain, lighting, spatial tools, animation and audio editing, UI scaling and device checks, bulk editing and publishing, audits and more.
Why Studio Bridge
- It does not time out and force a Studio restart. Every command has a deadline and can be cancelled, results survive a reconnect, and the plugin reloads itself when it changes.
- Fewer calls and tokens.
batchruns up to 50 edits in one call, the server instructions are a few hundred characters, and tool groups keep the tool list small. - It is easy to trust. It listens only on
127.0.0.1, needs a secret on every request, verifies the plugin's signature, collects no telemetry, and ships with build provenance. - Free for commercial games. See License.
Recently added
- Tool groups (
studio-bridge settings tools), a Studio status window, and tokenless publishing to npm with provenance. - Terrain, lighting presets, scatter, spatial and physics tools, effects, tweens.
- Animation authoring, editing and preview; audio management with preview.
- UI autoscale, responsive checks on real devices, and the device emulator.
- Playtest control: character movement, keyboard and mouse input.
- Asset search, safe insert and model generation; searchable Roblox documentation.
- Bulk editing, renaming and duplication; script dependency and audit tools.
Install
Windows, Roblox Studio and Claude Code are required. macOS is supported but untested, and Linux works through Wine (see the macOS and Linux sections below).
With npm (recommended). Needs Node 22 or newer: npm install -g @zrob407/studio-bridge, then studio-bridge install. It runs on Node, which is signed by the OpenJS Foundation, so Windows protections such as Smart App Control do not block it the way they can block an unsigned exe. Data lives in %LOCALAPPDATA%\StudioBridge like the exe's, and studio-bridge update upgrades it through npm. The package is published on npm with build provenance, which npm audit signatures can verify.
With the exe (no Node needed). The exe is not code-signed, so Windows may warn about or block it (see Verifying a download); use npm or the source if that happens. Download studio-bridge-<version>.exe from the releases page and double-click it, or run studio-bridge.exe install in a terminal. It copies itself to %LOCALAPPDATA%\StudioBridge, creates a secret token, writes the Studio plugin, and registers itself with Claude Code (claude mcp add --scope user). Then restart Claude Code and Roblox Studio. If Studio asks, allow HTTP requests and Script Injection for "Studio Bridge".
If an earlier source install is registered with Claude Code (node server.mjs), the installer finds it, switches the registration to the exe, reuses its token (so an open Studio window keeps working) and copies over uploads.json and asset-owners.json if the new location has none. It never overwrites existing files and leaves the old folder alone; --migrate-from <folder> does the same for a folder you point it at. Old plugin files such as ClaudeStudioBridge.rbxmx are removed so only one copy loads.
From source (Node 22 or newer). Run node cli.mjs install in this folder. node install.mjs still works and does the same.
With OpenAI Codex CLI. studio-bridge install --client codex (or --client all for Claude Code and Codex) adds a [mcp_servers.studio-bridge] entry to ~/.codex/config.toml (or $CODEX_HOME/config.toml), keeping everything else in that file, with a 30-second startup timeout and a 600-second tool timeout; Codex's default tool timeout is 60 seconds, which would cut off playtests and large asset batches. Restart Codex afterwards. To add it by hand:
[mcp_servers.studio-bridge]
command = "C:\\Users\\you\\AppData\\Local\\StudioBridge\\studio-bridge.exe"
args = ["serve"]
startup_timeout_sec = 30
tool_timeout_sec = 600
The setup follows the configuration format in OpenAI's published Codex documentation. The test suite checks the server against the official MCP client library, and doctor reports a Codex registration. If something does not work with Codex, please open an issue.
Only one bridge runs at a time, because it owns port 3010 and the Studio plugin connects to that port. When you upgrade, a newer server that finds an older one still running asks it to stop (using the shared token) and takes over the port, so you do not have to end the old process by hand. A server of the same version, or an older one, never replaces another. That also means two AI clients, for example Claude Code and Codex, cannot use the bridge at the same time: the second one to start finds the port busy and stops with a message.
Other commands: update downloads the latest release, checks it against the release's SHA256SUMS.txt and installs it over the old one (update --check only reports), doctor checks the installation and mentions when an update is available (--offline skips that), uninstall removes the plugin and the registration (--purge also deletes the data folder), version prints the version. install --no-register leaves the Claude Code configuration alone and prints the command to run yourself; install --standalone writes the full plugin instead of the self-updating loader.
To change a tool without rebuilding the exe, put a replacement file under %LOCALAPPDATA%\StudioBridge\overrides using the same relative path (for example handlers\script_get.luau or tools.json); it wins over the embedded copy.
To build the exe yourself: npm ci then npm run build (Windows, Node 24). The result is dist\studio-bridge.exe.
Updates
Three layers, from least to most automatic. Only the first two are on by default.
- A notice. When the bridge starts it asks GitHub for the latest release, at most once a day, and
studio_listthen mentions an available update. Nothing is downloaded. Turn it off withstudio-bridge settings check-updates off. - Update on request. Tell Claude to update Studio Bridge. The
bridge_updatetool reports the new version first and only downloads, verifies and installs it when it is called withconfirm: true, which Claude should do only after you agree. You then run/mcp. You can also runstudio-bridge updateyourself. - Auto-update (off by default).
studio-bridge settings auto-update onmakes the bridge download, verify and install new releases on its own when it starts; they take effect at the next restart and are logged inupdate-log.txtin the data folder. Because this replaces the program without asking, it is opt-in; the checksum is verified first, but releases are not code-signed.
Every download is checked against the SHA256SUMS.txt published with the release before anything is replaced, and downloads are only accepted from GitHub. studio-bridge settings shows the current choices.
Pieces
server.mjsis the MCP server (no dependencies, Node 22). It also runs a bridge on127.0.0.1:3010that the Studio plugin talks to, over a WebSocket (/ws, with acknowledgements and result replay after a reconnect) with HTTP long-polling as an automatic fallback. Every connection needs the secret intoken.txt, and browser origins are refused.plugin.stub.luais the small loader thatnode install.mjsfills in with the token and writes to%LOCALAPPDATA%\Roblox\Plugins\Studio Bridge.rbxmx. On start it asks the running bridge forplugin.template.lua(the real plugin), checks the source's HMAC-SHA256 signature (keyed by your token) and refuses to run anything that fails the check. While Studio is in edit mode it re-checks every 10 seconds and reloads the plugin when the file changes and no command is running, so plugin changes need no Studio restart. Restart Studio once after the first install. In Studio: Plugins > Manage Plugins, allow HTTP requests (and Script Injection) for Studio Bridge.install --standalonewrites the full plugin instead of the loader, for people who do not want Studio to load code from the bridge. It does not update itself.tools.jsonlists every tool (name, description, input schema) plus a smallmetasection. The server watches it and tells the client the tool list changed, so edits show up without restarting the server; clients that ignore the notification pick them up on the next/mcpreconnect.handlers/*.luauare the Luau bodies of the tools. They are read on every call, so editing one needs no restart.
Adding a tool
- Write
handlers/<name>.luau. The arguments arrive as the tableparams, and whatever the file returns is the result. Shared helpers such asresolve,pathOfandrequireScriptcome fromhandlers/_prelude.luau. - Add an entry to
tools.jsonwith the samename, a short description and an input schema. A tool that has a handler file runs in the edit window by default and can be used insidebatch. - Optional, in
meta:"role": "server"or"client"to target a play-session window, and"batchable": falseto keep it out ofbatch.
Tools that need server-side work (uploads, screenshots, the audit) are implemented in server.mjs and only have their schema in tools.json.
cli.mjsis the command line (serve,install,uninstall,doctor,version) and the entry point of the exe.paths.mjsdecides where files live: the data folder, the optionaloverridesfolder, the files embedded in the exe, or the source checkout.ws.mjsis a small dependency-free WebSocket server layer.assets.mjsis the Open Cloud upload client.screenshot.ps1captures or focuses the Studio window.
The Studio Bridge window
The plugin adds a Studio Bridge button to the Plugins toolbar that opens a themed panel (it follows Studio's light or dark theme):
- Status: whether the bridge is connected and over which transport, how many commands have run and failed, the last command and how long ago it ran, and how long the plugin has been up.
- Tools: a summary of how many tools are offered and their approximate token cost, one-click presets (Everything, Essentials, World builder, UI designer, Animator, Publisher) and a switch for each tool group. Changes are saved to the bridge straight away; your AI client may need
/mcpto refresh its tool list. If the profile is fixed by theSTUDIO_BRIDGE_TOOLSenvironment variable, the switches are read-only. - Log: a short log of connection events and commands.
macOS
Studio Bridge runs natively on macOS with the official Roblox Studio. It has not been tested on a real Mac yet, so please report anything that does not work, with the output of studio-bridge doctor.
- Install Node 22 or newer, then
npm install -g @zrob407/studio-bridgeandstudio-bridge install. - Reports disagree on where Studio for Mac reads plugins, so
installwrites the plugin to both~/Documents/Roblox/Pluginsand~/Library/Application Support/Roblox/Plugins; Studio reads only one of them, so it never loads twice. To see which folder yours uses, click Plugins Folder in Studio's Plugins tab. If it is somewhere else, runinstallwithSTUDIO_BRIDGE_PLUGINS_DIRset to that folder. Studio only loads plugins at startup, so quit and reopen it afterwards. - Data (token, uploads, exports, settings) lives in
~/Library/Application Support/StudioBridge. - Open Studio, allow HTTP requests and Script Injection for "Studio Bridge" if it asks, and run
studio-bridge doctor.
Differences from Windows:
- The
screenshottool (a screen capture of the Studio window) uses the built-inscreencapture,osascriptandsips, and needs Screen & System Audio Recording permission for the terminal or app that runs Claude Code (System Settings > Privacy & Security).viewport_screenshotcaptures the 3D view from inside Studio and needs no permission. input_keyboard,input_mouseandgui_clickbring Studio to the front withopen -a "Roblox Studio"before sending input.- The packaged exe is Windows only. Use the npm package.
Linux
Roblox has no native Linux Studio, so this setup is for Studio running under Wine through Vinegar or Grapejuice. The bridge itself and Claude Code run natively on Linux; Studio reaches the bridge on 127.0.0.1 because Wine shares the host network.
- Install Node 22 or newer, then
npm install -g @zrob407/studio-bridgeandstudio-bridge install. installfinds where Studio reads plugins. With Vinegar (native or Flatpak) Studio's Local AppData is~/.local/share/vinegar/appdata(Flatpak:~/.var/app/org.vinegarhq.Vinegar/data/vinegar/appdata), so the plugin goes intoappdata/Roblox/Plugins. Reports disagree on whether some Vinegar setups read the Wine prefix instead, so the plugin is also written todrive_c/users/<user>/AppData/Local/Roblox/Pluginsinside the prefix when one exists; Studio reads only one of them, so it never loads twice. Grapejuice,$WINEPREFIXand~/.wineuse the prefix folder. If yours is somewhere else, run it withSTUDIO_BRIDGE_PLUGINS_DIRset to thatPluginsfolder. Studio only loads plugins at startup, so restart it afterwards.- Data (token, uploads, exports, settings) lives in
$XDG_DATA_HOME/studio-bridge, usually~/.local/share/studio-bridge. - Start Studio from your launcher, allow HTTP requests and Script Injection for "Studio Bridge" if it asks, and run
studio-bridge doctor.
Differences from Windows:
- The
screenshottool (a screen capture of the Studio window) works on Windows and on Hyprland, where it needsgrim.viewport_screenshotcaptures the 3D view from inside Studio and works everywhere. input_keyboard,input_mouseandgui_clickneed Studio to be the focused window. On Hyprland (detected fromHYPRLAND_INSTANCE_SIGNATURE) Studio Bridge finds the window withhyprctl -j clientsand focuses it withhyprctl dispatch focuswindow. On other X11 desktops it usesxdotool. Elsewhere, click into Studio yourself before using those tools.- The packaged exe is Windows only. Use the npm package.
- This path has not been tested on a real Linux machine yet. Reports are welcome.
Windows
studio_list shows every connected window with a role:
edit: the normal Studio window (default target)server: the running game server during a play sessionclient: the player client. It cannot use HTTP itself, so commands reach it through a RemoteFunction relay in the server window. Passstudio: "client".
When several windows are connected, pass studio as an id prefix, a placeId, part of the place name, or a role. Tokens are combined (for example "Lure client").
Studio Bridge MCP questions
How do I add Studio Bridge MCP to Claude Code?
Run claude mcp add studio-bridge -- npx -y @zrob407/studio-bridge in your terminal. Add --scope user to make it available in every project.
How do I add Studio Bridge MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can I use this for commercial games?
Yes, the free version is free to use even for commercial games under the Studio Bridge License.
Does it work with Claude Code?
Yes, it is specifically designed to work with MCP-compatible assistants and has been tested with Claude Code.
Is there a paid version?
Yes, Studio Bridge Pro is a paid add-on pack that includes features like snapshots, diffs, QA playtests, and a place audit report.