was-fb-mcp
Related Servers
Alternatives to was-fb-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate Facebook Page management including posting, commenting, and analytics via the Facebook Graph API.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to manage Facebook Pages through Meta's Graph API, including posting, scheduling, drafts, reading insights, and moderating comments.1541 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Facebook Pages through the Graph API, including creating posts, moderating comments, fetching page and post insights, and filtering negative feedback.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to manage Facebook Pages through the Graph API, including publishing and scheduling posts, moderating comments, and reading page and post analytics.1665 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceAutomates Facebook Page management via Graph API, enabling posting, comment moderation, and analytics through AI agents.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Facebook profiles, pages, posts, and engagement via the Graph API with OAuth authentication.2-
TDQS
Scored across 10 tools
Each tool targets a distinct operation or resource: commenting, campaign listing, insights, raw API, user info, page listing, post creation, feed fetching, comment retrieval, and ad account listing. No overlap or ambiguity.
All tools follow a consistent 'fb_' prefix followed by verb_noun in snake_case (e.g., fb_reply_comment, fb_list_campaigns). The pattern is uniform and predictable.
10 tools cover core Facebook/Meta operations: pages, posts, comments, ads, insights, and a universal API fallback. Well-scoped for a Facebook MCP server without being bloated or sparse.
Covers common CRUD for posts and comments, ad management, and insights. Missing update/delete for posts and comments, but the raw API tool (fb_api) can fill gaps. Minor but acceptable shortfall.