Skip to main content
Glama
Sign In
Roblox MCP

Roblox MCP

by sdhzcxnb0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Roblox MCP

No user-submitted related servers found.

    Related Servers

    • Vibe Blocks MCP

      majidmanzarpour
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects Roblox Studio to AI coding editors via the Model Context Protocol, allowing AI agents to understand and interact with live Roblox Studio sessions through scene manipulation, scripting, and optional Roblox Open Cloud API integration.
      66
      MIT

    • Roblox Studio MCP Server

      forgestudioapp
      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.
      875 npm
      MIT

    • roblox-mcp-bridge

      kavinr24
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Roblox Studio to local AI agents via HTTP, allowing them to control Studio tools.
      MIT
    • Superbase

      Superbase

      fiangg20
      A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to a live Roblox executor session to read console logs and errors, search and inspect the instance tree, read scripts, change properties, and run Lua, while reporting connection status on every call.
      8
      30
      4
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Each tool targets a distinct resource or action, but there are mild overlaps: get_instance vs read_script (both read instance data, one script-source-specific) and create_instance vs insert_model (both add objects, one generic, one catalog asset). execute_luau intentionally overlaps with everything, though its description explicitly says to prefer dedicated tools.

    Naming Consistency4/5

    Almost all tools follow a clean snake_case verb_noun pattern (read_script, get_tree, create_instance, set_property, delete_instance, list_scripts, write_script). The only deviation is studio_status, which is a descriptive noun phrase without a verb, but it remains readable and predictable.

    Tool Count5/5

    13 tools is well within the sweet spot and every tool maps to a meaningful Studio operation: status, inspection, search, mutation, scripts, and asset insertion. Nothing feels redundant enough to remove, and nothing essential is obviously missing from the count.

    Completeness4/5

    The surface covers the core lifecycle: inspect (status, tree, instance, selection, search), mutate (create, set_property, delete, insert_model), and script management (read/list/write) plus an escape hatch via execute_luau. Gaps include no explicit playtest start/stop control, no undo/redo tool, and no dedicated reparent/rename operation, though most can be worked around via set_property (Parent/Name) or execute_luau.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources