Skip to main content
Glama

Related Servers

Alternatives to Pipepost

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      AutomateLab Content Distribution publishes content across DEV.to, Hashnode, GitHub Discussions, Reddit and Bluesky, with browser workflows for LinkedIn, Medium and X. Tracks publishing state and adapts content per platform. Product and documentation: https://automatelab.tech/products/mcp/content-distribution-mcp/
      8
      38 npm
      5
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that formats and syndicates Markdown content to Twitter/X, Threads, and a static blog on S3, with automatic thread splitting and preview capabilities.
      3
      -
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for publishing to WordPress. 13 tools cover posts, categories, tags, image hosting, featured images, and SEO metadata (Rank Math, etc.) One call runs the full markdown-to-live-URL pipeline.
      13
      3 npm
      4
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Unified Publish MCP is a server that enables cross-platform social content publishing, searching, and commenting across 28+ platforms via a unified interface, leveraging the Model Context Protocol.
      AGPL 3.0

    TDQS

    A3.7/5.0

    Scored across 29 tools

    Disambiguation2/5

    Several tools are hard to tell apart: `generate_social_posts` and `repurpose` both produce platform-targeted social content from an article, and `seo_score` vs `content_audit` both score/audit markdown with overlapping issue and suggestion outputs. An agent would need to read descriptions very carefully to consistently pick the right one.

    Naming Consistency3/5

    The naming is readable and mostly snake_case, with recognizable platform prefixes like `bluesky_`, `seo_`, `x_post`, and `linkedin_post`. However, it does not follow one consistent pattern: many tools are bare verbs or nouns (`publish`, `repurpose`, `setup`, `status`, `frontmatter`, `analytics`) while others are verb_noun (`save_draft`, `list_posts`, `delete_draft`).

    Tool Count2/5

    29 tools is above the 25+ threshold and feels heavier than necessary. Some tool groups (e.g. `generate_social_posts`/`repurpose`, `seo_score`/`content_audit`) have overlapping purposes, and several very specific Bluesky/X/LinkedIn/Mastodon posting tools increase count without adding proportionally distinct capabilities.

    Completeness3/5

    The server covers a broad pipeline: drafts, SEO metadata, CMS publishing/cross-publishing, social posting, and analytics. However, there is no way to update, delete, unpublish, or fetch the full content of an already-published post, and local drafts lack an explicit update operation, leaving notable lifecycle gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues