Skip to main content
Glama
WhyFaust

Faust Threads MCP

by WhyFaust
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Faust 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

    • 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

    • 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
    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

    B3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and action: feed retrieval, post-level insights, account-level insights, follower demographics, publishing a post, and publishing a reply. Even the two insights tools are explicitly separated by media metrics versus user metrics.

    Naming Consistency4/5

    All tools share the threads_ prefix and use readable snake_case, which makes the set feel cohesive. However, read tools use noun phrases like threads_post_insights while write tools use publish_ verbs, so the convention is not uniformly verb_noun.

    Tool Count5/5

    Six tools is well-scoped for a Threads-focused server. Each tool covers a distinct need without unnecessary bloat or redundancy.

    Completeness4/5

    The server covers the core Threads workflows: reading posts, fetching insights, viewing demographics, and publishing content. It is missing update/delete operations and perhaps single-post retrieval, but these are not critical for the apparent analytics-and-publishing focus.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources