Content Distribution
Automates content distribution across multiple developer and social publishing platforms. Publish articles, announcements, and updates simultaneously to DEV.to, Hashnode, GitHub Discussions, Reddit, Bluesky, LinkedIn, and Medium from a single MCP tool call.
真实 I/O · 已连通 ✓
启动 server · tools/list · 8 个工具 · content-distribution-mcp下面每个工具的字段、类型、必填项,都是我们真的把 server 启动、tools/list 拉回来的原始 JSON Schema —— 真实的工具契约。注意:下方「示例调用」是按 schema 自动生成的演示,不是真实调用的返回。
post_publishPublish one or more channel variants immediately. Side effects: makes external HTTP requests to each channel platform; writes publish state to the local YAML backend; requires valid credentials in the named profile. Idempotent on (content.id, channel) — re-running with the same IDs returns cached state without re-posting. Use post_publish for immediate-only delivery; use post_schedule when any var
contentobjectrequiredvariantsarrayrequiredprofile_namestringrequired{
"tool": "post_publish",
"arguments": {
"content": {},
"variants": [],
"profile_name": "…"
}
}post_scheduleEnqueue channel variants with schedule_at for future publishing; variants without schedule_at are published immediately. Side effects: writes entries to the local YAML schedule store; makes external HTTP requests for any immediately-published variants; requires credentials in the named profile. Idempotent on (content.id, channel). Use post_schedule when any variant needs a future publish time; use
contentobjectrequiredvariantsarrayrequiredprofile_namestringrequired{
"tool": "post_schedule",
"arguments": {
"content": {},
"variants": [],
"profile_name": "…"
}
}post_drainFire all scheduled posts due at or before the given time boundary. Side effects: makes external HTTP requests for each due entry; writes results to the YAML backend. Idempotent — already-published (content.id, channel) pairs are skipped; no-op when no entries are due. Safe to call from cron. Use post_drain on a recurring schedule to flush the queue; use post_publish or post_schedule to add new con
nowstring{
"tool": "post_drain",
"arguments": {
"now": "…"
}
}post_statusReturn publish state for content pieces. Filters by content_id, channel, or both; returns all entries when neither is given. Side effects: read-only; no external HTTP calls; no auth needed. Deterministic given unchanged backend state. Use post_status to inspect what has been published, what is queued, or what errored; use post_publish, post_schedule, or post_drain to change state.
content_idstringchannelstring{
"tool": "post_status",
"arguments": {
"content_id": "…",
"channel": "…"
}
}post_unpublishBest-effort delete of a published post on the target platform. Side effects: makes an external HTTP DELETE or update request; DEV.to sets published=false (soft delete); platforms without a delete API return success=false without error. Non-idempotent — calling on an already-deleted URL may return a platform 404. Use post_unpublish to retract a live post; use post_status first to obtain the live_ur
live_urlstringrequiredchannelstringrequired{
"tool": "post_unpublish",
"arguments": {
"live_url": "…",
"channel": "…"
}
}channel_hintsReturn static per-channel metadata: character limits, Markdown support flags, tag vocabulary, and CTA placement rules. Side effects: read-only; no external HTTP calls; no auth needed. Fully deterministic — returns compile-time adapter constants. Use channel_hints before composing a variant body to understand channel constraints; use post_publish or post_schedule once you have a valid variant.
channelstringrequired{
"tool": "channel_hints",
"arguments": {
"channel": "…"
}
}profile_listReturn all distribution profile names configured in the YAML backend. Side effects: read-only; no external HTTP calls. Deterministic given backend state. Use profile_list to discover available profiles before calling post_publish, post_schedule, or subreddit_list; then pass the chosen name as profile_name.
{
"tool": "profile_list",
"arguments": {}
}subreddit_listReturn all subreddits in the Subreddit Catalog with cooldown windows, flair vocabulary, and last-posted metadata. Optionally filtered to subreddits allowed by the named profile. Side effects: read-only; no external HTTP calls. Deterministic given backend state. Use subreddit_list to select a subreddit and obtain flair IDs before composing a reddit: channel variant; pass flair in variant.extras.fla
profile_namestring{
"tool": "subreddit_list",
"arguments": {
"profile_name": "…"
}
}综合分
效果测评卡
进行中 · 待运行真实 I/O 已解决「输入输出是什么」;下一步接 agent 真跑,量化「效果好不好」。
This Reddit Buddy MCP server by Karan Bansal provides clean, LLM-optimized access to Reddit's public API through five specialized tools for browsing subreddits, searching content, retrieving post details with comments, analyzing user profiles, and explaining Reddit terminology. Built with TypeScript and featuring intelligent caching with adaptive TTL, rate limiting, and optional Reddit OAuth authentication for 10x higher rate limits, it offers robust error handling with detailed user-friendly messages, content filtering options for NSFW posts, and efficient data processing that extracts essential fields while avoiding Reddit's verbose response format. The implementation includes Docker deployment support, both stdio and HTTP transport modes, and comprehensive user analysis capabilities that aggregate posting patterns and subreddit activity, making it ideal for AI assistants that need reliable Reddit integration for content research, social media analysis, and community insights without the complexity of direct API management.
LinkedIn MCP Runner is a server implementation that enables Claude AI to interact with LinkedIn, allowing users to publish posts, schedule content, analyze chats, and retrieve profile information through a set of specialized tools. Developed by Ertiqah, LLC, this Node.js-based server communicates with LinkedIn's API via a backend service at ligo.ertiqah.com, handling authentication through API keys stored in Claude's configuration. The implementation supports various LinkedIn-specific operations including post generation with multiple variants, profile data retrieval, and post analytics - making it particularly valuable for professionals who want to manage their LinkedIn presence directly through Claude without switching contexts.
Provides offline access to complete TwitterAPI.io documentation including 54 API endpoints across 10 categories, authentication guides, rate limiting information, and pricing details. Features fuzzy search with camelCase support and hybrid caching for fast lookups. TwitterAPI.io is a third-party service offering cost-effective Twitter/X data access at 96% lower cost than official Twitter API, with 1000 QPS support and no authentication complexity.