Skip to main content
Glama
thenavidm

Threads MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Threads MCP

No user-submitted related servers found.

    Related Servers

    • Threads API MCP Server

      VladMontana
      F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to interact with Meta Threads by fetching profile details, recent posts, post and account analytics, and conversation reply trees, as well as exporting posts as JSON for archiving or embedding.
      7
      -

    • threads-mcp

      Maz1n0-zzz
      A
      license
      B
      quality
      D
      maintenance
      Enables posting and managing Threads content via Meta Threads API, including text, image, video, carousel, and replies.
      9
      9 npm
      MIT

    • meta-mcp

      exileum
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to manage Instagram and Threads accounts — publish content, handle comments, view insights, search hashtags, and manage DMs through the Meta Graph API.
      59
      55 npm
      13
      MIT

    • threads-private-api

      molkex
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with Threads via MCP, including sub-80ms keyword search, full nested discussion tree extraction, replying to any external thread, publishing posts, fetching user profiles and threads, trending topics, and engagement actions like likes and reposts.
      2
      -

    • Instagram MCP Server

      sbarbieri82831
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI applications to interact with Instagram Business accounts through Meta's Graph API, including profile retrieval, media publishing, insights, comments, conversations, and direct messaging.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool maps to a distinct Threads API action—publishing, staging, replying, insights, search, or token management—and the descriptions call out exactly where boundaries lie. The reply-related tools in particular are carefully separated by depth, scope, and ownership, so an agent is unlikely to pick the wrong one.

    Naming Consistency4/5

    The vast majority of tools follow a clear snake_case verb_noun pattern like create_post, get_replies, and hide_reply. The few exceptions—whoami, repost, reply_to—are still readable and do not break the overall predictability.

    Tool Count2/5

    At 30 tools, this is above the 25+ threshold that makes a toolset feel heavy, even though each tool appears to cover a distinct part of the Threads API. The broad scope explains the count, but it is still more than most agents will need to hold in context at once.

    Completeness5/5

    The surface covers the Threads content lifecycle completely: staging, publishing, threading, carousels, quoting, replying, reposting, deleting, reply moderation, insights, search, and token refresh. There are no obvious dead ends—the missing edit operation is an API limitation, not a gap in this server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources