mcpbeat Sign in

Content Distribution MCP Server

local only

Content Distribution runs on your own machine — the client starts it, so there is no endpoint to ping. 55 installs a week from npm. Last commit 8 Jun 2026.

Publish content to DEV.to, Hashnode, GitHub Discussions, Reddit, Bluesky, LinkedIn, and Medium.

Installs per day peak 26 · avg 11 · +35% w/w
a month agotoday
55
Installs / week
npm · @automatelab/content-distribution-mcp
5
Stars
1 open issues
8 Jun 2026
Last commit
0 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable src/backends/yaml.ts:15
    const p = path.join(this.baseDir, file);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add content-distribution -- npx -y @automatelab/content-distribution-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "content-distribution": {
      "args": [
        "-y",
        "@automatelab/content-distribution-mcp"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.content-distribution]
command = "npx"
args = ["-y", "@automatelab/content-distribution-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "content-distribution": {
      "args": [
        "-y",
        "@automatelab/content-distribution-mcp"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "content-distribution": {
      "args": [
        "-y",
        "@automatelab/content-distribution-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: DEV_TO_API_KEY (DEV.to API key for publishing articles), HASHNODE_TOKEN (Hashnode personal access token), HASHNODE_PUBLICATION_ID (Hashnode publication ID), GITHUB_TOKEN (GitHub personal access token for GitHub Discussions), GITHUB_DISCUSSION_REPO (GitHub repo for Discussions in owner/repo format), REDDIT_CLIENT_ID (Reddit OAuth app client ID), REDDIT_CLIENT_SECRET (Reddit OAuth app client secret), REDDIT_USERNAME (Reddit account username), REDDIT_PASSWORD (Reddit account password), BLUESKY_IDENTIFIER (Bluesky handle (e.g. you.bsky.social)), BLUESKY_PASSWORD (Bluesky app password), DISTRIBUTION_BACKEND (State backend (default: yaml)), DISTRIBUTION_BACKEND_DIR (Directory for YAML state files (default: ~/.distribution-mcp)). The author declared them in the registry entry; get the values from the project itself.

Alternatives to Content Distribution

same job, measured the same way
Pipepost
by mendlem

MCP server to publish to Substack, Ghost, Dev.to, WordPress, LinkedIn + 5 more from Claude Code.

88 installs/wk local only
CLI
by noticedso

Search your developer network and trace connection paths via GitHub & LinkedIn.

46 installs/wk local only
publishwith.ai
by publishwith

Publish AI reports as managed native links with versions, access control, revocation, and audit.

answering
Herohunt MCP
by herohunt-ai

People search API - find 1 billion candidates across LinkedIn and GitHub with real-time data.

27 installs/wk local only
C
Developer Poetry
by developerpoetry

Public poetry board; any mind may publish, human or AI, by reading one line of code.

3 tools answering
Vibe Coding
by muse-code-space

Auto-document vibe coding sessions - collect, summarize, and publish

75 installs/wk local only
GitHub
by aifity

Connect AI assistants to GitHub - manage repos, issues, PRs, workflows, and git operations.

local only
Github
by davidweb3-ctrl

GitHub MCP Server - List PRs, issues, repo info, and search code

21 installs/wk local only

Content Distribution — questions

Answers built from our own checks of this server.

Why is there no uptime for Content Distribution?
Content Distribution runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @automatelab/content-distribution-mcp was installed 55 times last week.
How do I connect Content Distribution?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @automatelab/content-distribution-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Content Distribution?
The npm package @automatelab/content-distribution-mcp was installed 55 times in the last week. Week over week that is +35%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Content Distribution open source?
Yes — it is published under the MIT licence, written in TypeScript, 5 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.