facebook-mcp-server
An MCP (Model Context Protocol) server that exposes Facebook Page operations as MCP tools, including posting to a page, retrieving page posts/comments, filtering negative comments by keywords, replying to comments, and deleting posts/comments using a configured Facebook Page access token and Page ID.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses an access token supplied via .env (better than hardcoding), but scope granularity and authorization model are not described. Webhook security and transport/security requirements are not documented in the provided content. Deletion capabilities increase risk if misused; no evidence of audit logging, policy checks, or permission boundaries is present from the README.
⚡ Reliability
Best When
You need a quick, agent-driven interface to basic Facebook Page actions for a single page, and you can supply and protect a Facebook Page access token.
Avoid When
You cannot tolerate incomplete documentation (especially around tool schemas, parameters, pagination, and error behavior) or you need fine-grained authorization and audit trails.
Use Cases
- • Automated publishing to a Facebook Page via an MCP-enabled agent
- • Moderating Facebook Page comments (retrieval, keyword-based filtering, targeted replies)
- • Content management workflows (listing posts/comments and deleting specific items)
Not For
- • Production-grade compliance-critical moderation without additional controls (review, audit logging, and policy enforcement)
- • Use where deletion operations must be strongly permissioned and idempotently safe
- • High-assurance integrations that require documented error codes, retries, and stable pagination semantics
Interface
Authentication
The README indicates credentials are provided via a .env file containing a Page access token and Page ID. Specific OAuth flow/scopes are not documented in the provided content.
Pricing
No pricing information provided; repository appears to be a self-hosted open-source tool.
Agent Metadata
Known Gotchas
- ⚠ Deletion tools (delete_post, delete_comment) are exposed; agents may call them unintentionally without additional guardrails.
- ⚠ filter_negative_comments depends on keyword behavior that is not specified beyond 'keywords'—expect false positives/negatives unless customized.
- ⚠ No documented pagination or result limits for listing posts/comments.
- ⚠ No documented rate limit behavior; agents may need to throttle to avoid Graph API limits.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for facebook-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.