Facebook Pages Mcp

io.github.lanternrowPublished by GitHub account lanternrowv1.0.3Updated Oct 24, 2026

Facebook Pages organic analytics, post management, and insights via Meta Graph API v25.0.

Overview

AI-generated overview

Lets an assistant read Facebook Page analytics, posts, comments and video insights, and publish new posts, through the Meta Graph API.

What you can do
Connects an MCP-compatible assistant to a Facebook Page via Meta Graph API v25.0. Read tools cover page metadata, page-level insights with date ranges and day/week/28-day aggregation, published posts, per-post engagement, post comments, video performance and the full page feed. One write tool, create_post, publishes text, link or photo posts, and a utility tool checks token validity, expiry and granted scopes.
When to use it
Useful when you manage Facebook Pages and want an assistant to pull organic analytics, review post and video performance, read comments, or draft and publish posts without leaving the chat. It targets current, non-deprecated page metrics and works with Pages managed through Business Manager as well as personal accounts.
Requirements
Runs locally over stdio, typically via npx or a built Node.js project (Node 18+ for native fetch). Requires a Meta app and a long-lived Facebook Page Access Token in FB_PAGE_ACCESS_TOKEN, plus the numeric Page ID in FB_PAGE_ID. Network access to the Meta Graph API is needed.
Before you install
FB_PAGE_ACCESS_TOKEN is a long-lived credential granting access to the Page; anyone with it can read Page data and publish posts, so store it securely and revoke it if exposed. The create_post tool writes publicly visible content to the Page. Page data is sent to Meta's Graph API, and token setup involves Meta app permissions such as pages_show_list, pages_read_engagement and business_management.

Installation

In SourceWeft

  1. Open Facebook Pages Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

facebook-pages-mcp

[npm version] [License: MIT]

MCP server for Facebook Pages organic analytics and management, powered by Meta Graph API v25.0.

Built for Claude Code and any MCP-compatible AI tool. Gives your AI assistant direct access to your Facebook Page data — posts, insights, comments, and more.

Part of The SEO Engine toolkit by Rex Jones — AI-powered SEO and social media tooling for agencies and businesses.

Why this exists

  • No good Facebook Pages MCP server existed. Instagram has several. Facebook Pages had none that worked on a current API version.
  • Meta deprecated legacy metrics on June 15, 2026. page_impressions, page_reach, and page_impressions_unique no longer return data. This server uses the replacement metrics from day one.
  • Business Manager support. Most businesses manage Pages through Meta Business Manager, not personal accounts. This server works with both.

Quick start

Option 1: npx (no install)

json
{  "mcpServers": {    "facebook-pages": {      "command": "npx",      "args": ["-y", "facebook-pages-mcp"],      "env": {        "FB_PAGE_ACCESS_TOKEN": "your_page_access_token",        "FB_PAGE_ID": "your_page_id"      }    }  }}

Option 2: Clone and build

bash
git clone https://github.com/lanternrow/facebook-pages-mcp.gitcd facebook-pages-mcpnpm installnpm run build

Then add to your Claude Code MCP settings:

json
{  "mcpServers": {    "facebook-pages": {      "command": "node",      "args": ["/path/to/facebook-pages-mcp/dist/index.js"],      "env": {        "FB_PAGE_ACCESS_TOKEN": "your_page_access_token",        "FB_PAGE_ID": "your_page_id"      }    }  }}

Getting your Page Access Token

Step 1: Create a Meta App

  1. Go to Meta for Developers and click Create App
  2. Name your app and choose the "Manage everything on your Page" use case
  3. Connect it to your Business Portfolio

Step 2: Generate a token in the Graph API Explorer

  1. Open the Graph API Explorer
  2. Select your app from the Meta App dropdown
  3. Add permissions: pages_show_list, pages_read_engagement, business_management
  4. Click Generate Access Token and complete the OAuth flow
  5. When asked about Pages, select "Opt in to all current and future Pages"

Step 3: Get your Page Access Token

If your Pages are managed through Business Manager (most businesses):

# First, find your business IDGET /me/businesses?fields=id,name
# Then get Page tokens for that businessGET /{business-id}/owned_pages?fields=id,name,access_token

If your Pages are on your personal account:

GET /me/accounts?fields=id,name,access_token

Copy the access_token and id for the Page you want.

Step 4: Exchange for a long-lived token (recommended)

Short-lived tokens expire in ~1 hour. Exchange for a long-lived token (~60 days):

GET /oauth/access_token  ?grant_type=fb_exchange_token  &client_id={your-app-id}  &client_secret={your-app-secret}  &fb_exchange_token={short-lived-token}

Tip: For Pages you admin, Page tokens derived from a long-lived User Token never expire.

Tools

Read tools

ToolDescription
get_page_infoPage metadata: name, category, follower count, contact info, cover photo
get_page_insightsPage-level analytics with date ranges and period aggregation (day/week/28-day)
get_published_postsPaginated list of posts authored by the Page
get_post_insightsPer-post engagement: impressions, clicks, reactions by type
get_post_commentsPaginated comments with author info and like/reply counts
get_video_insightsVideo performance: views, watch time, reactions
get_page_feedFull feed including visitor posts

Write tools

ToolDescription
create_postPublish text, link, or photo posts to the Page

Utility tools

ToolDescription
refresh_token_infoCheck token validity, expiration, and granted scopes

Metrics and the June 2026 deprecation

Meta deprecated these page-level metrics on June 15, 2026:

DeprecatedReplacement
page_impressionspage_views_total
page_reachPage Viewer metric (rolling out)
page_impressions_uniqueMedia Viewers metric (rolling out)

This server uses only non-deprecated metrics: page_views_total, page_fans, page_fan_adds, page_fan_removes, page_actions_post_reactions_total.

Architecture

src/  index.ts          # MCP server entry point, tool registration  client.ts         # Graph API HTTP client (native fetch, no dependencies)  types.ts          # TypeScript interfaces for API responses  tools/    pages.ts        # get_page_info, get_page_feed    insights.ts     # get_page_insights, get_video_insights    posts.ts        # get_published_posts, get_post_insights, get_post_comments, create_post    utils.ts        # refresh_token_info
  • Zero external HTTP dependencies — uses Node 18+ native fetch
  • Rate limit tracking — captures x-app-usage and x-page-usage headers
  • Cursor-based pagination — all list endpoints support after cursor and configurable limits
  • Zod validation — all tool inputs validated with descriptive error messages

Environment variables

VariableRequiredDescription
FB_PAGE_ACCESS_TOKENYesLong-lived Page Access Token
FB_PAGE_IDYesDefault Facebook Page ID (numeric)

Development

bash
npm run dev    # Watch mode — recompiles on savenpm run build  # Production buildnpm start      # Run the server

Contributing

Issues and PRs welcome. If Meta changes the API (they will), please open an issue.

License

MIT — see LICENSE.


Built as part of The SEO Engine by Rex Jones.

Source: README.md at commit ef120c0

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts