Pipepost

What MendleM/Pipepost MCP server does

MendleM/Pipepost MCP server turns an MCP-compatible coding workflow into a content publishing pipeline. It accepts markdown and exposes tools for content quality checks, SEO preparation, frontmatter generation, draft storage, CMS publishing, social distribution, and analytics.

Content preparation includes heading and readability audits, link checking, SEO scoring, metadata generation, Schema.org JSON-LD, and frontmatter for Hugo, Jekyll, Astro, Next.js, Dev.to, Hashnode, and Ghost. It can also create platform-specific social copy or repurpose a full article into posts for Twitter/X, LinkedIn, Reddit, Bluesky, Hacker News, and newsletters.

Publishing targets include Dev.to, Ghost, Hashnode, WordPress, Medium, and Substack. Cross-publishing sends one article to several configured platforms and uses the first successful platform URL as the canonical URL for the others. Separate tools handle direct posting to Bluesky, Mastodon, LinkedIn, and X, along with Bluesky search, mentions, threads, and replies.

How it works

The server runs as a local stdio process. A client invokes its MCP tools, while credentials and local data remain on the machine. Platform credentials are stored in ~/.pipepost/config.json; drafts are stored under ~/.pipepost/drafts/. The setup tool validates and replaces credentials for a selected CMS, social network, or Unsplash.

Local operations such as basic SEO scoring, basic content audits, link checks, frontmatter generation, draft management, and IndexNow submission are free. Full SEO analysis and full audits, metadata and schema generation, social generation, repurposing, publishing, and cross-publishing may consume credits. The status tool reports remaining credits, the free-credit reset date, configured platforms, and the active plan. Credit-pack keys can be activated through the activate tool.

Setup and configuration

The README provides this MCP configuration for Claude Code:

{
  "mcpServers": {
    "pipepost": {
      "command": "npx",
      "args": ["-y", "pipepost-mcp"]
    }
  }
}

The documented initialization command is npx pipepost-mcp init. After installation, use the setup tool to add credentials for each CMS or social service. Unsplash requires an access key. Bluesky requires a handle and app password; Mastodon requires an instance URL and write-statuses token; LinkedIn requires an access token with w_member_social; and X requires four OAuth 1.0a values. CMS requirements vary by platform.

Tools and capabilities

MendleM/Pipepost MCP server includes tools for:

• SEO scoring, metadata, structured data, content audits, and link validation.
• Saving, listing, retrieving, and deleting local markdown drafts.
• Publishing one article or cross-publishing it with canonical URL wiring.
• Listing CMS posts and aggregating supported analytics.
• Finding Unsplash cover images and submitting HTTPS URLs through IndexNow.
• Generating or repurposing social content, then posting to supported networks.
• Reading Bluesky notifications, searching posts, fetching conversation trees, and replying.

Publishing and social tools return platform-specific errors for missing credentials, invalid input, credit exhaustion, rate limits, authentication failures, or upstream failures. Cross-publishing reports individual platform failures without necessarily stopping the other targets.

Limitations and notes

MendleM/Pipepost MCP server does not provide Google indexing through IndexNow; Google does not participate in that protocol. Unsplash requests are subject to its rate limits. Bluesky posts and replies are limited to 300 graphemes, LinkedIn posts to 3,000 characters, and X posts to 280 graphemes. X's free API tier limits writes to 17 tweets per 24 hours.

Analytics covers Dev.to, Ghost, Hashnode, and WordPress. Medium and Substack do not expose post-level analytics through their APIs. Substack publishing uses reverse-engineered cookie authentication.