Skip to main content
Glama
N-Graves

threads-mcp-server

by N-Graves
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to threads-mcp-server

No user-submitted related servers found.

    Related Servers

    • meta-threads-mcp

      MetaThreads
      A
      license
      A
      quality
      C
      maintenance
      Unofficial MCP server for Meta's Threads API. Enables LLMs like Claude to publish posts, manage replies, and track insights through the Model Context Protocol.
      15
      MIT

    • 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

      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
      -

    • 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
      26 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 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: profile retrieval, post creation, listing posts, insights, deletion, and a generic passthrough. The generic 'call' tool is clearly scoped as a fallback for endpoints not covered, so there is no meaningful overlap or confusion.

    Naming Consistency5/5

    All tool names follow a consistent 'threads_verb_noun' pattern, such as threads_get_profile, threads_create_post, and threads_delete_post. The naming is uniform, descriptive, and predictable across the set.

    Tool Count5/5

    With six tools, the server covers the core Threads operations without being bloated. This is a well-scoped number for the apparent domain and leaves room for the generic passthrough to handle edge cases.

    Completeness5/5

    The tool set covers the essential profile, post creation/deletion, listing, and insights workflows. The inclusion of a generic call tool ensures that any missing or future Threads API endpoints remain accessible, so there are no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources