smithery Safe content atomic mcp-remote

Facebook Pages

MCP server for Facebook Pages API — manage posts, comments, photos, videos, insights, and Messenger conversations through 28 tools. ## Features - Create, update, delete, and schedule posts - Upload photos and videos from URL - Comment management and moderation (reply, hide, delete) - Page insights and post analytics - Messenger conversations (list, read, send messages, typing indicator) - Multi-page support with per-page access tokens ## 28 Tools **Pages (3)**: List managed pages, get page info, get page access token **Posts (6)**: List, get, create, update, delete, schedule posts **Comments (5)**: List, create, reply, delete, hide/unhide comments **Photos (3)**: Upload from URL, list, delete **Videos (3)**: Upload from URL, list, delete **Insights (4)**: Page insights, post insights, fan demographics, page views **Conversations (4)**: List conversations, get messages, send message, typing indicator ## Configuration - `FACEBOOK_PAGE_ACCESS_TOKEN` (required) — Page Access Token with pages_manage_posts, pages_manage_engagement, read_insights, pages_messaging permissions - `FACEBOOK_PAGE_ID` (optional) — Page ID, auto-detected from token if not set

Cognium trust score

50%

Tier

Unverified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: social-media
Source: Smithery
Repository: github.com/kaewz-manga/facebook-pages-mcp-community
Author type: human
Updated: 2026-04-21

View source Find related skills

MCP

Resolve Facebook Pages from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"