SuperAPI AI Directory

facebook-mcp

Public Facebook pages and profiles as JSON: likes, followers, talking-about counts, contact details and post feeds with reactions.

Open website

About this tool

facebook-mcp is a hosted Model Context Protocol (MCP) server that provides read-only Facebook tools for MCP clients such as Claude, Cursor, and Windsurf. It queries public pages or profiles by handle and returns structured JSON data, including exact like counts, contact information, owner information, and a post feed containing reactions, comments, and shares. No Meta developer app is required, and no self-hosting is needed.

Main capabilities

  • Query public Facebook pages or profiles, returning page records (like counts, contact information, owner, etc.) and a post feed (including reactions, comments, and shares).
  • Supports querying by handle (username or numeric ID).
  • Returns structured JSON for easy reasoning by AI clients.
  • Provides a pagination mechanism to traverse the post feed via nextPageToken, returning 3 posts each time.
  • Supports a language parameter that affects the localized display of strings (such as the text format of followersCount).
  • Provides one resource URI (hasdata://facebook/language) that lists the acceptable values for the language parameter; reading it does not consume credits.

How to use

  1. Get a HasData API key: create one for free in the HasData dashboard, no credit card required.
  2. Configure the MCP client:
    • Remote server URL:https://mcp.hasdata.com/mcp?apis=facebook
    • Pass the key using the x-api-key request header.
    • Clients that support OAuth can add it directly as a connector and sign in.
    • Clients that only support stdio can connect through the npm package @hasdata/facebook-mcp or the PyPI package hasdata-facebook-mcp as a launcher.
  3. Call the tool: use the hasdata_facebook_profile_getFacebookProfile tool and pass the handle parameter.
  4. Pagination: the first call returns profile, posts (the latest one), photos, and pagination (including nextPageToken). Subsequent calls use nextPageToken to get more posts, returning 3 each time, until the response no longer contains a token.

Use cases

  • Query metrics such as like counts, follower counts, and discussion counts for brand pages.
  • Get page contact information and confirm the owner.
  • Analyze the post feed to find the most shared posts.
  • Compare the reaction mix of a brand and its competitors.
  • Check whether a page is verified and its category.
  • Traverse the post feed to filter posts of a specific type (such as videos).

Limitations

  • Only public pages and public profiles are supported; private personal accounts and groups are not supported.
  • Nonexistent, deleted, or non-public pages still return a 200 status code, but the response contains error instead of profile, and the call is billed.
  • The first call to the post feed returns only 1 post, not the 3 stated by postsPerPage.
  • Subsequent pagination calls no longer return profile and photos.
  • Contact information is the information displayed to the requester on the page, not an authoritative record.
  • Image URLs are Facebook CDN links with signed parameters and will expire, so files need to be fetched and stored promptly.
  • Billing: each successful call consumes 10 credits; response size does not affect the price. The free tier provides 1,000 credits per month (about 100 calls), and paid plans start at $59/month (200,000 credits, about 20,000 calls). Concurrency limits: free tier 1 request at a time, Startup 5, Basic 15, Growth 50-500. Non-200 responses are not billed, but successful calls that do not find a page are still billed.
  • Not affiliated with Meta, uses only public data, and users must comply with Meta's terms and applicable laws on their own.

Other information

  • Open source license: MIT.
  • The test suite verifies the tool contract and runs once a week.
  • The key can be shared with other HasData APIs and combined using the apis parameter.