Chisle
The coding-agent plugin that bills 52% of a bare model across 20 live tasks. Terse persona + tool-output compressor + context diet.
Free Roblox Studio MCP server and plugin. Connect Claude Code, Cursor or any MCP client to Studio with 87 tools, git history, snapshots, a disk backup of your GUIs and a backdoor scanner.
Developer toolsGitHub @drgost1Availability not checked yetOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Repository information has not been collected yet.
No updates detected yet. GitHub releases will appear here.
Free Roblox Studio MCP server and plugin. Connect Claude Code, Cursor or any MCP client to Studio: 85 tools, snapshots, two-way script sync, git and a backdoor scanner.
Loading the full README.
Read the full README ↗A free Roblox Studio MCP server and plugin that works as an add-on to Roblox's built-in Studio MCP. Connect Claude Code, Cursor or any MCP client to Roblox Studio and let your AI build, audit and version your game: 87 tools for Luau scripts, instances and properties, plus two-way file sync, git history, snapshots, a backdoor scanner, Luau linting and AI 3D-asset generation.
Keep the built-in server for play tests and screenshots. Add Tufan for everything around them.
Website and overview · npm · Latest release
You need Node.js 18 or newer.
Open Claude Code, Cursor or another AI agent in your Roblox project folder and paste:
Set up Tufan-Blox-Bridge, a Roblox Studio MCP server and plugin, for this project.
1. Run `npx -y tufan-blox-bridge@latest setup` in this folder. It installs the server and the Studio plugin, and registers with Claude Code or Cursor.
2. If it says nothing was registered, add the config it prints to your MCP settings, keeping any servers already there.
3. Don't ask me for API keys. They're optional.
4. Tell me what it did and the next steps it printed.
npx -y tufan-blox-bridge@latest setup
Then restart Roblox Studio and your AI client, and open the Tufan Studio toolbar button. A green pill means it's connected.
1 — One-line installer (run from your Roblox project folder). It checks Node ≥ 18, installs the MCP server globally (npm i -g tufan-blox-bridge), drops the Studio plugin into your Plugins folder (tufan-blox-bridge install-plugin), and auto-registers with Claude Code when the claude CLI is on PATH:
# Windows (PowerShell)
iwr https://raw.githubusercontent.com/drgost1/Tufan-Blox-Bridge/main/install.ps1 | iex
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/drgost1/Tufan-Blox-Bridge/main/install.sh | bash
2 — Point your AI client at the server (skip if the installer registered it; use forward slashes in the path):
claude mcp add tufan --env TUFAN_PROJECT=C:/path/to/your/project -- tufan-blox-bridge
For Cursor / Claude Desktop / any MCP client:
{
"mcpServers": {
"tufan": {
"command": "tufan-blox-bridge",
"env": { "TUFAN_PROJECT": "C:/path/to/your/project" }
}
}
}
Optional env: TUFAN_OPENCLOUD_KEY (Open Cloud: datastore, cloud_luau, get_server_logs, get_server_history), TUFAN_MESHY_KEY (AI 3D generation).
3 — Restart Studio and your AI client. A Tufan Studio toolbar button appears — open its widget; the pill turns green when connected.
That's it. Your AI can now drive Studio, your scripts mirror to disk, and scan_backdoors is ready.
tufantimes out / won't connect? Runclaude mcp get tufanand confirm the command istufan-blox-bridge(global install) ornpx -y tufan-blox-bridge. If an argument got dropped,claude mcp remove tufan, then re-run the add. The installer auto-verifies this.
npx -y tufan-blox-bridge or bunx tufan-blox-bridge.npm i -g tufan-blox-bridge → command tufan-blox-bridge.tufan-blox-bridge install-plugin (copies the bundled .rbxm into your Plugins folder), or manually download TufanBloxBridge.rbxm from Releases (or pwsh scripts/build-plugin.ps1 -Install).Roblox's built-in Studio MCP is excellent at running and seeing your game. Tufan is the add-on for building it safely, keeping it versioned and keeping it clean. Install both: they cover different jobs, and Tufan tells your AI which one to use.
This is the beginning of the README. Read the rest at the original. Read the full README ↗