content-distribution MCP Server

What this does

content-distribution exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

DEV_TO_API_KEY
HASHNODE_TOKEN
HASHNODE_PUBLICATION_ID
GITHUB_TOKEN
GITHUB_DISCUSSION_REPO
REDDIT_CLIENT_ID
REDDIT_CLIENT_SECRET
REDDIT_USERNAME
REDDIT_PASSWORD
BLUESKY_IDENTIFIER
BLUESKY_PASSWORD
DISTRIBUTION_BACKEND
DISTRIBUTION_BACKEND_DIR

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install content-distribution?

Run the Claude Code command in the install section to add content-distribution to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with content-distribution?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to content-distribution as well.

Does content-distribution need an API key?

Yes. Before it can run, set these environment variables: DEV_TO_API_KEY, HASHNODE_TOKEN, HASHNODE_PUBLICATION_ID, GITHUB_TOKEN, GITHUB_DISCUSSION_REPO, REDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET, REDDIT_USERNAME, REDDIT_PASSWORD, BLUESKY_IDENTIFIER, BLUESKY_PASSWORD, DISTRIBUTION_BACKEND, DISTRIBUTION_BACKEND_DIR. They go in the env block of your MCP config.