Skip to main content
Glama
Sign In
Superbase

Superbase

by fiangg20
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Superbase

Related Servers

  • Roblox Client MCP

    LiteEagle262
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI assistants to inspect and control a live Roblox client through an executor, including reading console output, exploring the instance tree, decompiling scripts, monitoring remote traffic, and running Luau code.
    MIT

  • Roblox MCP Server

    33jrdd
    F
    license
    B
    quality
    Not graded
    maintenance
    Enables AI assistants to interact with running Roblox game instances by inspecting the game hierarchy, reading client-side scripts, and executing Lua code directly within the Roblox client through a WebSocket bridge.
    4
    4
    37 npm
    -

  • Roblox Executor MCP Server

    okenjioxx
    A
    license
    B
    quality
    C
    maintenance
    Connects AI assistants to live Roblox executor clients, letting the model run Luau in-game, walk the instance tree, decompile scripts, capture remote calls, and orchestrate work across multiple clients through 289 tools, a browser dashboard, and an in-game scripting surface. It also supports persistent playbooks, session traces, and verified agent workflows for repeatable automation.
    291
    MIT

  • Roblox Executor MCP

    thegrateminecra-backups
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    Lets AI agents interact with a live Roblox game via an executor, supporting multi-agent sessions and tools for executing Lua, decompiling scripts, exploring game instances, and capturing screenshots.
    -
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

A3.9/5.0

Scored across 30 tools

Disambiguation4/5

Each tool targets a distinct area (execution, instance inspection, script search, spying, GUI, performance, snapshots), and the descriptions actively cross-reference each other (semantic_search defers to search_scripts, run_file is described as execute_lua from a file). The only real overlaps are among the code-execution tools (execute_lua, run_file, recipes.run) and the log trio (get_logs, get_errors, wait_for_log), but the descriptions make the boundaries clear enough to choose correctly.

Naming Consistency3/5

Most tools follow a verb_noun snake_case pattern (get_logs, list_scripts, find_instances, wait_for_instance, set_property), but a large minority are bare nouns or noun_verb hybrids (recipes, snapshot, stats, notify, screenshot, roblox_status, http_spy, remote_spy). Conventions are mixed, yet every name remains readable and domain-indicative.

Tool Count3/5

30 tools is heavy and several are multi-action bundles (recipes, snapshot, remote_spy, http_spy, gui_interact, player_info, call_instance), so the set is at the upper limit even for this broad domain. Nothing feels truly redundant, but a few thin tools (notify, clear_logs, wait_for_log) could be folded into siblings to slim the surface.

Completeness4/5

Coverage is genuinely broad: connection state, execution, script/instance discovery, code introspection, remote/HTTP interception, GUI interaction, screenshots, performance and snapshot diffing all exist as lifecycle-complete families. Minor gaps remain, such as browsing or reading local files (only run_file executes them) and no way to abort a runaway Lua execution.

Maintenance

ActivityMaintained
ResponsivenessOutdated data

Resources