Skip to main content
Glama
magical-index

alidocs-web-mcp

by magical-index
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to alidocs-web-mcp

No user-submitted related servers found.

    Related Servers

    • youdao-note-mcp

      Lancenas
      A
      license
      A
      quality
      C
      maintenance
      Bridges Youdao Note's official SSE MCP endpoint to local stdio, dynamically exposing all official tools to MCP clients so users can manage notes, todos, search, and clipping through natural language.
      3
      MIT

    • browserpilot-mcp

      Fire162
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables remote AI agents to control a local, authenticated desktop browser over MCP through an outbound WebSocket bridge and Chrome extension, supporting tab management, navigation, page reading, clicking, typing, scrolling, screenshots, and JavaScript evaluation.
      1
      MIT

    • discord-web

      VKirill
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an MCP client to read Discord servers, channels, threads, and messages, and to send messages, replies, reactions, and GIFs through an already-open Discord Web tab via a local Chrome extension and 127.0.0.1 bridge, without using a bot or the Discord HTTP API.
      8 npm
      MIT

    • feishu-mcp

      feifan2024
      A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to read, write, and search Feishu (Lark) documents, wiki pages, spreadsheets, and bitable records over MCP, with stdio or authenticated HTTP(S) transport.
      9
      259 npm
      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

    A4.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the bridge lifecycle: status, pairing, revocation, discovery of page tools, and forwarding calls. There is no meaningful overlap between them, even though get_bridge_status and list_page_tools both return state—they report on different layers (bridge vs. page-provided tools).

    Naming Consistency5/5

    All tool names follow the same snake_case verb_noun pattern: get_bridge_status, get_pairing_code, revoke_session, call_page_tool, list_page_tools. The verbs are specific and the nouns clearly indicate the target, making the naming fully predictable.

    Tool Count5/5

    Five tools is well-scoped for a bridge-focused MCP server. Each tool covers a necessary part of the pairing/connection/call lifecycle without redundancy or bloat, and the count aligns with the server's narrow purpose.

    Completeness5/5

    The tool surface covers the full bridge lifecycle: obtaining a pairing code, checking status, revoking sessions, enumerating page-provided tools, and invoking them. There are no obvious dead ends—even hosts that don't refresh tool lists are supported via call_page_tool and list_page_tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources