Skip to main content
Glama
L-Chris

weflow-mcp

by L-Chris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to weflow-mcp

No user-submitted related servers found.

    Related Servers

    • weflow

      rfdiosuao
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read local WeChat chat records, sessions, contacts, and group members through WeFlow's local HTTP API, keeping all data on localhost.
      24 npm
      MIT

    • yan

      lyqi712
      A
      license
      B
      quality
      A
      maintenance
      Enables MCP-compatible AI clients to read local WeChat data through an existing WxLens HTTP service, so users can find messages, extract a person's statements, summarize discussions, scan multiple groups, and read related articles or attachments.
      40
      4
      MIT

    • weixin-mcp-server

      LinnnnYue
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables WeChat automation on PC via MCP, supporting sending messages and files, searching contacts, retrieving chat history, and executing commands, compatible with WeChat 4.1+.
      1
      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

    C2.9/5.0

    Scored across 12 tools

    Disambiguation3/5

    The two message retrieval tools (weflow_get_messages and weflow_get_session_messages_chatlab) have overlapping purposes; the first already supports ChatLab format, making the second redundant and confusing. Other tools are distinct within their domains.

    Naming Consistency3/5

    Tool names use a consistent 'weflow_' prefix but mix verb_noun (list_sessions, get_messages), noun-only (health, request), and SNS category prefixes (sns_timeline, sns_export) inconsistently. The use of both 'list_' and 'get_' for similar actions adds inconsistency.

    Tool Count5/5

    12 tools is appropriate for a domain covering health, chat sessions, messages, contacts, group members, and Moments. The number is well within the expected range and each tool addresses a specific sub-area.

    Completeness3/5

    The server provides comprehensive read and export functionality for chat and Moments, but lacks dedicated tools for sending messages or managing contacts/groups. While weflow_request can fill some gaps, core operations like sending a message are not directly exposed.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources