Skip to main content

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.

Roblox Studio MCP connects your AI coding agent to a live Studio session through a lightweight HTTP bridge. This guide walks you from a clean machine to a working connection in five steps — no manual file editing required if you use the --auto-install-plugin flag.

​
Prerequisites

Before you start, make sure you have:
  • Roblox Studio installed and able to open a place
  • Node.js 18+ and npm available in your terminal (node -v to check)
  • One of the supported AI tools: Claude Code, Codex CLI, Gemini CLI, Claude Desktop, or Cursor
1
Enable HTTP Requests in Game Settings
2
The Studio plugin communicates with the MCP server over localhost:58741. Studio blocks outbound HTTP by default, so you must opt-in once per place.
3
  • Open Roblox Studio with your project
  • Go to Game Settings → Security
  • Toggle Allow HTTP Requests to On
  • Click Save
    • 4
    This setting is saved per-place. You must enable it in every place file you want the agent to connect to. It does not grant network access to the published game on Roblox servers — it only allows localhost traffic in Studio.
    5
    Add the MCP server to your agent
    6
    The --auto-install-plugin flag tells the server to copy the matching MCPPlugin.rbxmx into Studio’s Plugins folder the first time it starts. Run the command that matches your tool:
    7
    Claude Code
    claude mcp add robloxstudio -- npx -y @chrrxs/robloxstudio-mcp@latest --auto-install-plugin
    Codex CLI
    codex mcp add robloxstudio -- npx -y @chrrxs/robloxstudio-mcp@latest --auto-install-plugin
    Gemini CLI
    gemini mcp add robloxstudio npx --trust -- -y @chrrxs/robloxstudio-mcp@latest --auto-install-plugin
    Claude Desktop / Cursor (JSON config)
    {
  "mcpServers": {
    "robloxstudio-mcp": {
      "command": "npx",
      "args": ["-y", "@chrrxs/robloxstudio-mcp@latest", "--auto-install-plugin"]
    }
  }
}
    Windows — Claude Desktop / Cursor (cmd wrapper)
    {
  "mcpServers": {
    "robloxstudio-mcp": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@chrrxs/robloxstudio-mcp@latest", "--auto-install-plugin"]
    }
  }
}
    8
    Windows users: If npx does not resolve when launched from a JSON-configured client (Claude Desktop, Cursor), use the cmd /c wrapper variant shown above.
    9
    @latest pins the server to the newest npm release automatically. If you need a specific version, replace @latest with the version tag (e.g. @2.20.0).
    10
    Fully close and reopen Studio
    11
    Studio loads plugins only on startup. After the MCP server has run for the first time with --auto-install-plugin, you must completely close and reopen Roblox Studio — not just close the place — so the new MCPPlugin.rbxmx is picked up.
    12
    Make sure Roblox Studio is not running in the system tray or background before reopening. On macOS, use Cmd+Q (not just closing the window) to ensure a full exit.
    13
    Verify the connection
    14
    After Studio restarts, look for the MCP Server button in the Plugins toolbar. Click it to open the dock widget. The status indicator should show Connected (green).
    15
    If the widget shows Disconnected (red), that is normal while the MCP server is not running. The plugin will auto-connect as soon as the server starts.
    16
    If you see a yellow warning banner, the plugin and server versions differ — see the version mismatch section for the one-command fix.
    17
    Ask your agent something
    18
    With the plugin showing Connected, open your AI tool and try one of these prompts to confirm everything is working end-to-end:
    19
    What's the structure of this game?
    20
    Find scripts using deprecated APIs and rewrite them.
    21
    Start a multiplayer test with 2 clients, read the server log, and tell me why the round never starts.
    22
    Evaluate `MatchService.activeMatches` on the server while a match is running.
    23
    Set a log breakpoint on the damage function, reproduce the hit, then read the breakpoint logs.
    24
    Capture a server Script Profiler sample while the wave spawns and rank the hottest functions.
    25
    Spawn 50 NPCs in a 10x5 grid for stress testing.
    26
    The agent will call get_connected_instances first to discover your open Studio places, then route subsequent tool calls to the correct instance automatically.

    ​
    Next steps

    • Multiple places open? Read MCP Clients to learn how instance_id routing works when several Studio windows are connected.
    • Want read-only access? The Inspector Edition ships 36 read-only tools — safe for code review without risk of accidental edits.
    • Need Open Cloud features? Pass --open-cloud-key, --creator-id, and --creator-group-id flags to unlock cloud-side tools. See MCP Clients for details.

    Build docs developers (and LLMs) love

    Get started for freeTalk to us