Pipepost
Related Servers
Alternatives to Pipepost
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables an AI assistant or any MCP client to publish, cross-post, schedule, and preview markdown stories on Medium, DEV, and other pluggable platforms, while keeping credentials out of the chat and adding a canonical link back to the author's own blog.-
- AlicenseAqualityCmaintenanceAutomateLab 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/8283 npm4MIT
- AlicenseAqualityAmaintenanceEnables drafting once, reviewing per-platform previews and adaptation diffs, approving by content hash, and syndicating approved content to beehiiv/Ghost drafts and Substack paste packs. It also provides provenance-labeled cross-platform analytics and hash-chained receipts while refusing publishing and scraping.6MIT
- AlicenseNot gradedqualityBmaintenanceWrite once. Let your agent publish. Open-source, local-first CLI + MCP server that publishes one Markdown file to dev.to, Hashnode, WordPress, Ghost, Medium, Substack, Pages & X Articles. Free / open source (MIT), self-hosted. Website: https://openpub.princepal.dev/ Docs: https://openpub.princepal.dev/docs2MIT
- FlicenseAqualityDmaintenanceAn 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-
- AlicenseAqualityDmaintenanceEnables publishing markdown blog posts directly to Dev.to as drafts or live articles through a single MCP tool, with support for tags, series, canonical URL, and cover image.1MIT
TDQS
Scored across 29 tools
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.
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`).
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.
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.