meta-mcp
Related Servers
Alternatives to meta-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityNot gradedmaintenanceEnables AI assistants to interact with Instagram and Facebook accounts through their APIs, supporting messaging, post management, commenting, and content creation.14-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Instagram Business accounts by automating content publishing, scheduling posts, and analyzing performance metrics. Supports posts, stories, reels, and carousels with detailed audience insights and hashtag discovery.-
- AlicenseNot gradedqualityDmaintenanceEnables AI applications to interact with Instagram Business accounts programmatically via the Graph API, supporting profile info, media posting, insights, and DMs.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI applications to interact with Instagram Business accounts through the Graph API, supporting profile management, media publishing, insights retrieval, and direct messaging capabilities.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to publish images and Reels to an Instagram Business account through the Meta Graph API, with tools for uploading media, creating and publishing containers, managing comments, and retrieving insights.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to manage a Threads profile through Meta's API, including posting, threads, replies, reply moderation, and insights.3028 npm1MIT
TDQS
Scored across 59 tools
Every tool has a distinct platform prefix (meta, ig, threads) and specific action, making purposes clear. Even overlapping tools like ig_publish_video vs ig_publish_reel are explicitly differentiated with deprecation notes. No tool names blur together.
All tools follow a consistent verb-noun pattern with platform prefixes (e.g., ig_get_media, threads_publish_text, meta_exchange_token). Verbs are predictable (get, publish, delete, reply), and there are no mixed naming conventions or vague placeholder names.
At 59 tools, this server vastly exceeds the typical 3-15 tool range and even the heavy 25+ threshold. It combines two separate platforms (Instagram and Threads) into one monolithic surface, overwhelming agents with choices. Splitting into separate per-platform servers would be more appropriate.
The surface appears remarkably complete, covering publishing, media management, comments, insights, profiles, DMs, hashtags, webhooks, token management, and even collaboration invites. Deprecated tools are properly redirected (ig_publish_video to ig_publish_reel), and no critical dead-ends are evident.