Skip to main content
Glama

Related Servers

Alternatives to xiumi-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and CLI users to search and inspect Xiumi public-account templates, copy editable templates into their own account, recolor and replace images/text, manage drafts, validate structures, publish previews, and snapshot/restore versions through 34 MCP tools.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to turn a single Markdown document into platform-ready output — WeChat Official Account inline-styled rich text, Zhihu HTML, Xiaohongshu 1080×1440 card sets with covers, split X/Threads/Bluesky/LinkedIn threads, long images, and rendered covers. Also supports AI-assisted captions and creating WeChat draft posts via the official API, plus listing available themes and styles.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Bridges AI writing and content platforms by enabling AI agents to format Markdown and publish posts directly to WeChat Official Accounts with automatic image handling. It supports conversational theme management and streamlined drafting to eliminate the need for manual copy-pasting between editors.
      110 npm
      1,358
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI tools to preview and publish Markdown articles to WeChat Official Accounts, automatically converting content into WeChat-optimized HTML and handling cover images. Also lets users query publish status and read/like/comment statistics through natural language.
      5
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target a distinct resource+action: template search vs. tag listing, component insertion vs. deletion vs. inspection, and export vs. screenshot are clearly separable. The only friction points are the session cluster (start/login/open_article/status) and the mild overlap between xiumi_status and xiumi_get_comps, both of which report component information.

    Naming Consistency4/5

    Every tool uses the same xiumi_ prefix with snake_case, giving a predictable namespace. Most follow verb_noun (search_templates, insert_template, fill_text, set_image, delete_comp, get_comps), but a few are bare or noun forms (xiumi_status, xiumi_save, xiumi_start, xiumi_screenshot, xiumi_login), a minor deviation.

    Tool Count4/5

    16 tools is slightly heavy but each maps to a real step in the browser-automation workflow: session setup, template discovery/insertion, slot editing, typography, and export. No obviously redundant tool pads the count, though the seven session/output tools make the set feel large.

    Completeness4/5

    The lifecycle is well covered: launch/login/open/status/save/export/screenshot plus template browsing, insertion, text and image filling, deletion, component listing, typography, and metadata. Gaps remain for structural edits — no reordering/moving components, duplicating components, inserting a plain paragraph/divider, or undo — which agents may need for fine-grained layout repair.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data