infoAbout
infoAbout s&box newspaperLatest News published_with_changesChanges mapRoadmap monitoringMetrics
gamesGames
sports_esportsBrowse Games exploreDiscover Games
categoryWorkshop
sports_esportsGames landscapeMaps view_in_arModels textureMaterials apparelClothing constructionMore..
forumForum menu_bookLearn
docsDocumentation apiApi Reference schoolTutorials manage_searchCode Search
Claude bridge
Released
Connects Claude AI to your s&box editor in real-time. Describe what you want and it creates. Game Dev is open for all!
by sboxskinsgg library
updated 8 Days Ago
1.9MB
thumb_down_alt8 favorite10 library_books0
homeDetailsnewspaperNewshistoryChangesreviewsReview1codeSource
Claude bridge
News
s&box Claude Bridge v2.0.0 "Native"
s&box Claude Bridge v2.0.0 "Native"
Major Toolset and native MCP update
calendar_today 7/10/2026 people Lou Sputthole chat_bubble 0 visibility 4

Major Native MCP & Toolset Update

By 
Lou Sputthole
 

s&box Claude Bridge v2.0.0 "Native" — the editor is now an AI-agent workspace


The s&box editor ships a native MCP server now — on by default, loopback-only, port 7269. So the Claude Bridge stops being a stack of file-IPC scripts and becomes what it was always meant to be: a structured automation platform living inside the editor. v2.0.0 moves the bridge's full tool surface onto that native transport — 232 tools across 28 described toolsets (53 of them read-only), streamed over HTTP instead of polled off disk.


What that buys you, concretely:

  • Claude sees what it builds. take_screenshot, capture_view, screenshot_from, and screenshot_orbit return the PNG inline in the tool result. No temp-file path to read back — the image is right there, so the build → screenshot → fix loop actually closes.

  • Agents discover tools live. search_tools finds the right one; list_toolsets / describe_toolset browse the 28 groups; call_tool / call_tools run them (batch several in one round trip). No 200-tool flat list to scroll.

  • Checkpoint the scene, then take risks. checkpoint_scene snapshots every root object to temp storage; restore_checkpoint rolls it all back. Batch-retint 40 props with a dry-run first, hate the result, roll back — this is the agent-side undo (live-verified resurrecting a 317-root scene).

  • Real prefabs, real batch ops. create_prefab writes full serialization and instantiate_prefab truly rebuilds the tree with GUID remap. batch_set_property / batch_delete / batch_add_component all validate with dryRun: true before they touch anything.

  • Drive a car, run a playtest. create_vehicle_controller turns any rigidbody prop into a raycast car with a built-in driver seat; tune_vehicle applies arcade / drift / offroad / race presets. The playtest harness runs a scripted loop in play mode and asserts the result in-frame.

  • No Node.js on the main path. The editor hosts the server. Node is only needed for the optional lifeline — a slim diagnostics server that keeps answering logs and compile errors when the editor crashes and takes the native server down with it.


Tool names are unchanged from v1.x; upgrading is one command plus an addon update. Six tools whose names collided with native built-ins (spawn_model, list_scenes, save_scene, undo, redo, remove_component) now defer to Facepunch's identical implementations — your workflows keep the same names.


Connect: claude mcp add --transport http sbox http://127.0.0.1:7269/mcp Or install the Claude Code plugin (wires both servers plus the cookbook brain, specialist agent, and screenshot workflow): /plugin marketplace add LouSputthole/Sbox-Claude → /plugin install sbox-claude


Source-available (no redistribution). Built by sboxskins.gg. Full docs: sboxskins.gg/claudebridge 

people
Log in to reply
You can't reply if you're not logged in. That would be crazy.