threadflow-mcp
Related Servers
Alternatives to threadflow-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
- AlicenseAqualityDmaintenanceEnables AI agents to read, post, search, and engage with Twitter/X content, including AI-powered reply drafting and analytics.17MIT
- AlicenseAqualityCmaintenanceEnables AI agents to write, schedule, and publish Threads posts, manage carousels, images, and videos, review drafted replies, and read account insights through Meta's official Threads API. Includes per-permission allow/ask/deny controls so agents must confirm before publishing.40MIT
- AlicenseBqualityDmaintenanceEnables creating, managing, and publishing X/Twitter posts, threads, and replies directly through Claude chat. Supports draft management with the ability to create, list, publish, and delete tweet drafts.101MIT
- AlicenseAqualityAmaintenanceEnables AI agents to manage a Threads profile through Meta's API, including posting, threads, replies, reply moderation, and insights.3028 npm2MIT
- AlicenseAqualityBmaintenanceAgent-native X (Twitter) posting as one MCP server for Claude Code / Cursor / Codex / Windsurf. Your X token never touches the agent; every post clears a server-side guardrail before it ships.1114 npmAGPL 3.0
TDQS
Scored across 4 tools
The four tools map to distinct workflow stages (validate, draft, schedule, post), and descriptions explicitly contrast validate_thread's no-side-effect dry run with draft_thread's registry write. The main residual overlap is that both validate and draft perform validation, so an agent could momentarily hesitate between them, but the side-effect distinction resolves it.
All four names follow a strict verb_noun snake_case pattern (validate_thread, draft_thread, schedule_thread, post_thread). The convention is predictable and the noun is consistent across the set.
Four tools is well-scoped for a narrow thread draft/validate/schedule/post workflow, and each tool clearly earns its place. Nothing feels padded or redundant.
The happy-path lifecycle is covered (validate -> draft -> schedule or post), but there is no way to edit a registered draft, list/inspect drafts, cancel a scheduled post, or discard a draft. The in-memory registry makes these gaps more painful, since a scheduled post cannot be unscheduled through the tool surface.