Skip to main content
Glama

Related Servers

Alternatives to Roblox-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding tools to control Roblox Studio for workspace exploration, instance manipulation, and script management. It provides tools for playtesting, scene rendering, and integration with the Roblox Creator Store.
      6
      8
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to directly manage Roblox Studio projects by creating, reading, updating, and deleting scripts, listing instances, executing Luau code, and inspecting properties. It works through natural language, making Studio operations accessible to AI.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables a bot to inspect, query, create, edit, and script Roblox Studio instances in token-cheap batches, plus run Luau, playtests, screenshots, and inputs through Roblox's official Studio MCP connection. It runs locally over stdio or an authenticated local HTTP endpoint, returning small structured answers instead of dumping whole games into context.
      8
      MIT

    TDQS

    B3/5.0

    Scored across 50 tools

    Disambiguation3/5

    Many tools target distinct operations, but overlaps exist: execute_luau can replicate nearly all mutation tools; playtest overlaps with play_solo/run_game/stop_playtest/get_play_state; create_instance vs bulk_create vs create_gui blur creation boundaries. Descriptions help, but an agent could easily misselect.

    Naming Consistency4/5

    Nearly all tools use snake_case and follow a verb_noun pattern (create_instance, set_property, get_play_state). Minor deviations exist: noun-first names (bridge_status, toolbox_search), bare verbs (undo, redo, playtest), and mixed prefixes (studio_, toolbox_).

    Tool Count2/5

    50 tools is excessive for the domain; many granular tools could be consolidated (e.g., create_instance/bulk_create/create_gui, multiple playtest controls). While the domain is broad, this count burdens selection and suggests over-provisioning.

    Completeness4/5

    Covers the major lifecycle: Studio launch/open/close, scene CRUD, scripting, GUI, asset insertion, lighting, camera, playtest, performance, player control, and undo/redo. Minor gaps like direct input simulation or place publishing exist, but execute_luau provides an escape hatch for most missing operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues