Facebook Pages MCP Server
Related Servers
Alternatives to Facebook Pages MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA Facebook/Messenger MCP server that lets AI agents read and engage with profiles, pages, posts, comments, groups, Messenger conversations, notifications, and events using the user's existing browser session cookies — no Graph API app, tokens, or browser automation required. It supports multi-account and Page switching, write operations (posting, commenting, messaging) with per-identity limits and cooldowns, and honest error reporting where Meta has decommissioned cookie-era endpoints.411MIT
- AlicenseNot gradedqualityCmaintenanceConnects Facebook Business Pages to AI assistants so they can query page and post insights, engagement metrics and audience demographics, publish posts, photos, videos, reels and stories, and moderate comments through natural language. Supports granular, per-account read-only or read-and-write permissions with destructive actions disabled by default.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage Facebook Pages through Meta's Graph API, including posting, scheduling, drafts, reading insights, and moderating comments.1556 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
- AlicenseNot gradedqualityDmaintenanceAutomates Facebook Page management via Graph API, enabling posting, comment moderation, and analytics through AI agents.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate Facebook Page management including posting, commenting, and analytics via the Facebook Graph API.MIT
TDQS
Scored across 22 tools
Most tools map to a single resource+action (page_get, post_get, page_photos_list), so an agent can pick correctly. A few pairs overlap: pages_list vs pages_find, page_insights vs page_insights_metrics, and token_debug vs facebook_pages_status all answer similar questions, and set_token vs refresh_token both change the session token, but descriptions distinguish them.
All names are snake_case and follow a resource-first pattern (page_*, post_*, graph_*), which is readable and predictable. Minor deviations: the collection prefix is plural 'pages_' for two tools, admin/utility tools use a different 'facebook_pages_' prefix, and page_insights_metrics lacks an action verb.
22 tools is on the heavy side but each maps to a distinct Graph API edge or utility (posts, comments, insights, photos, videos, albums, events, messaging, auth, pagination, batch). Some listing tools could be collapsed into a generic edge reader, but nothing is clearly redundant.
The surface is almost entirely read-only: there are no direct tools to publish a post, reply to or moderate a comment, send a Messenger message, upload media, or create an event, which are core Facebook Pages workflows. graph_batch is an escape hatch for writes, but only if the agent already knows the raw Graph paths and has the write permission.