3xui-mcp
Related Servers
Alternatives to 3xui-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables 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.161MIT
- AlicenseCqualityDmaintenanceEnables 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.1535 npmMIT
- AlicenseCqualityBmaintenanceEnables LLM agents to manage a self-hosted Termix instance through MCP, covering SSH, RDP/VNC, Docker, and fleet management capabilities.1841MIT
- AlicenseAqualityDmaintenanceEnables AI agents to safely read, audit, and manage Clash Verge Rev / Mihomo configuration with read-only and controlled runtime operations.668 npmMIT
- AlicenseCqualityBmaintenanceEnables 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.20413 npmMIT
TDQS
Scored across 12 tools
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.
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.
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.
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.