Skip to main content
Glama
MetaThreads

meta-threads-mcp

by MetaThreads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to meta-threads-mcp

No user-submitted related servers found.

    Related Servers

    • threads-mcp-server

      N-Graves
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Meta Threads API, enabling profile retrieval, post creation and deletion, insights, and passthrough to other Threads endpoints with optional read-only and no-destructive modes.
      6
      11 npm
      MIT

    • threads-mcp

      griffinwork40
      F
      license
      A
      quality
      D
      maintenance
      MCP server for the Threads API, enabling profile management, content reading, publishing, replies, and discovery through 26 tools.
      26
      -

    • mcp-threads

      pete-builds
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Meta's Threads API that enables publishing posts and reply chains, reading timelines and insights, and managing long-lived credentials with proactive refresh and safety checks.
      MIT

    • threads-mcp

      bintangtimurlangit
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for Meta's Threads that acts as your own account, enabling reading profiles, posts, replies, timeline, search, and performing actions like posting, replying, liking, following, and scheduling, using a real logged-in browser session.
      24
      10 npm
      MIT
    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

    A3.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action; even the three creation variants are clearly separated by media type. The only subtle overlap is between get_replies and get_conversation, but their descriptions differentiate direct replies from a full threaded view.

    Naming Consistency5/5

    All tools follow a consistent pattern: prefixed with `threads_` followed by a verb and noun (e.g., create_post, get_replies, hide_reply). No mixed naming conventions, making the set predictable.

    Tool Count5/5

    15 tools is appropriately scoped for a social media API server, covering content creation, retrieval, deletion, replies, moderation, and analytics without feeling bloated.

    Completeness4/5

    Core content lifecycle (create/get/delete/reply) is covered along with moderation (hide/unhide) and analytics for both media and user. Some gaps exist such as searching posts or accessing other users' profiles, but these are beyond the typical API scope, so overall this is a solid surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources