MindThread MCP
Related Servers
Alternatives to MindThread MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to manage a Threads profile through Meta's API, including posting, threads, replies, reply moderation, and insights.3030 npm4MIT
- FlicenseBqualityCmaintenanceEnables posting and managing Threads content via Meta Threads API, including text, image, video, carousel, and replies.9-
- AlicenseAqualityCmaintenanceEnables AI assistants to manage Instagram and Threads accounts — publish content, handle comments, view insights, search hashtags, and manage DMs through the Meta Graph API.5994 npm14MIT
- 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
- FlicenseAqualityBmaintenanceEnables AI assistants to interview users about their niche, generate original Threads posts from reference examples, connect and verify accounts, and schedule, pause, or inspect publishing queues through MCP tools or GPT Actions.9-
- FlicenseAqualityDmaintenanceEnables 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-
TDQS
Scored across 40 tools
The tools cover many distinct resources, but several adjacent workflows overlap: single vs bulk settings writes (update_account_settings, preview_account_settings, apply_account_settings), multiple ways to queue a draft (approve_library_item, bulk_queue_library, update_library_item), and multiple posting paths (publish, schedule_text, add_library). The long descriptions do clarify most boundaries, so an agent can usually recover, but tool-name-level disambiguation is weaker than ideal.
Most names are readable snake_case, but the conventions are mixed: verb_noun actions, bulk_* prefixes, noun-only tools such as analytics_insights and cloud_patrol_stats, and the bare verb publish. The naming is still interpretable, but it is not a predictable verb_noun pattern throughout.
At 40 tools, this is well above a focused tool surface and falls into the too-many category even for a broad account-management domain. Many operations are justified individually, but the set carries substantial workflow branching that increases agent selection cost.
Coverage is broad: account connection, material, settings and guardrails, content generation, publishing, scheduling, library management, cloud patrol, analytics, events, approvals, and usage. Minor gaps remain, such as no explicit account disconnect/delete flow and no way to delete or edit already-published posts.