PostSprout vs io.github.MendleM/pipepost
PostSprout is an MCP server published by postsprout.app. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.MendleM/pipepost is an MCP server published by MendleM. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.MendleM/pipepost | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 No figure published Not marked · First seen |
Listed Version: 0.9.0 Downloads/month (npm): 242 Downloads/week (npm): 112 Forks (GitHub): 1 Stars (GitHub): 5 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | PostSprout | io.github.MendleM/pipepost |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 5 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release (differs) | 2026-11-02 | Not published |
| Where it runs (differs) | Remote server (postsprout.app/api/mcp) | On your machine (pipepost-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/mendlem/pipepost |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-11-02 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 11 h ago, requires authentication | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
PostSprout
Manage your blog ideas, article schedule, writing runs and draft approvals from your AI app.
io.github.MendleM/pipepost
MCP server to publish to Substack, Ghost, Dev.to, WordPress, LinkedIn + 5 more from Claude Code.
How to run each
PostSprout As a remote MCP server
claude mcp add --transport http postsprout https://postsprout.app/api/mcpio.github.MendleM/pipepost As a local MCP server: npm package
claude mcp add --transport stdio pipepost -- npx -y pipepost-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only PostSprout has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: PostSprout · What it can do: io.github.MendleM/pipepost · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.