A browser extension and local bridge that connects AI chat sites (DeepSeek, Gemini, Kimi, etc.) to MCP servers running on the user's machine, enabling AI agents to read/write files, run commands, and control Roblox Studio through a local workspace folder.
OpenRender exposes 16 tools with minimal schema rigor. Most tools have basic descriptions (10-50 chars), but critically lack parameter descriptions and output schemas. Input schemas are present but sparse: most parameters have only type and description, no enums, ranges, or constraints. No error handling guidance. Tools like execute_luau and run_command are high-risk (IRREVERSIBLE) but lack confirmation patterns or dry-run support. The server is a STDIO-only extension for Roblox Studio, not a standalone MCP server, tool definitions appear inferred from code comments rather than explicit MCP registration.
Create a new folder
Delete a file or folder permanently
Edit a file by replacing specific text
Execute Luau code in Roblox Studio
Search file contents for a pattern
List all available commands with full parameter details
List contents of a directory in the workspace
List all connected MCP servers and their available commands
No output schemas documented. Tools return unstructured responses; LLMs cannot plan downstream calls or extract required fields (e.g., file paths, command exit codes, Luau execution results).
High-risk tools (execute_luau, run_command, delete_path) lack confirmation or dry-run patterns. Agents can irreversibly execute arbitrary code or delete files without safeguards.
Parameter descriptions are minimal or absent. 'pattern' in search_files and grep_files lacks format guidance (glob vs regex?). 'datamodel_type' in execute_luau lacks enum constraint or valid values.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |
Move or rename a file or folder
Read the contents of a file
Execute a terminal command in the workspace
Capture a screenshot from Roblox Studio
Search for files matching a pattern
Display directory tree structure
Get information about the workspace folder
Write or create a file
No error handling guidance. Tools do not indicate what errors are retryable, user-fixable, or fatal. LLMs receive raw failures with no recovery path.
Tool definitions appear inferred from code comments, not explicitly registered via MCP. No visible tool registration with schemas in the source. Caps per-tool scores at 50.