Skip to main content
Glama

Related Servers

Alternatives to 3xui-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables managing 3x-ui panels through their current API, including creating and updating clients across inbounds, monitoring online clients, and accessing panel features like nodes, routing, and backups via runtime-discovered API tools.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to control a locally running Bettbox (mihomo-based Clash client) without any client patches, switching proxy nodes, setting routing mode or TUN, testing latency, listing live connections, and adding, removing, or updating subscriptions. All capabilities ride on the client's existing surfaces: the mihomo REST API, its control socket, and its config/profile files.
      16
      1
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI agents to manage server infrastructure through the 1Panel API, including Docker containers, databases, and system monitoring. It provides tools for website management, file operations, and application deployment via natural language commands.
      15
      35 npm
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables MCP clients like Claude Code, Claude Desktop, or Cursor to read and manage Remnawave 3.x VPN panel resources — users, nodes, hosts, config profiles, squads, subscription templates, billing, and HWID devices — through the panel's REST API, with contract-driven tool schemas, numeric user IDs, multi-panel config lookup, and an optional readonly mode.
      204
      13 npm
      MIT

    TDQS

    A4.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Tools are cleanly divided between inbound management and client management, with each tool targeting a distinct resource-action pair. Even within clients, get_client and get_client_traffic are clearly differentiated by scope, eliminating any ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (list/get/create/update/delete), applied uniformly across both inbounds and clients. This makes the API highly predictable and easy to navigate.

    Tool Count5/5

    With 12 tools, the server is well-scoped for managing two primary resources (inbounds and clients). Each tool has a clear purpose and none feel redundant, falling comfortably within the ideal range.

    Completeness5/5

    The tool surface covers the full lifecycle for both inbounds and clients, including creation, retrieval, update, deletion, and listing. Additional capabilities like traffic stats and online status round out the domain without obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues