meta-mcp-py
Related Servers
Alternatives to meta-mcp-py
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables direct management of Facebook Pages and linked Instagram Business/Creator accounts through the official Meta Graph API, including posting, scheduling, reading and responding to comments, and viewing insights.20-
- AlicenseAqualityDmaintenanceEnables Instagram and Facebook analytics via the Meta Graph API, offering account insights, media analytics, and post engagement data.196MIT
- AlicenseNot gradedqualityDmaintenanceEnables analytics and management of Facebook Pages through the Meta Graph API, including posts, insights, audience, and publishing.GPL 3.0
- FlicenseNot gradedqualityBmaintenanceEnables publishing and managing organic Facebook Page and Instagram content directly through Meta's Graph API without paid third-party services.-
- AlicenseBqualityCmaintenanceEnables MCP-based interaction with the Meta Graph API for Facebook Pages and linked Instagram Business accounts, including posting, commenting, and reading page details.611 npmMIT
- AlicenseAqualityCmaintenanceEnables publishing to Facebook, Instagram, and YouTube through official APIs using your own OAuth credentials, with support for images, videos, Reels/Stories, and scheduled posts.6MIT
TDQS
Scored across 56 tools
Most tools are distinct by platform and resource, but there is real overlap: reply_to_comment covers Facebook or Instagram while ig_reply_to_comment exists separately, and audience_overview overlaps with get_page_audience and get_ig_audience_demographics. The many publish-from-URL vs publish-from-file variants also add ambiguity despite clear descriptions.
The dominant snake_case verb_noun pattern is good, but there are notable deviations: graph_get, token_permissions, token_info, account_summary, follower_growth, audience_overview, and ig_publish_* reverse the platform/verb order compared to publish_page_*. The set is readable, but not predictable enough for a high consistency score.
56 tools is extreme for an MCP server and clearly above the 50+ threshold. Many tools are variants of the same underlying operation (URL vs local file uploads, Facebook vs Instagram replies), so the set could be significantly consolidated without losing capability.
The server covers a wide range of Facebook, Instagram, Threads, and custom-audience workflows, including publish, insights, comments, and audience management. However, notable gaps exist: no update for posts or audiences, no delete for Threads or Facebook comments, no Instagram story publishing, and graph_get is read-only so it cannot fill mutation gaps.