Skip to main content
Glama
Sign In
mihomo_party

mihomo_party

by bfrontend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mihomo_party

No user-submitted related servers found.

    Related Servers

    • Clash-Verge-MCP

      Koierrr
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • Bettbox MCP

      InkiChang
      A
      license
      Not graded
      quality
      C
      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.
      MIT

    • mihomo-mcp

      wlor0623
      A
      license
      A
      quality
      C
      maintenance
      Enables AI/MCP clients to manage a local mihomo/Clash Meta core by switching proxies, testing latency, viewing or closing connections, changing modes, and toggling TUN and Windows system proxy settings through a named pipe or HTTP control channel.
      10
      MIT

    • mihomo-mcp

      Aris-qin
      A
      license
      A
      quality
      C
      maintenance
      Bridges the mihomo (Clash Meta) RESTful API to the Model Context Protocol, enabling AI clients to switch proxies, test latency, refresh subscriptions, set operating modes, and monitor connections.
      10
      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

    B3.4/5.0

    Scored across 7 tools

    Disambiguation3/5

    Most tools are distinct, but list_profiles actually lists proxy groups and their nodes, while switch_profile switches subscription profiles, so the word 'profile' has two different meanings. select_proxy is also closely related to the node information returned by list_profiles, which may cause some misselection.

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun pattern: list_profiles, get_active_config, list_rules, add_rules, reload_config, switch_profile, select_proxy. There are no mixed conventions or vague standalone verbs.

    Tool Count5/5

    Seven tools is well-scoped for a Mihomo/Clash configuration management server. Each tool covers a distinct operational area: inspection, rule addition, reload, profile switching, and proxy selection.

    Completeness3/5

    Core workflows like listing rules, adding rules, reloading, switching profiles, and selecting proxies are covered, but rule management is incomplete: there is no delete_rules or update_rules operation. There is also no tool to list override files even though add_rules accepts an optional override_file parameter.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources