プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。レビューとアカウント機能は今後のステップで始まります。
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

Facebook MCP

作者:IvanBBaevバージョン 0.8.0i★ –iパソコンで動く
レジストリ名io.github.IvanBBaev/facebook-mcp

インストール

概要

作者による説明(英語の原文)

Facebook Pages MCP server for the Meta Graph API — publishing, insights, moderation, messaging

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

  • 接続方法: パソコンで動く
  • トランスポート: stdio
  • カテゴリ: マーケティング・SNS
  • 入力が必要なもの:FB_SYSTEM_TOKEN, FB_ACCESS_TOKEN, FB_PAGE_TOKEN, FB_APP_SECRET, FB_CONFIRM_TOKEN, FB_HTTP_TOKEN

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

  • 基本チェック:1項目中1項目に合格
  • あなたのパソコンで、あなたのユーザーと同じ権限(ファイル、ネットワーク、アプリ)で動きます。
  • 自分で入力するもの: FB_SYSTEM_TOKEN, FB_ACCESS_TOKEN, FB_PAGE_TOKEN, FB_APP_ID, FB_APP_SECRET, FB_PAGE_ID, FB_API_VERSION, FB_ADS_API_VERSION, FB_REQUEST_TIMEOUT_MS, FB_HOST_CONCURRENCY, FB_MAX_RESULT_CHARS, FB_WRITE_MODE, FB_CONFIRM_TOKEN, FB_MEDIA_DIR, FB_JOURNAL_PATH, FB_ACTIVITY_STATE_PATH, FB_EXPORT_DIR, FB_TOOL_PACKAGES, FB_PACKAGES_DENY, FB_PACKAGES_READONLY, FB_TRANSPORT, FB_HTTP_TOKEN, FB_HTTP_PORT, FB_AD_ACCOUNT_ID, FB_ADS_BUDGET_CEILING, FB_ADS_CAMPAIGN_SPEND_CAP_MAX, FB_LOG_LEVEL

「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。

必要なもの

  • npmNode.jsのインストール(npxコマンドに必要)

どのアプリを使っていますか?

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます

{
  "mcpServers": {
    "facebook": {
      "command": "npx",
      "args": [
        "-y",
        "@ivanbaev/facebook-mcp"
      ],
      "env": {
        "FB_SYSTEM_TOKEN": "your-value",
        "FB_ACCESS_TOKEN": "your-value",
        "FB_PAGE_TOKEN": "your-value",
        "FB_APP_ID": "your-value",
        "FB_APP_SECRET": "your-value",
        "FB_PAGE_ID": "your-value",
        "FB_API_VERSION": "your-value",
        "FB_ADS_API_VERSION": "your-value",
        "FB_REQUEST_TIMEOUT_MS": "your-value",
        "FB_HOST_CONCURRENCY": "your-value",
        "FB_MAX_RESULT_CHARS": "your-value",
        "FB_WRITE_MODE": "your-value",
        "FB_CONFIRM_TOKEN": "your-value",
        "FB_MEDIA_DIR": "your-value",
        "FB_JOURNAL_PATH": "your-value",
        "FB_ACTIVITY_STATE_PATH": "your-value",
        "FB_EXPORT_DIR": "your-value",
        "FB_TOOL_PACKAGES": "your-value",
        "FB_PACKAGES_DENY": "your-value",
        "FB_PACKAGES_READONLY": "your-value",
        "FB_TRANSPORT": "your-value",
        "FB_HTTP_TOKEN": "your-value",
        "FB_HTTP_PORT": "your-value",
        "FB_AD_ACCOUNT_ID": "your-value",
        "FB_ADS_BUDGET_CEILING": "your-value",
        "FB_ADS_CAMPAIGN_SPEND_CAP_MAX": "your-value",
        "FB_LOG_LEVEL": "your-value"
      }
    }
  }
}

ターミナルでこれを実行します

