threads-lyr
Related Servers
Alternatives to threads-lyr
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables 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-
- AlicenseAqualityCmaintenanceMCP 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.69 npmMIT
- AlicenseAqualityCmaintenanceEnables read-only research on public X data through tools for posts, threads, profiles, search, trends, collections, and saved-result analysis using free public APIs and optional sessions.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.2Academic Free v1.1
- FlicenseAqualityDmaintenanceMCP server for the Threads API, enabling profile management, content reading, publishing, replies, and discovery through 26 tools.26-
- AlicenseAqualityAmaintenanceAn 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.2411 npmMIT
TDQS
Scored across 3 tools
The two data-fetching tools are clearly distinct: one retrieves profile metadata, the other retrieves user's posts. The close_session tool is obviously a lifecycle utility and does not overlap with the data access tools.
All tool names follow a consistent verb_noun pattern: get_threads_profile, get_user_threads, and close_session. This makes the intended action and target clear at a glance.
With only 3 tools, the server is minimal but appropriately scoped for a lightweight Threads reader/API client. It's slightly on the low end but each tool serves a purpose, so the count is reasonable.
The server covers the core read-only operations: fetching a profile and fetching recent threads. However, there is no tool for retrieving a single thread's details or replies, which could be a minor gap depending on the use case. Overall, the surface is sufficient for basic public Threads data access.