meta-mcp
Related Servers
Alternatives to meta-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Instagram Graph API integration, enabling AI applications to manage Instagram Business accounts: fetch profiles, media, insights, publish content, and handle DMs.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Instagram Business accounts via the Instagram Graph API, enabling profile retrieval, media publishing, insights, and direct messaging.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for automatic Instagram publishing — single image, carousel and Reels — via the official Instagram Graph API.18 npm-
- AlicenseNot gradedqualityDmaintenanceMCP server for Instagram Graph API providing 25 tools for publishing photos, reels, carousels, and stories, managing comments, viewing insights, and searching hashtags.5 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for organic Instagram analytics via the Meta Graph API, providing read-only tools for profiles, media, insights, audience, and optional publishing.GPL 3.0
- AlicenseNot gradedqualityCmaintenanceMCP server providing seamless integration with Instagram's Graph API for business account management, content publishing, and analytics.MIT
TDQS
Scored across 66 tools
The set has clear namespaces and many distinct actions, but several tools overlap enough to cause hesitation: e.g. threads_get_replies vs threads_get_conversation vs threads_get_pending_replies, ig_get_messages vs ig_get_conversations, and ig_get_media_list vs ig_get_media. Descriptions help differentiate most cases, but an agent can still misselect among these closely related retrieval tools.
Tools consistently use snake_case with platform prefixes (ig_, threads_, meta_) followed by an action/noun phrase. Minor deviations exist, such as ig_business_discovery lacking a clear action verb and threads_get_user_threads being described as an alias, but the overall pattern is predictable.
66 tools is very heavy for a single MCP server, even accounting for Instagram, Threads, and Meta app/token/webhook coverage. The surface feels bloated, and several near-duplicate tools could likely be consolidated or parameterized.
Coverage across Instagram and Threads is strong: publishing, comments, replies, DMs/conversations, insights, profiles, locations, search, webhooks, and token management are present. Minor gaps exist around Facebook Page management, scheduled publishing, and bulk moderation, but core lifecycle operations are well represented.