lainbridge

lets claude code build stuff directly in roblox studio. it reads your game, edits scripts, creates instances and UI, runs lua, takes screenshots — 30+ tools.

you need

• node.js (click the big green LTS button, install it)
• roblox studio
• claude code

install

1. install node.js if you don't have it (click the big green LTS button)
2. download the zip and extract it anywhere
3. open claude code in the extracted folder
4. that's it — claude handles the rest (installs the plugin, starts the bridge, configures the tools)
5. open studio, go to Home > Game Settings > Security, turn on "Allow HTTP Requests"
6. click Connect in the Lainbridge panel in studio

after the first run, the tools are available in any directory. just open claude code wherever your game project is.

every time after that

1. double-click "Lainbridge" on your desktop (starts the bridge — leave it open)
2. open studio, click Connect in the lainbridge panel
3. open claude code in your project folder — it just works

alternative: install via npm

if you prefer a global install:

npm install -g lainbridge
lainbridge setup

what can it do

just tell claude what you want. some examples:

• "add a sprint system to my game"
• "fix the gun not doing damage"
• "build a shop UI with 3 tabs"
• "make the NPC walk between waypoints"
• "show me a screenshot of the game"
• "find all scripts that use RemoteEvents"

claude reads your game state, understands how your scripts connect, makes the changes, and verifies they work.

why lainbridge over roblox's built-in mcp?

roblox has an official mcp server. it gives you run_code and a few playtest tools. that's about it — every operation goes through raw luau. the AI has to write lua code to read your game, write lua code to edit scripts, write lua code to create instances. it's slow, error-prone, and burns tokens.

lainbridge gives you 30+ purpose-built tools instead of one generic "run code" tool.

| | lainbridge | roblox mcp | |---|---|---| | dedicated tools | 30+ | ~11 | | read full game state in one call | get_context — instant from cache | no (write luau to traverse) | | edit scripts safely | 4 methods with hash protection | no (write luau yourself) | | understand your codebase | analyze_system maps how scripts connect | no | | find code across all scripts | search_scripts with regex | no | | create UI from json | create_ui — full tree in one call | no (write luau) | | batch create with rollback | batch_create — atomic, all-or-nothing | no | | screenshots | screenshot, capture_viewport | no | | undo/redo | yes | no | | terrain, lighting, camera | dedicated commands | no (write luau) | | type-safe properties | Color3, UDim2, CFrame wrappers | no (write luau) | | live state cache | instant reads, real-time sync | no cache |

roblox's mcp does have a couple things lainbridge doesn't: virtual mouse/keyboard input during playtests and built-in pathfinding. but for actually building games — reading code, editing scripts, creating systems — lainbridge is significantly faster and more reliable.

the core difference: roblox's mcp makes the AI figure out how to do everything in raw lua. lainbridge handles the hard parts so the AI can focus on your game.

all 30+ tools

reading — get_context, read_script, get_instance, get_status, get_errors, get_console

analysis — analyze_system, get_script_deps, search_scripts

creating — create_script, create_instance, create_ui, batch_create

editing — edit_surgical, edit_lines, edit_regex, edit_script, set_properties, delete_instance

execution — run_lua, run_in_playtest, execute_command

visual — screenshot, capture_viewport

and more via execute_command — clone, reparent, find instances, set attributes, set tags, terrain, lighting, camera, CSG, sounds, constraints, undo/redo

troubleshooting

"commands aren't working" — make sure the bridge window is open and studio shows "Connected" in the lainbridge panel.

"Allow HTTP Requests" — you need to enable this in studio every time you open a new place. Home > Game Settings > Security.

"tools not showing up in claude code" — open claude code in the lainbridge folder first so it can configure itself. or run manually: claude mcp add -s user lainbridge -- npx -y lainbridge@latest

"node is not recognized" — install node.js from https://nodejs.org and restart your terminal.

how it works

claude code <-> mcp server <-> bridge <-> studio plugin <-> roblox studio

the bridge keeps a copy of your game state in memory so reads are instant. edits go through the plugin which wraps everything in studio's undo system.

multiple studio instances

run bridges on different ports:

lainbridge start 9091
lainbridge start 9092

use the switch_port tool in claude code to swap between them.

license

MIT