Roblox Executor MCP Server
<p align="center">
<img src="docs/banner.svg" alt="Roblox Executor MCP" width="900"/>
</p>
# Roblox Executor MCP Server
An MCP server that allows Agents to interact with a running Roblox game client — execute code, inspect scripts, spy on remotes, and more.
> **Credit:** This project is based on [roblox-executor-mcp](https://github.com/notpoiu/roblox-executor-mcp) by [notpoiu](https://github.com/notpoiu). Full credit to the original authors for the foundational work.
## Features
- Code Execution
- Script Inspection
- Bytecode Disassembly
- Instance Search
- Instance Explorer
- GC Search
- Property Read & Write
- Remote Spy
- Reverse Mode
- Anti-Cheat Scan
- Console
- Semantic Search
- Persistent Memory
- GUI Interaction
- Screenshot
- Web Dashboard
- Multi-Client
## Dashboard
Roblox Executor MCP includes a local web dashboard at:
```
http://localhost:16384/
```
Use it to see connected Roblox clients, browse the instance explorer, inspect and edit scripts, spy on remotes, run a Luau console, view live server logs, manage relay peers, and configure semantic search.
TDQS
Scored across 22 tools
Most tools have distinct purposes, e.g., remote spy management vs. execution vs. UI interaction. Potential confusion between execute, execute-file, and get-data-by-code is mitigated by clear descriptions explaining return value differences.
All tool names follow a consistent kebab-case verb-object pattern (e.g., block-remote, clear-remote-spy-logs, ensure-remote-spy). No mixing of conventions.
With 22 tools covering spy, execution, UI, searching, scripts, and client management, the count is well-scoped for a Roblox executor server. Not excessive nor too sparse.
Core workflows like remote spy, code execution, instance searching, and client management are well-covered. Minor omissions (e.g., no tool to modify instance properties) but not critical for the server's purpose.