Skip to main content
Glama
weflow-mcp

weflow-mcp

by L-Chris

Related Servers

Alternatives to weflow-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients on Windows to read WeChat sessions, contacts, messages, media, and files through WeFlow, and to send or natively forward messages via the desktop WeChat client.
      MIT
    • A
      license
      B
      quality
      B
      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
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local MCP clients to inspect WeChat chats, retrieve and search indexed messages, and submit tracked send-message tasks through native desktop automation on macOS and Windows.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read the local, already-logged-in WeChat account's chat history: fetch recent messages per contact for reply suggestions, bulk-export all conversations into a local SQLite index for full-text and semantic search, and export media or Moments timelines as offline HTML. Everything runs locally and read-only on macOS, exposing 15 MCP tools plus a matching CLI.
      GPL 3.0

    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

    ActivityInactive
    ResponsivenessNo recent community issues