Skip to main content
Glama
1736280642-Star

content-publish-engine-mcp

by 1736280642-Star
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to content-publish-engine-mcp

No user-submitted related servers found.

    Related Servers

    • sau-mcp

      xyc667
      F
      license
      B
      quality
      C
      maintenance
      MCP server wrapping social-auto-upload CLI for AI clients to verify cookies and publish videos/notes to Chinese social platforms (Douyin, Kuaishou, Xiaohongshu, Bilibili).
      10
      -

    • WeChat Publisher MCP

      BobGod
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI tools to automatically publish articles to WeChat Official Accounts, supporting Markdown-to-HTML conversion, image handling, and both preview and official publishing modes.
      2
      57
      MIT

    • Social Publisher MCP

      winLee1118
      A
      license
      A
      quality
      B
      maintenance
      A local MCP service for safely preparing, validating, and executing multi-platform social media auto-publishing, with dry-run mode and real adapter for Douyin.
      6
      1
      MIT

    • social0-mcp

      Abhishek-B-R
      A
      license
      A
      quality
      B
      maintenance
      MCP server to manage social media accounts from AI assistants, enabling post creation, scheduling, publishing, and media uploads across multiple platforms.
      13
      41 npm
      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

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools target distinct actions (preflight, create, run, get, verify, liveness, due-check, auth-probe). However, publish_liveness_check and publish_job_verify both involve verifying published state, which could cause confusion despite differing contexts.

    Naming Consistency2/5

    Naming is inconsistent: publish_job_create/run/get/verify follow verb_noun, but publish_liveness_check, publish_verification_due, and publish_content_preflight are noun phrases, and platform_auth_probe breaks the publish_ prefix. This mixed pattern reduces predictability.

    Tool Count5/5

    With 8 tools, the set is well-sized for a content publishing engine, covering the main workflow without being bloated. Each tool addresses a clear step in the process.

    Completeness4/5

    Core lifecycle (preflight, create, run, verify, liveness) is covered, enabling end-to-end publishing. Minor gaps exist: no job deletion/listing or schedule management, but these are not essential for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources