Clash Control MCP
Related Servers
Alternatives to Clash Control MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI clients to manage local Clash/mihomo proxy frontends through natural language, including adding and deduplicating routing rules, listing and switching profiles and proxy groups, and reloading configuration.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to inspect devices and automation rules, preview and apply changes, create backups, compare snapshots, and restore rules on a local MiJia gateway, with writes requiring confirmation.1MIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a local Clash Verge Rev / mihomo core on Windows over its named-pipe controller, discovering the live pipe automatically so it works in both sidecar and service mode. Supports inspecting status, switching proxy nodes, latency testing, changing modes, viewing connections and rules, and updating providers.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents such as Claude to query local security status, inspect threats and system resources, and initiate scans through read-only, privacy-redacted tools with audit logging.1-
- AlicenseAqualityCmaintenanceEnables querying and managing Apache APISIX gateway configurations (routes, services, upstreams, consumers, plugins) through natural language, with read-only mode and write operations requiring confirmation.1540 PyPIMIT
TDQS
Scored across 66 tools
Each tool has a highly specific purpose within a clear hierarchical namespace (e.g., clash.verge.*, clash.runtime.*). Descriptions are detailed and unique, making it easy to distinguish between similar tools like list vs inspect variants.
All tools follow a consistent pattern: `clash.<category>.<action>`. The hierarchy is uniform, verbs are descriptive (get, set, list, inspect, configure), and snake_case is used throughout without deviations.
At 66 tools, the server is excessively large. While the Clash Verge domain is complex, this many tools in a single server creates cognitive overload and violates typical MCP scoping. The count far exceeds the 15–25 range considered reasonable.
The tool set covers a broad and deep range of operations: profiles, configuration, runtime control, preferences, optimization diagnostics, and recovery. Minor gaps exist (e.g., no direct runtime config write), but core workflows are well-supported.