SpeedContent Social MCP
Related Servers
Alternatives to SpeedContent Social MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage social media posts across multiple platforms by scoring virality, generating threads, converting formats, optimizing hooks, scheduling campaigns, and validating platform limits.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create, schedule, and manage social media posts across 10 platforms via a unified API.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to draft, schedule, and publish social media content, generate AI text and image variations, analyze performance, and automate social workflows.MIT

AdaptlyPostofficial
AlicenseAqualityAmaintenanceGives AI agents the ability to schedule and publish social media posts to Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Pinterest, Threads, and Bluesky. Create, schedule, and bulk-plan posts with per-platform captions, then check per-platform results and retry failures.12MIT
PostMCP MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to manage social media publishing across platforms like LinkedIn, Twitter, Facebook, Instagram, Threads, and Bluesky.729 npmMIT- AlicenseAqualityBmaintenanceEnables AI assistants to schedule and publish social media posts to platforms like Instagram, TikTok, YouTube, LinkedIn, Facebook, X, Threads, and Pinterest using natural language.33586 npm4MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: generate_social_post creates work, check_social_job only polls an existing job by id, and list_social_platforms only reads metadata. The descriptions even spell out when to use check_social_job (only after a timeout) versus generate_social_post, so there is no realistic misselection.
All three tools follow the same verb_noun snake_case pattern: generate_social_post, check_social_job, list_social_platforms. The verb (generate/check/list) also maps cleanly onto each tool's action, reinforcing the pattern.
Three tools is on the low end but well-matched to a narrow single-purpose service: one action tool, one status poller, one discovery tool. Nothing feels redundant or padded, though the surface is thin enough that a couple more operations could reasonably exist.
The core lifecycle for generating a social post is covered: discover platforms, generate, and recover from timeouts via job lookup. Minor gaps remain — there is no way to cancel or list jobs, or to fetch/reuse a completed post outside the timeout path — but agents can work around these.