Skip to main content
Glama
Yero-413

wechat-clawbot-push

by Yero-413

Related Servers

Alternatives to wechat-clawbot-push

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for WeChat automation, supporting message sending, chat history retrieval, and contact list management via SSE protocol.
      5
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Free self-hosted WeChat push notification service with a standard MCP Server, enabling message sending via Webhook or MCP tools.
      GPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server providing an Agent-first, read-only interface to authorized WeChat conversations, with CLI and plugin support for Codex and Claude Code.
      1
      MIT

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool maps to a distinct step in the push workflow: checking bridge/token state, acquiring/refreshing the token, and sending the message. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Two tools use a clear verb_noun pattern (push_wechat_message, acquire_token), while bridge_status is a noun phrase that would be more consistent as get_bridge_status. Minor deviation, but the naming is still predictable and readable.

    Tool Count5/5

    Three tools is exactly right for this narrow purpose: preflight status, token acquisition, and sending. Every tool serves a necessary role in the workflow with no redundancy.

    Completeness5/5

    The lifecycle is complete: check status, acquire token if needed, then push; push_wechat_message also self-verifies the token, avoiding dead ends. There are no obvious missing operations for the stated text-push use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues