Content Distribution MCP Server

Publish your content everywhere - without rewriting for every platform. A MCP server that distributes a single piece of content across 8+ channels (DEV.to, Hashnode, GitHub Discussions, Reddit, Bluesky, LinkedIn, Medium, Twitter) with automatic platform-specific adaptation, idempotent publishing, per-community anti-spam rules, and centralized state management.

People connecting social media tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-06-08 · ★ 5 · #21 OF 46 MAINTAINED SOCIAL MEDIA · VERIFIED 2026-08-25

MIT · TypeScript servers · how we verify → /methodology

01 · Install Content Distribution

before you install - you'll need

The README does not document required environment variables for a basic install.

Claude Code

claude mcp add automatelab-tech-content-distribution-mc -- npx -y @automatelab/content-distribution-mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "automatelab-tech-content-distribution-mc": {
      "command": "npx",
      "args": [
        "-y",
        "@automatelab/content-distribution-mcp"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @automatelab/content-distribution-mcp - the @automatelab scope differs from the repo owner (automatelab-tech); confirm it's the project's official package

registry namespace io.github.AutomateLab-tech is GitHub-verified and matches the repo owner

03 · What Content Distribution can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v2.1.0 · 2026-05-20

04 · Who maintains Content Distribution

content-distribution is maintained by automatelab-tech. We track 4 MCP servers from automatelab-tech - 4 actively maintained, 18 combined GitHub stars, oldest repo from May 2026. Full record: all servers from automatelab-tech.

05 · Facts

repository: github.com/automatelab-tech/content-distribution-mcp
category: social media - ranked #21 of 46 actively-maintained social media servers as of 2026-08-25.
registry: io.github.AutomateLab-tech/content-distribution (active, first published 2026-05-21)
packages: npm:@automatelab/content-distribution-mcp

06 · Content Distribution FAQ

What is Content Distribution?

Is Content Distribution still maintained?

Yes - as of 2026-08-25, its last commit was 2026-06-08. We re-verify nightly.

How do I install Content Distribution?

Run `npx -y @automatelab/content-distribution-mcp`. The README does not document required environment variables for a basic install. You can also paste the ready-made client config above.

Does Content Distribution run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Content Distribution

Alternatives to Content Distribution

Maintained social media servers if Content Distribution isn't the fit.

More social media MCP servers · KonQuest Meta Ads MCP · Vk · Citedy SEO Agent · Linkedin MCP · Xtap Down

More TypeScript MCP servers · SEO Performance MCP · Simplenote MCP · Memorix · Push Engage · Notion MCP Server · see all