Ext Ops Panel
Open dashboard
Comparison

com.socialneuron/mcp-server vs Post Engineer

com.socialneuron/mcp-server is an MCP server published by socialneuron.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Post Engineer is an MCP server published by Ryan-Carloso. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplacecom.socialneuron/mcp-serverPost Engineer
Official MCP Registry Listed
Version: 1.6.0
Downloads/month (npm): 2 866
Downloads/week (npm): 888
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen
Listed
Version: 1.52.571
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Listed
Version: 2.1.6
Downloads/month (npm): 2 866
Downloads/week (npm): 888
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen
Not listed

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

com.socialneuron/mcp-server vs Post Engineer
Factcom.socialneuron/mcp-serverPost Engineer
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)5 (better)1 (worse)
Forks (GitHub)00
Last release (differs)2026-11-08 (worse)2026-11-12 (better)
Where it runs (differs)On your machine (@socialneuron/mcp-server)On your machine (post-engineer-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/socialneuron/mcp-servergithub.com/ryan-carloso/post-engineer
Changes in the last 7 days (differs)118
First seen (differs)2026-10-112026-10-30

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

com.socialneuron/mcp-server

In its own words, on Official MCP Registry:

52 MCP tools for AI social media: create, distribute, analyze, and optimize content.

Post Engineer

In its own words, on Official MCP Registry:

Create AI personas, generate short videos and schedule posts to YouTube, Instagram and more.

How to run each

com.socialneuron/mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "SOCIALNEURON_API_KEY=<YOUR_SOCIALNEURON_API_KEY>" --transport stdio com-socialneuron-mcp-server -- npx -y @socialneuron/mcp-server

Requires: SOCIALNEURON_API_KEY (secret)

Post Engineer As a local MCP server: npm package

Claude Code
claude mcp add --env "POST_ENGINEER_API_KEY=<YOUR_POST_ENGINEER_API_KEY>" --transport stdio post-engineer -- npx -y post-engineer-mcp

Requires: POST_ENGINEER_API_KEY (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only com.socialneuron/mcp-server asks for

  • SOCIALNEURON_API_KEY (secret)

Only Post Engineer asks for

  • POST_ENGINEER_API_KEY (secret)
  • POST_ENGINEER_API_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: com.socialneuron/mcp-server · What it can do: Post Engineer · 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