A
licenseNot graded
qualityD
maintenanceConnects AI assistants to Roblox Studio, enabling them to interact with instance hierarchy, edit Luau scripts, manage properties, and sync files over a local connection.
11 npm
2
MIT
mcp-tools
by gavinostler
Related Servers
Alternatives to mcp-tools
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConnects AI coding assistants to Roblox Studio, enabling direct manipulation of the DataModel through natural language commands with undo support.1454 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to explore, edit, and automate Roblox Studio sessions locally, including browsing instance hierarchies, reading and modifying scripts, manipulating properties, creating instances, building terrain, and running playtests.1,024 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to explore Roblox Studio game structure, read and edit scripts, and perform bulk changes locally and safely.MIT
- AlicenseAqualityCmaintenanceEnables an AI agent to drive Roblox Studio, including running Luau code, syncing Rojo projects, starting solo or multiplayer play tests, and retrieving logs, screenshots, and GUI information.11MIT
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants like Claude and Gemini to Roblox Studio, enabling game structure exploration, script editing, UI generation, style extraction, and bulk changes locally and safely.5 npmMIT
TDQS
A4/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct operation: server lifecycle (start/status/stop), plugin build, plugin install, and Studio import. The only closely related pair, build_plugin vs. install_plugin, is explicitly separated in the descriptions, and the start/status/stop trio has clear non-overlapping semantics.
Naming Consistency5/5
All names use snake_case with a consistent domain prefix and readable operation naming: rojo_start, rojo_status, rojo_stop, rojo_build_plugin, rojo_install_plugin, studio_import. The pattern is predictable, and rojo_status is a conventional command-style exception rather than a real inconsistency.
Tool Count5/5
Six tools is a well-scoped set for the apparent Rojo/Studio workflow, with each tool earning its place. Nothing feels padded, and the surface is not so thin that basic lifecycle operations are missing.
Completeness4/5
The core lifecycle is covered: start/status/stop the Rojo server, build/install the plugin, and import a model into Studio. Minor gaps exist around plugin status/uninstall, server logs, and common Rojo operations like a one-shot place build, but agents can work around these.
Maintenance
ActivityMaintained
ResponsivenessNo issues