Threads MCP
Related Servers
Alternatives to Threads MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceEnables posting and managing Threads content via Meta Threads API, including text, image, video, carousel, and replies.9-
- AlicenseAqualityCmaintenanceEnables AI agents to write, schedule, and publish Threads posts, manage carousels, images, and videos, review drafted replies, and read account insights through Meta's official Threads API. Includes per-permission allow/ask/deny controls so agents must confirm before publishing.4045 npm1MIT
- AlicenseBqualityCmaintenanceThis server enables local access to official Meta Threads data, including latest posts, analytics insights, follower demographics, and guarded, approval-based publishing of posts and replies.6MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage a Threads profile through Meta's API, including posting, threads, replies, reply moderation, and insights.3030 npm4MIT
- FlicenseNot gradedqualityDmaintenanceA local-first MCP server for reading, planning, scheduling, and publishing Meta Threads posts, with OAuth and Keychain integration.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to browse feeds, inspect profiles and discussion threads, search topics, and publish, reply, react, repost, bookmark, follow, or download media on a signed-in Meta Threads account.1MIT
TDQS
Scored across 5 tools
Read tools (get_profile, get_post, list_recent_posts) and write tools are clearly separated by resource and action. The one blur is threads_publish_text vs threads_publish_image: publish_text explicitly becomes an image post when image_url is supplied, 'exactly like threads_publish_image', so an agent may be unsure which to call for image content.
Every tool uses the same threads_ prefix followed by a snake_case verb_noun pattern (get_profile, get_post, publish_text, publish_image, list_recent_posts). No mixing of conventions or vague verbs.
Five tools is well within the well-scoped range and each earns its place: two read/verification tools, two publish paths, and a recent-posts listing for duplicate detection. Nothing redundant or missing at the count level.
Core lifecycle of publish plus verify is covered, including idempotency and duplicate detection. However, there is no delete/retract, no reply or quote/repost capability, and no post-level insights/metrics, which are notable gaps for a Threads publishing surface.