← All servers
🔧

Content DistributionVerified🛡 No advisories

io.github.AutomateLab-tech/content-distribution
New to MCP? Start here →
5★ stars
0weekly installs
1 month agolast release

Provenancewhere it came from, and what was verified

✓
Verified namespace

Published to the official MCP registry by github.com/automatelab-tech, which proved it owns this namespace.

Verified owner: github.com/automatelab-tech ↗io.github.AutomateLab-tech/content-distribution

🛡 Permissions & trustwhat this server can touch before you run it

◆
Secrets required
Needs DEV_TO_API_KEY, HASHNODE_TOKEN, GITHUB_TOKEN, REDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET, REDDIT_PASSWORD, ….
✓
Configuration
Reads HASHNODE_PUBLICATION_ID, GITHUB_DISCUSSION_REPO, REDDIT_USERNAME, BLUESKY_IDENTIFIER, DISTRIBUTION_BACKEND, DISTRIBUTION_BACKEND_DIR.

About

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

Packages & transports

npm@automatelab/content-distribution-mcpv2.2.1 · npx

Metadata

Sourcegithub.com/AutomateLab-tech/content-distribution-mcp ↗
Categorydevops
LicenseMIT
Add to your client
Pick your client, copy, paste into its config. That's the whole setup.
~/.claude/claude_desktop_config.json
{
  "mcpServers": {
    "content_distribution": {
      "command": "npx",
      "args": [
        "-y",
        "@automatelab/content-distribution-mcp"
      ]
    }
  }
}

▶ Try itrun it locally

This is a local server, so it runs on your machine, not ours. Paste this to open it in the official MCP Inspector and poke at its tools:

npx @modelcontextprotocol/inspector npx -y @automatelab/content-distribution-mcp