Ext Ops Panel
Open dashboard
Comparison

Blowhorn - AI Native Social Media Management vs Postbase

Blowhorn - AI Native Social Media Management is an MCP server published by blowhorn-ai. Marketplaces we read that list it: 1 (Official MCP Registry). Postbase is an MCP server published by postbasehq. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-12. 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

Where each is published
MarketplaceBlowhorn - AI Native Social Media ManagementPostbase
Official MCP Registry Listed
Version: 1.0.2
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.3.0
Downloads/month (npm): 245
Downloads/week (npm): 65
Forks (GitHub): 1
Stars (GitHub): 10
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.3.0
Downloads/month (npm): 245
Downloads/week (npm): 65
Forks (GitHub): 1
Stars (GitHub): 10
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

Blowhorn - AI Native Social Media Management vs Postbase
FactBlowhorn - AI Native Social Media ManagementPostbase
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (worse)10 (better)
Forks (GitHub)11
Last release (differs)2026-11-09Not published
Where it runs (differs)Remote server (mcp.blowhorn.ai/mcp)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Not statedAGPL-3.0-or-later
Repository (differs)github.com/blowhorn-ai/blowhorn-mcpgithub.com/postbasehq/mcp
Changes in the last 7 days (differs)60
First seen (differs)2026-10-302026-10-11
Endpoint at the last check (differs)Responded 10 h ago, requires authenticationResponded 1 h ago, requires authentication

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

Blowhorn - AI Native Social Media Management

In its own words, on Official MCP Registry:

Social media and marketing management for LinkedIn, X, Reddit, Hacker News, Bluesky, Slack, GitHub

Postbase

In its own words, on Official MCP Registry:

Schedule social posts, threads and video to X, LinkedIn, Bluesky, Mastodon and YouTube from your AI.

How to run each

Blowhorn - AI Native Social Media Management As a remote MCP server

Claude Code
claude mcp add --transport http blowhorn https://mcp.blowhorn.ai/mcp

Postbase As a remote MCP server

Claude Code
claude mcp add --transport http postbase https://mcp.postbase.so/mcp

Requires: POSTBASE_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Both endpoints responded at the last daily 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

The marketplaces of Blowhorn - AI Native Social Media Management publish no settings it asks for, so we do not compare settings.

What it can do: Blowhorn - AI Native Social Media Management · What it can do: Postbase · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built