mihomo-mcp
Related Servers
Alternatives to mihomo-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets an assistant observe and control Windows application windows, plus interact with Xiaomi MiMo AI Desktop workflows, through 22 tools for Unicode typing, smooth dragging, cross-window drops, and bounded SSE streaming.MIT
- AlicenseNot gradedqualityBmaintenanceRemote-first, model-independent Windows execution MCP for ChatGPT, Claude, Gemini, and other MCP-compatible AI clients.MIT
- AlicenseNot gradedqualityCmaintenanceUnifies local MCP servers into a single secure Cloudflare Tunnel endpoint, making them accessible to MCP clients like Notion and Claude. Supports HTTP/SSE/stdio servers, built-in file system tools, bearer authentication, and one-click Windows setup.MIT
- FlicenseNot gradedqualityFmaintenanceA lightweight MCP HTTP server giving AI assistants real tools to interact with your Windows machine, including running commands, file access, system info, web search, and browser automation.1-

zerouter-mcpofficial
AlicenseAqualityAmaintenanceConnects MCP clients such as Claude Desktop, Cursor and Claude Code to an OpenAI- and Anthropic-compatible AI gateway, enabling chat with Claude, GPT, Gemini, Grok and Kimi models, listing available models, and looking up per-million-token pricing. It also sends one prompt to several models in parallel and returns each answer with token usage, latency and estimated cost.4MIT
TDQS
Scored across 10 tools
Most tools target a distinct resource and action (e.g., get_connections vs get_rules vs get_configs), but delay_test and list_proxies both surface latency information, and the three toggle/set tools (set_mode, set_tun, toggle_system_proxy) touch related proxy settings. Descriptions help differentiate them, so confusion is minor.
Predominantly consistent verb_noun snake_case pattern (get_connections, set_mode, list_proxies, switch_proxy). The only deviation is delay_test, which follows noun_verb order instead of test_delay or get_delay.
10 tools is a well-scoped set for a mihomo core controller, covering status, configuration, proxy management, and connection details without redundancy. Each tool earns its place.
Core operational workflows are covered: viewing configs, mode/TUN/system proxy toggles, proxy listing/switching, latency testing, rules, connections, and version. Minor gaps exist, such as setters for other config fields revealed by get_configs (e.g., mixed port, LAN sharing) and no subscription reload or rule editing.