meta-mcp
Related Servers
Alternatives to meta-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP 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 gradedqualityCmaintenanceMCP server for automatic Instagram publishing — single image, carousel and Reels — via the official Instagram Graph API.26 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.6 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP 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 57 tools
Tools are clearly disambiguated by domain prefixes (ig_, meta_, threads_) and within each domain have distinct purposes (e.g., publish_photo vs. publish_video). No overlapping functionality that would confuse an agent.
All tools follow a consistent pattern of prefix_verb_noun in lowercase snake_case (e.g., ig_delete_comment, threads_publish_image). No mixing of styles or abbreviations.
57 tools is high, but covers three substantial platforms (Instagram, Threads, Meta). Each domain has a reasonable number of tools given its API surface. Slightly above the ideal range but not excessive for the scope.
The set covers core CRUD, insights, and messaging for all three platforms. Missing update operations for posts (e.g., no edit media), but this is likely an API limitation. Otherwise, lifecycle coverage is thorough.