Skip to main content
Glama
Xenoz-GitHub

XenozMCP

by Xenoz-GitHub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to XenozMCP

No user-submitted related servers found.

    Related Servers

    • dex-mcp

      972jesko
      A
      license
      A
      quality
      B
      maintenance
      Debug and inspection tooling for Roblox projects, exposed as an MCP server so an AI agent can explore the instance tree, read/write properties, call remotes, and run Luau in a Roblox client driven by an executor.
      14
      20 npm
      MIT

    • dex-mcp

      sanztheo
      A
      license
      A
      quality
      D
      maintenance
      Debug and inspection tooling for Roblox projects, exposed as an MCP server so an AI agent can explore the instance tree, read/write properties, call remotes, and run Luau in a Roblox client driven by an executor.
      10
      14
      20 npm
      1
      MIT

    • Melo

      yannyhl
      A
      license
      Not graded
      quality
      D
      maintenance
      An agentic MCP server for Roblox Studio that provides over 45 tools for script diffing, playtest automation, and bulk instance manipulation. It enables AI agents to manage full development cycles within Roblox, including transaction-safe batch operations and real-time script reviews.
      2 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 21 tools

    Disambiguation5/5

    Tools are clearly separated into three distinct domains: cloud services, Roblox Studio interaction, and vault management. No overlapping purposes; each tool has a unique and well-defined role.

    Naming Consistency4/5

    The naming convention is predominantly snake_case with descriptive prefixes (cloud_, vault_). Some names like 'start_stop_play' combine two actions but are still understandable. Overall consistent.

    Tool Count4/5

    21 tools is above the typical range but justified by the server's broad scope covering cloud operations, Studio control, and a secure vault. Each tool serves a distinct purpose without redundancy.

    Completeness4/5

    The tool set covers core workflows for cloud data stores, Studio management, and vault operations. A minor gap is the absence of a delete operation for data store entries, but overall it's comprehensive.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources