Roblox Studio MCP Server
# Archiving project June 6th 2026
Hey a few months ago my laptops motherboard was shorted which contained the hardware keys needed to get into my NPM account, due to Node customer support taking forever and also other priorities taking place for me, I will be **archiving** this project.
I recommend you swap to https://github.com/Chrrxs/robloxstudio-mcp which is a fork of this one that's being actively maintained by Chrrxs.
# Roblox Studio MCP Server
**Connect AI assistants like Claude and Gemini to Roblox Studio**
[](https://www.npmjs.com/package/robloxstudio-mcp)
---
## What is This?
An MCP server that lets AI explore your game structure, read/edit scripts, and perform bulk changes all locally and safely.
## Setup
1. Install the [Studio plugin](https://github.com/boshyxd/robloxstudio-mcp/releases) to your Plugins folder
2. Enable **Allow HTTP Requests** in Experience Settings > Security
3. Connect your AI:
**Claude Code:**
```bash
claude mcp add robloxstudio -- npx -y robloxstudio-mcp@latest
```
**Codex CLI:**
```bash
codex mcp add robloxstudio -- npx -y robloxstudio-mcp@latest
```
**Gemini CLI:**
```bash
gemini mcp add robloxstudio npx --trust -- -y robloxstudio-mcp@latest
```
Plugin shows "Connected" when ready.
<details>
<summary>Other MCP clients (Claude Desktop, Cursor, etc.)</summary>
```json
{
"mcpServers": {
"robloxstudio-mcp": {
"command": "npx",
"args": ["-y", "robloxstudio-mcp@latest"]
}
}
}
```
**Windows users:** If you encounter issues, use `cmd`:
```json
{
"mcpServers": {
"robloxstudio-mcp": {
"command": "cmd",
"args": ["/c", "npx", "-y", "robloxstudio-mcp@latest"]
}
}
}
```
</details>
## What Can You Do?
Ask things like: *"What's the structure of this game?"*, *"Find scripts with deprecated APIs"*, *"Create 50 test NPCs in a grid"*, *"Optimize this movement code"*
<details>
<summary><strong>Inspector Edition (Read-Only)</strong></summary>
### robloxstudio-mcp-inspector
[](https://www.npmjs.com/package/robloxstudio-mcp-inspector)
A lighter, **read-only** version that only exposes inspection tools. No writes, no script edits, no object creation/deletion. Ideal for safely browsing game structure, reviewing scripts, and debugging without risk of accidental changes.
**31 read-only tools:** `get_file_tree`, `search_files`, `get_place_info`, `get_services`, `search_objects`, `get_instance_properties`, `get_instance_children`, `search_by_property`, `get_class_info`, `get_project_structure`, `mass_get_property`, `get_script_source`, `grep_scripts`, `get_attributes`, `get_tags`, `get_tagged`, `get_selection`, `get_playtest_output`, `get_connected_instances`, `get_descendants`, `compare_instances`, `get_output_log`, `export_build`, `list_library`, `search_materials`, `get_build`, `search_assets`, `get_asset_details`, `get_asset_thumbnail`, `preview_asset`, `capture_screenshot`
**Setup** - same plugin, just swap the package name:
**Claude:**
```bash
claude mcp add robloxstudio-inspector -- npx -y robloxstudio-mcp-inspector@latest
```
**Codex:**
```bash
codex mcp add robloxstudio-inspector -- npx -y robloxstudio-mcp-inspector@latest
```
**Gemini:**
```bash
gemini mcp add robloxstudio-inspector npx --trust -- -y robloxstudio-mcp-inspector@latest
```
<details>
<summary>Other MCP clients (Claude Desktop, Cursor, etc.)</summary>
```json
{
"mcpServers": {
"robloxstudio-mcp-inspector": {
"command": "npx",
"args": ["-y", "robloxstudio-mcp-inspector@latest"]
}
}
}
```
**Windows users:** If you encounter issues, use `cmd`:
```json
{
"mcpServers": {
"robloxstudio-mcp-inspector": {
"command": "cmd",
"args": ["/c", "npx", "-y", "robloxstudio-mcp-inspector@latest"]
}
}
}
```
</details>
</details>
---
<!-- VERSION_LINE -->**v2.7.0-next.6** - 43 tools, inspector edition, monorepo architecture
[Report Issues](https://github.com/boshyxd/robloxstudio-mcp/issues) | [DevForum](https://devforum.roblox.com/t/v180-roblox-studio-mcp-speed-up-your-workflow-by-letting-ai-read-paths-and-properties/3707071) | MIT Licensed
TDQS
Scored across 24 tools
Most tools have distinct purposes, but there is some overlap between 'create_object' and 'create_object_with_properties', and between 'mass_create_objects' and 'mass_create_objects_with_properties', which could cause confusion. However, descriptions clarify the differences, and other tools like 'search_objects' vs 'search_by_property' are well-differentiated.
Tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., 'create_object', 'get_instance_properties', 'set_script_source'). There are no deviations in naming conventions, making the set predictable and easy to parse.
With 24 tools, the count is on the higher side for a single domain, which may feel heavy and could overwhelm agents. While the tools cover many aspects of Roblox Studio, some could potentially be consolidated (e.g., the multiple 'mass_' tools) to reduce complexity.
The tool set provides comprehensive coverage for Roblox Studio operations, including CRUD for objects (create, delete, get, set), property management, scripting, searching, and project hierarchy exploration. No obvious gaps are present; agents can perform full lifecycle management and complex workflows.