Facebook Pages Mcp

io.github.lanternrow由 GitHub 帳號 lanternrow 發布v1.0.3更新於 Oct 24, 2026

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

概覽

AI 產生的概覽

讓助理透過 Meta Graph API 讀取 Facebook 粉絲專頁的 analytics、貼文、留言與影片資料,並發佈新貼文。

可以做什麼
透過 Meta Graph API v25.0 將相容 MCP 的助理連接到 Facebook 粉絲專頁。讀取類工具涵蓋專頁中繼資料、可依日期範圍與日/週/28 天彙總的專頁層級 analytics、已發佈貼文、單篇貼文互動數據、貼文留言、影片成效以及完整專頁動態。一個寫入工具 create_post 可發佈文字、連結或相片貼文,另有工具可檢查權杖有效性、到期時間與已授權範圍。
適用情境
適合管理 Facebook 粉絲專頁、希望助理不必離開對話就能取得自然流量 analytics、檢視貼文與影片成效、閱讀留言,或起草並發佈貼文的情境。它採用目前尚未棄用的專頁指標,並同時支援透過 Business Manager 管理的專頁與個人帳號專頁。
執行需求
以 stdio 在本機執行,通常透過 npx 或已建置的 Node.js 專案(Node 18+ 以使用原生 fetch)。需要一個 Meta 應用程式,並在 FB_PAGE_ACCESS_TOKEN 提供長期專頁存取權杖,在 FB_PAGE_ID 提供數字專頁 ID。需要連線至 Meta Graph API 的網路存取。
安裝前請注意
FB_PAGE_ACCESS_TOKEN 是長期憑證,可存取該專頁;持有者可讀取專頁資料並發佈貼文,應妥善保管,外洩時立即撤銷。create_post 工具會將公開可見的內容寫入專頁。專頁資料會傳送至 Meta 的 Graph API,權杖設定涉及 pages_show_list、pages_read_engagement 與 business_management 等 Meta 應用程式權限。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Facebook Pages Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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.

來源:README.md,提交 ef120c0

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.0.3最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分