Features
Capabilities
RoCodex provides your AI coding assistant with deep integration into Roblox Studio through purpose-built MCP tools.
Documentation Search
Before writing any code, your AI can search the official Roblox Creator Hub to verify API names, method signatures, events, and Luau behavior.
search_luau_docs("Humanoid MoveToFinished event")
This ensures your AI never guesses at API names or uses deprecated syntax. Results are pulled directly from create.roblox.com/docs.
Live Studio Execution
Your AI can execute Luau code directly inside your running Roblox Studio session. This is useful for:
- Inspecting the DataModel hierarchy
- Testing functions before committing them to scripts
- Debugging errors with full Studio context
- Reading instance properties and attributes
execute_luau_in_studio([[
local Workspace = game:GetService("Workspace")
for _, child in Workspace:GetChildren() do
print(child.ClassName, child.Name)
end
]])
Strict Luau Enforcement
RoCodex enforces modern Luau best practices through its system prompt:
- Uses
game:GetService("ServiceName")instead of global access - Prefers
task.wait(),task.spawn(),task.delay()over deprecated functions - Enforces Luau type annotations for clarity
- Respects server/client boundaries for RemoteEvents and RemoteFunctions
- Always inspects the DataModel before assuming folder or object names
Script Management
RoCodex can read, create, and modify scripts inside your game:
- Read any script's source code
- Create new scripts with proper parent paths
- Modify existing scripts with targeted edits
- Search across all scripts for patterns
Instance Inspection
Your AI can inspect any instance in your game:
- List children and descendants
- Read properties and attributes
- Check class types and inheritance
- Navigate the full instance hierarchy
Auto Playtest
RoCodex can start and stop playtests directly from your editor, allowing your AI to:
- Test gameplay changes in real-time
- Verify that scripts work correctly at runtime
- Capture console output during playtests
Privacy first. All tool execution happens locally on your machine. Your game code, scripts, and Studio data never leave your computer.
