Skip to main content
Glama
MilkyWay-qt

weread-mcp

by MilkyWay-qt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to weread-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-server-weread

      ChenyqThu
      F
      license
      A
      quality
      F
      maintenance
      An MCP server enabling LLMs to access WeChat Reading bookshelf, notes, highlights, and reviews via tools like get_bookshelf, search_books, and get_book_notes_and_highlights.
      4
      137 npm
      170
      -

    • 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.
      39
      4
      MIT

    • weread-shelf

      flybear16
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables SQL queries on WeRead (微信读书) book data by syncing it into DuckDB, with an MCP server for agent-based analysis and cross-source joins.
      MIT

    • wxauto-mcp-sse

      bjdr69
      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
      -
    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/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools map cleanly to distinct API endpoints or user workflows, but the review/highlight cluster (get_book_highlights, get_best_highlights, get_highlight_reviews, get_my_reviews, list_book_reviews, get_review_detail) creates some overlap risk. The detailed descriptions do a good job of separating them, so misselection should be rare.

    Naming Consistency4/5

    The dominant get_/list_/search_ snake_case pattern is consistent and readable. Minor deviations exist—recommend_books and similar_books lack a get_/list_ prefix, and get_reading_progress vs get_read_stats uses inconsistent root wording—but these do not seriously hinder prediction.

    Tool Count4/5

    19 tools is on the heavier side, but each one covers a meaningful facet of the WeChat Reading domain: discovery, shelf, progress, highlights, reviews, stats, and recommendations. The two gateway-level meta tools add some noise but serve a legitimate fallback purpose.

    Completeness4/5

    The tool surface covers the core read-only workflows well: searching books, viewing shelf/progress, exporting highlights and reviews, pulling reading statistics, and getting recommendations. Mutating actions like adding to shelf or updating progress are absent, but they are likely outside the API's scope, and call_gateway provides a raw escape hatch for missing endpoints.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources