
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
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.
Installation
In SourceWeft
- Open Facebook Pages Mcp in the dashboard and add it to a workspace.
- 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
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, andpage_impressions_uniqueno 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)
Option 2: Clone and build
Then add to your Claude Code MCP settings:
Getting your Page Access Token
Step 1: Create a Meta App
- Go to Meta for Developers and click Create App
- Name your app and choose the "Manage everything on your Page" use case
- Connect it to your Business Portfolio
Step 2: Generate a token in the Graph API Explorer
- Open the Graph API Explorer
- Select your app from the Meta App dropdown
- Add permissions:
pages_show_list,pages_read_engagement,business_management - Click Generate Access Token and complete the OAuth flow
- 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):
If your Pages are on your personal account:
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):
Tip: For Pages you admin, Page tokens derived from a long-lived User Token never expire.
Tools
Read tools
Write tools
Utility tools
Metrics and the June 2026 deprecation
Meta deprecated these page-level metrics on June 15, 2026:
This server uses only non-deprecated metrics: page_views_total, page_fans, page_fan_adds, page_fan_removes, page_actions_post_reactions_total.
Architecture
- Zero external HTTP dependencies — uses Node 18+ native
fetch - Rate limit tracking — captures
x-app-usageandx-page-usageheaders - Cursor-based pagination — all list endpoints support
aftercursor and configurable limits - Zod validation — all tool inputs validated with descriptive error messages
Environment variables
Development
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
0Version history
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