Skip to main content
Glama
threadflow-mcp

threadflow-mcp

Related Servers

Alternatives to threadflow-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      12
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to read, post, search, and engage with Twitter/X content, including AI-powered reply drafting and analytics.
      17
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to interview users about their niche, generate original Threads posts from reference examples, connect and verify accounts, and schedule, pause, or inspect publishing queues through MCP tools or GPT Actions.
      9
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      40
      45 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      10
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to manage a Threads profile through Meta's API, including posting, threads, replies, reply moderation, and insights.
      30
      30 npm
      4
      MIT

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues