Skip to main content
Glama
blackcocwhite

Meiju MCP

by blackcocwhite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Meiju MCP

No user-submitted related servers found.

    Related Servers

    • agent-browser-mcp

      335234131
      A
      license
      B
      quality
      F
      maintenance
      Enables AI agents to directly control your real Chrome browser with full context including login sessions, cookies, and open tabs. It provides tools for page scanning, JavaScript execution, CDP control, screenshots, and physical mouse/keyboard input for authentic browser automation.
      20
      245
      MIT

    • chrome-agent-browser

      oscs1024-pixel
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to directly operate a user's local Chrome browser with full login state and cookies, supporting 23 tools such as tab management, clicking, typing, screenshots, file upload, and network inspection through natural language.
      257 npm
      MIT

    • tabora-browser

      halatao
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to control local Chrome/Edge browser profiles through MCP, including tab groups, bounded DOM actions, observations, and optional encrypted credential use.
      MIT

    • byob

      hannah5031
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI coding tools directly control the user's already-open, logged-in Chrome to read pages, navigate, click, type, screenshot, inspect network/storage, and automate browser tasks through local MCP tools.
      3 npm
      ISC

    • auth-fetch-mcp

      ymw0407
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to access content from authenticated web pages by opening a real browser for manual login and session capture. It saves browser profiles locally so users only need to log in once per service for future automated access.
      4
      116 npm
      36
      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

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    The login trio (login/login_status/logout) and the AC tools (list_devices/get_status/get_capabilities/control) form distinct clusters, and descriptions clarify intent. The only mild overlap is between get_status (cloud state) and get_capabilities (protocol profile), but the descriptions distinguish live state from capability probing well enough.

    Naming Consistency4/5

    All tools share a predictable meiju_ prefix and snake_case verb_noun pattern (login_status, list_devices, get_status, get_capabilities). The lone deviation is meiju_control, a bare verb without a noun, though it remains readable and unambiguous.

    Tool Count5/5

    Seven tools is well-scoped for a focused smart-home AC server: full login lifecycle, device enumeration, status read, capability inspection, and a single write tool. Nothing feels redundant or padded.

    Completeness4/5

    The surface covers the core lifecycle—authenticate, discover devices, read status/capabilities, and control settings. Minor gaps exist around scheduling, scenes, or multi-device/batch operations, and only one experimental AC profile supports writes, but agent workflows are not blocked.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources