Facebook Scraper3 MCP Server
Related Servers
Alternatives to Facebook Scraper3 MCP Server
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 MCP clients to query public Facebook pages and profiles by handle, retrieving like counts, contact details, owner info, and recent posts with reactions, comments, and shares as structured JSON.1269 npm331 PyPI10MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to access structured public web data (profiles, posts, videos, etc.) from social networks and directories via natural language, by forwarding tool calls to the scraper-api.com API.8419 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and browsing Facebook Marketplace listings, retrieving item details, nearby items, categories, and parsing listing URLs through MCP tools.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Facebook profiles, pages, posts, and engagement via the Graph API with OAuth authentication.2-
- AlicenseNot gradedqualityCmaintenanceEnables searching and scraping the public Facebook Ad Library to extract structured ad data such as advertiser, copy, landing URLs, and CTAs for competitive research, all without an account or API token.MIT
TDQS
Scored across 40 tools
The tool set has clear distinctions for major categories like pages, groups, profiles, and search, but there is significant overlap within categories that could cause confusion. For example, 'comments' and 'comments_2' have ambiguous boundaries, and multiple search tools (e.g., 'search_post', 'search_video', 'search_hashtag') might be misselected due to similar purposes. Descriptions help clarify some differences, but the overlap is notable.
Most tools follow a consistent verb_noun or noun_verb pattern with underscores, such as 'browse_games', 'get_group_details', and 'search_events'. There are minor deviations like 'page_id' (noun_noun) and 'reshares' (noun only), but overall the naming is predictable and readable across the set.
With 40 tools, the count is excessive for a scraper server, leading to potential bloat and complexity. While Facebook has many data types, this many tools suggests over-fragmentation rather than a well-scoped set, making it harder for agents to navigate efficiently. A more consolidated approach with 15-25 tools would be more appropriate.
The tool surface covers a wide range of Facebook entities comprehensively, including pages, groups, profiles, events, posts, comments, and various search functions. Minor gaps exist, such as limited update or delete operations (expected for scraping), but agents can perform most data retrieval tasks without significant dead ends in the core workflows.