claude mcp add facebook --env FB_SYSTEM_TOKEN=your-value --env FB_ACCESS_TOKEN=your-value --env FB_PAGE_TOKEN=your-value --env FB_APP_ID=your-value --env FB_APP_SECRET=your-value --env FB_PAGE_ID=your-value --env FB_API_VERSION=your-value --env FB_ADS_API_VERSION=your-value --env FB_REQUEST_TIMEOUT_MS=your-value --env FB_HOST_CONCURRENCY=your-value --env FB_MAX_RESULT_CHARS=your-value --env FB_WRITE_MODE=your-value --env FB_CONFIRM_TOKEN=your-value --env FB_MEDIA_DIR=your-value --env FB_JOURNAL_PATH=your-value --env FB_ACTIVITY_STATE_PATH=your-value --env FB_EXPORT_DIR=your-value --env FB_TOOL_PACKAGES=your-value --env FB_PACKAGES_DENY=your-value --env FB_PACKAGES_READONLY=your-value --env FB_TRANSPORT=your-value --env FB_HTTP_TOKEN=your-value --env FB_HTTP_PORT=your-value --env FB_AD_ACCOUNT_ID=your-value --env FB_ADS_BUDGET_CEILING=your-value --env FB_ADS_CAMPAIGN_SPEND_CAP_MAX=your-value --env FB_LOG_LEVEL=your-value -- npx -y @ivanbaev/facebook-mcp

動かす前に、空欄の値を入力してください。

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

{
  "mcpServers": {
    "facebook": {
      "command": "npx",
      "args": [
        "-y",
        "@ivanbaev/facebook-mcp"
      ],
      "env": {
        "FB_SYSTEM_TOKEN": "your-value",
        "FB_ACCESS_TOKEN": "your-value",
        "FB_PAGE_TOKEN": "your-value",
        "FB_APP_ID": "your-value",
        "FB_APP_SECRET": "your-value",
        "FB_PAGE_ID": "your-value",
        "FB_API_VERSION": "your-value",
        "FB_ADS_API_VERSION": "your-value",
        "FB_REQUEST_TIMEOUT_MS": "your-value",
        "FB_HOST_CONCURRENCY": "your-value",
        "FB_MAX_RESULT_CHARS": "your-value",
        "FB_WRITE_MODE": "your-value",
        "FB_CONFIRM_TOKEN": "your-value",
        "FB_MEDIA_DIR": "your-value",
        "FB_JOURNAL_PATH": "your-value",
        "FB_ACTIVITY_STATE_PATH": "your-value",
        "FB_EXPORT_DIR": "your-value",
        "FB_TOOL_PACKAGES": "your-value",
        "FB_PACKAGES_DENY": "your-value",
        "FB_PACKAGES_READONLY": "your-value",
        "FB_TRANSPORT": "your-value",
        "FB_HTTP_TOKEN": "your-value",
        "FB_HTTP_PORT": "your-value",
        "FB_AD_ACCOUNT_ID": "your-value",
        "FB_ADS_BUDGET_CEILING": "your-value",
        "FB_ADS_CAMPAIGN_SPEND_CAP_MAX": "your-value",
        "FB_LOG_LEVEL": "your-value"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

{
  "servers": {
    "facebook": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ivanbaev/facebook-mcp"
      ],
      "env": {
        "FB_SYSTEM_TOKEN": "your-value",
        "FB_ACCESS_TOKEN": "your-value",
        "FB_PAGE_TOKEN": "your-value",
        "FB_APP_ID": "your-value",
        "FB_APP_SECRET": "your-value",
        "FB_PAGE_ID": "your-value",
        "FB_API_VERSION": "your-value",
        "FB_ADS_API_VERSION": "your-value",
        "FB_REQUEST_TIMEOUT_MS": "your-value",
        "FB_HOST_CONCURRENCY": "your-value",
        "FB_MAX_RESULT_CHARS": "your-value",
        "FB_WRITE_MODE": "your-value",
        "FB_CONFIRM_TOKEN": "your-value",
        "FB_MEDIA_DIR": "your-value",
        "FB_JOURNAL_PATH": "your-value",
        "FB_ACTIVITY_STATE_PATH": "your-value",
        "FB_EXPORT_DIR": "your-value",
        "FB_TOOL_PACKAGES": "your-value",
        "FB_PACKAGES_DENY": "your-value",
        "FB_PACKAGES_READONLY": "your-value",
        "FB_TRANSPORT": "your-value",
        "FB_HTTP_TOKEN": "your-value",
        "FB_HTTP_PORT": "your-value",
        "FB_AD_ACCOUNT_ID": "your-value",
        "FB_ADS_BUDGET_CEILING": "your-value",
        "FB_ADS_CAMPAIGN_SPEND_CAP_MAX": "your-value",
        "FB_LOG_LEVEL": "your-value"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

  • FB_SYSTEM_TOKEN 秘密 env
    System-user access token (Business Manager). Takes precedence over FB_ACCESS_TOKEN and FB_PAGE_TOKEN when several are set.
  • FB_ACCESS_TOKEN 秘密 env
    Primary user access token. At least one of FB_SYSTEM_TOKEN, FB_ACCESS_TOKEN or FB_PAGE_TOKEN must be set.
  • FB_PAGE_TOKEN 秘密 env
    Long-lived Page access token used as a fallback credential when no user or system-user token is configured. It belongs to exactly one Page, so set FB_PAGE_ID to that Page ID alongside it (the doctor…
  • FB_APP_ID env
    Meta app ID; combined with FB_APP_SECRET it forms the app access token used to authorize /debug_token inspection.
  • FB_APP_SECRET 秘密 env
    Meta app secret. When set, appsecret_proof is attached to every call so a stolen bare token cannot be used on its own.
  • FB_PAGE_ID env
    Default Facebook Page ID, used when a tool call omits an explicit profile argument. Required when FB_PAGE_TOKEN is the only credential: it names the Page that token belongs to.
  • FB_API_VERSION env
    Graph API version to target. Defaults to the tested pinned version; other values are accepted verbatim as an escape hatch but are not tested.
  • FB_ADS_API_VERSION env
    Marketing API version the ads tools target (ad accounts, campaigns, ad sets, ads, insights, async reports). The Marketing API retires versions on its own, shorter schedule, so it is pinned separately…
  • FB_REQUEST_TIMEOUT_MS env
    Per-request timeout in milliseconds; integer in [1, 600000].
  • FB_HOST_CONCURRENCY env
    Maximum number of in-flight requests per Graph host; integer in [1, 64].
  • FB_MAX_RESULT_CHARS env
    Character budget applied by the result shaper before a tool result is truncated; integer in [500, 10000000].
  • FB_WRITE_MODE env
    Write gating mode: plan (validating dry-run preview, the default) or apply. It never covers the irreversible and spend tiers, which always need a per-call apply plus a plan_id.
  • FB_CONFIRM_TOKEN 秘密 env
    Operator confirmation token for out-of-band approval of irreversible or spend actions. The server prompts through MCP elicitation where the client supports it; otherwise the caller passes this value…
  • FB_MEDIA_DIR env
    Directory permitted for local media uploads. Unset means URL-only uploads and no local file access at all.
  • FB_JOURNAL_PATH env
    Path to the append-only write journal. Defaults to the XDG/%APPDATA% state path; the file is created owner-only (0600) and rotates by size.
  • FB_ACTIVITY_STATE_PATH env
    Path to the small JSON file where facebook_get_activity_since keeps, per Page, the horizon of the last complete read. Defaults to the XDG/%APPDATA% state path next to the journal; the file holds Page…
  • FB_EXPORT_DIR env
    Directory where the insights tools write a CSV or JSON file when called with `output`. Defaults to `exports/` under the XDG/%APPDATA% state path. Files are written atomically and owner-only (0600) an…
  • FB_TOOL_PACKAGES env
    Comma-separated tool packages or profiles to expose (e.g. core,posts,reader, or the profiles core|all|reader|publisher|moderator|ads). Omit for the default profile, which excludes ads.
  • FB_PACKAGES_DENY env
    Comma-separated packages OR profiles to exclude even when FB_TOOL_PACKAGES enables them; deny wins over allow. Profile names expand here exactly as they do in FB_TOOL_PACKAGES, and a profile beats a…
  • FB_PACKAGES_READONLY env
    Comma-separated packages OR profiles whose write tools are not registered at all; the read tools of those packages stay available. Profile names expand as they do in FB_TOOL_PACKAGES, so FB_PACKAGES_…
  • FB_TRANSPORT env
    Transport protocol: stdio (default) or http. The http transport binds 127.0.0.1 only and fails closed without FB_HTTP_TOKEN.
  • FB_HTTP_TOKEN 秘密 env
    Bearer token guarding the HTTP transport; required when FB_TRANSPORT=http (the server refuses to start without it). At least 16 characters — a shorter value is refused (under stdio it is dropped with…
  • FB_HTTP_PORT env
    Port for the HTTP transport (loopback only); used when FB_TRANSPORT=http. Integer in [1, 65535].
  • FB_AD_ACCOUNT_ID env
    Default ad account ID (act_… or the bare numeric id) for the opt-in ads package.
  • FB_ADS_BUDGET_CEILING env
    Hard ceiling for any ads budget write, in minor units of the ad account's own currency (e.g. cents for USD). Non-negative integer; a write above it is refused. No currency conversion: size it for the…
  • FB_ADS_CAMPAIGN_SPEND_CAP_MAX env
    Largest campaign spend_cap (the lifetime total a campaign may spend) that an ads write may set, in minor units of the ad account's own currency. Non-negative integer; a cap above it is refused, never…
  • FB_LOG_LEVEL env
    Stderr log verbosity: debug, info, warn or error. Logs never go to stdout — that is the stdio protocol channel.

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック

  • ✓ 合格

    作者とリポジトリが一致

    レジストリ名は、リポジトリを所有するGitHubアカウント IvanBBaev で確認済みです

  • … 未チェック

    今もメンテナンスされている

    このリポジトリはまだGitHubから読み取っていません

  • … 未チェック

    ライセンスがある

    このリポジトリはまだGitHubから読み取っていません

  • – 対象外

    エンドポイントが応答する

    これはパソコンで動くため、インターネット上のエンドポイントはありません

  • – 対象外

    OAuthでサインイン

    パソコンで動き、代わりにローカルの設定を使います

  • … 未チェック

    ツールの説明に隠れた指示がない

    パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです

マーケティング・SNSのほかのサーバーとの比較i

  • このカテゴリのほかの2961件のうち0%よりスターが多い
  • このカテゴリのほかの2961件のうち79%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの2961件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

Facebook MCPは安全ですか?

当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか?

入力が必要なもの:FB_SYSTEM_TOKEN, FB_ACCESS_TOKEN, FB_PAGE_TOKEN, FB_APP_SECRET, FB_CONFIRM_TOKEN, FB_HTTP_TOKEN

パソコンで動きますか、それともクラウドですか?

あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。

今もメンテナンスされていますか?

GitHubリポジトリの最終更新は–、最新バージョン(0.8.0)がレジストリに届いたのは9 日前です。

どのアプリで使えますか?

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。

代わりに使えるものは?

同じカテゴリには:MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i

Google Analytics MCP

作者:surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

パソコンで動く★ 244MIT9 日前更新
インストール

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

facebook-mcp — an MCP server for Facebook Pages

📖 [Documentation site →](https://ivanbbaev.github.io/facebook-mcp/)

A local-first, MIT-licensed TypeScript Model Context Protocol (MCP) server for developers who run their own Facebook Page(s) from an MCP client such as Claude Code, Claude Desktop, VS Code or Cursor. It talks to the Meta Graph API through your own Meta developer app and your own token: publishing, reading and insights, comment moderation and Messenger replies. Writes return a preview first by default (plan-and-apply), and the server sends no telemetry.

Things you could ask your agent once it is set up (the tools exist; see Status for what has been verified):

  • _"Draft a post with this photo and schedule it for Friday 9:00 — show me the preview first."_
  • _"Triage the unanswered comments on last week's posts."_
  • _"Give me this week's Page report."_

Not for you if you do not want to create a Meta developer app and handle an App ID, an App Secret and a token yourself — hosted social-media connectors with a one-click login are a better fit for that. It is also not for personal profiles, Groups, Instagram (there is a sibling server) or a hosted service for other people's Pages — see Not in scope.

Status

🚧 Pre-1.0, and not yet verified against a live Page. The latest release is

@ivanbaev/facebook-mcp

0.8.0 on npm. This README describes main, which can be ahead of that release;

unreleased changes are listed in changes/unreleased/.

  • Implemented, not live-verified. All 69 tools in the tool table are implemented. Every test in this repository runs against fakes and recorded fixtures behind a network fence that throws on a real fetch, so "the tests pass" means "the code does what the fixtures say", not "Meta accepted it". A live smoke harness exists (scripts/smoke/) but has not been run against a real Page for any release.
  • No client verified by hand. CI starts the packed server with npx on Linux, macOS and Windows, but no person has walked an install end-to-end in any MCP client yet — see Client compatibility.
  • Experimental tools. Some tools are marked experimental (list under Not in scope): they may change in any minor release, even after 1.0.
  • Breaking changes are planned. 0.9 changes tool contracts (see Roadmap). Read Known limitations before you rely on anything.

Contents: Status · Features · Requirements · Setup · Client compatibility · Configure credentials · Permissions · Tools · How this compares · Known limitations · Not in scope · Your responsibilities · Roadmap · Security notes · Documentation · Support · Trademark · License

Features

Implementation status only — see Status for what "implemented" does and does not mean. "Experimental" follows the experimental tier.

AreaCapabilityStatus
Core & diagnosticsIdentity, Page listing, rate-limit usage, doctor pre-flight check, setup-token✅ Implemented, not live-verified
ReadingPage and post reads, Reels, reactions, Stories, albums and photos, cursor pagination✅ Implemented, not live-verified
PublishingText / link / photo / video / Reels posts, Stories, scheduling, edit and delete✅ Implemented, not live-verified
InsightsPage, post and Reel insights, a one-call Page report, a posts comparison table, metric-rename and retirement guidance✅ Implemented, not live-verified
ModerationComment reads and triage, replies, comment edits, hide, like, delete, private reply, block/unblock, moderation settings✅ Implemented, not live-verified
MessagingConversation reads, "what is new since", replies within the 24-hour window, saved replies; message reactions, attachments and labels✅ Implemented, not live-verified (some experimental)
Ads (opt-in)Campaign / ad-set / ad reads, previews, insights, status, budget and spend-cap control; archive/delete, image upload, targeting edits, copies, boost✅ Implemented, not live-verified (some experimental)
Page profile (opt-in)Edit the Page's about, description, website, phone, hours, temporary status✅ Implemented, not live-verified, experimental
Live verificationEvery tool exercised against a real Page and a real ad account❌ Not done — see Status
npm / MCPB releasenpx @ivanbaev/facebook-mcp, attested .mcpb bundle, MCP Registry listing✅ Published — 0.8.0

Each tool wraps one capability rather than mirroring every Graph edge. Six packages (53 tools) are on by default; ads and page_admin are opt-in.

  • Local-first, no telemetry. Only three Meta hosts are ever reached (graph, graph-video, rupload); nothing phones home.
  • Least-privilege credentials. Works with a never-expiring System User token (Business Manager) or a long-lived Page token — no App Review required for an admin operating their own assets.
  • Safe writes. Tiered plan-and-apply gating; irreversible and spend actions require out-of-band confirmation and are never unlocked by an env flag alone.
  • Secret hygiene. Value-based redaction of secrets at a single choke-point across logs, errors, tool results, and the write journal.
  • Layered architecture. Lint-enforced core ← api ← mcp ← tools ← cli ← server layering, tools-as-data with a central package registry.

Requirements

  • Node.js ≥ 22 (enforced by engines and a runtime guard in the launcher; the project targets the version in .nvmrc).
  • A Meta (Facebook) developer app — a Business-type app at Standard Access is enough; no App Review is needed to operate your own assets.
  • A Facebook Page (and, for the opt-in ads package, an ad account) you administer.

Setup

The first run is five steps, in this order. Most of the time goes into Meta's app UI. docs/runbooks/onboarding.md is the long form with troubleshooting.

  1. Meta app — create a Business-type app at https://developers.facebook.com/apps and note its App ID and App Secret (Settings → Basic). setup-token needs both.
  2. Short-lived token — in the Graph API Explorer pick your app, User Token, tick the scopes you need (at least pages_show_list and pages_read_engagement), and Generate Access Token. It lives 1–2 hours, so do step 3 right away.
  3. Exchange it and write the env file — setup-token swaps it for a ~60-day token, resolves your Page and writes the env file:
   FB_APP_ID='<app id>' FB_APP_SECRET='<app secret>' \

FB_SETUP_TOKEN=' ' \ npx -y @ivanbaev/facebook-mcp setup-token

Success is status: completed in the Run block and status: written in the Env file block. The file lands at ~/.config/facebook-mcp/.env ($XDG_CONFIG_HOME if set) or %APPDATA%\facebook-mcp\.env on Windows, mode 0600. The server reads it on every start, so the client config below needs no env block. More than one Page? Re-run with --page= --force.

  1. Pre-flight — every package you plan to use should be usable:
   npx -y @ivanbaev/facebook-mcp doctor
  1. Register the server with your client and make the first call — see the next two subsections, then

冒頭だけを表示しています。続きはリポジトリで読めます

PopNxに聞く