Skip to main content
Glama
Threads MCP

Threads MCP

by kerwilgil

Related Servers

Alternatives to Threads MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      C
      maintenance
      Enables posting and managing Threads content via Meta Threads API, including text, image, video, carousel, and replies.
      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
      C
      maintenance
      This server enables local access to official Meta Threads data, including latest posts, analytics insights, follower demographics, and guarded, approval-based publishing of posts and replies.
      6
      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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to browse feeds, inspect profiles and discussion threads, search topics, and publish, reply, react, repost, bookmark, follow, or download media on a signed-in Meta Threads account.
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Read tools (get_profile, get_post, list_recent_posts) and write tools are clearly separated by resource and action. The one blur is threads_publish_text vs threads_publish_image: publish_text explicitly becomes an image post when image_url is supplied, 'exactly like threads_publish_image', so an agent may be unsure which to call for image content.

    Naming Consistency5/5

    Every tool uses the same threads_ prefix followed by a snake_case verb_noun pattern (get_profile, get_post, publish_text, publish_image, list_recent_posts). No mixing of conventions or vague verbs.

    Tool Count5/5

    Five tools is well within the well-scoped range and each earns its place: two read/verification tools, two publish paths, and a recent-posts listing for duplicate detection. Nothing redundant or missing at the count level.

    Completeness3/5

    Core lifecycle of publish plus verify is covered, including idempotency and duplicate detection. However, there is no delete/retract, no reply or quote/repost capability, and no post-level insights/metrics, which are notable gaps for a Threads publishing surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues