mcp-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rojo_startA | Serve a Rojo project ( |
| rojo_statusA | Is a Rojo server for this project answering on the port (and did rojo_start start it)? |
| rojo_stopA | Stop the Rojo server rojo_start started on this port (never one it didn't start). |
| rojo_build_pluginA | Build the auto-connect Rojo plugin: the installed Rojo CLI's own version (from GitHub) plus a
patch that, in Edit mode with Auto Reconnect on, connects every few seconds to a server whose
project lists the open place in |
| rojo_install_pluginA | Install the plugin rojo_build_plugin built as Studio's Rojo plugin (the old one is backed up to %LOCALAPPDATA%\Roblox\PluginBackups). With Studio closed it also turns on Rojo's Auto Reconnect and sets Confirmation Behavior to "Unlisted PlaceId", so listed places connect without a click. Studio picks the plugin up when it next opens. The project needs "servePlaceIds": [] for auto-connect to happen. |
| studio_importA | Import a model file (FBX, OBJ, GLB or GLTF) through Roblox Studio's own 3D Importer, as a person would (File > Import, then Import), leaving the importer's settings as they are. Needs exactly one Studio window, in Edit mode (not playtesting), visible on screen; it takes the mouse and keyboard for about 15 s. Returning means the importer accepted the file: Studio's Import Queue finishes it a few seconds later, so check the model arrived before using it. Leave a few seconds between imports. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.