Facebook MCP Server

This project is a MCP server for automating and managing interactions on a Facebook Page using the Facebook Graph API. It exposes tools to create posts, moderate comments, fetch post insights, and filter negative feedback — ready to plug into Claude, or other LLM-based agents.

🤖 What Is This?

This MCP provides a suite of AI-callable tools that connect directly to a Facebook Page, abstracting common API operations as LLM-friendly functions.

✅ Benefits

• Empowers social media managers to automate moderation and analytics.

• Seamlessly integrates with Claude Desktop or any Agent client.

• Enables fine-grained control over Facebook content from natural language.

Related MCP server: Just Facebook MCP Server

📦 Features

This fork runs the server over HTTP (streamable-http) in Docker, designed for LAN/Tailscale access. Unlike upstream, the server holds no credentials — each client sends its Facebook access token + page id per request via HTTP headers. Original stdio project: hagaihen/facebook-mcp-server.

🚀 Deploy with Docker Compose

git clone git@github.com:hoangvantuan/fb_page_mcp.git
cd fb_page_mcp
docker compose up -d --build

Service fb-mcp listens on the endpoint http://<host>:9000/mcp (container 0.0.0.0:8000, published as 9000:8000, stateless, restart: unless-stopped, healthcheck included).

docker compose logs -f      # xem log
docker compose ps           # trạng thái (Up healthy)
docker compose down         # dừng

Architecture — credentials from the client

The server keeps no secret. facebook_api.py reads credentials from the current request's headers (via the MCP SDK request_ctx), so every client uses its own Page:

Missing either header → the tool returns a clear Missing credentials error (no empty API call). run_http.py disables the SDK's DNS-rebinding protection so non-localhost Hosts (LAN/Tailscale IP) are accepted.

🧩 Connect from Claude Code

# host has exported FACEBOOK_ACCESS_TOKEN + FACEBOOK_PAGE_ID; single quotes keep
# the secret out of the config file (Claude Code resolves ${VAR} at runtime)
claude mcp add --transport http fb-mcp http://<HOST-OR-TAILSCALE-IP>:9000/mcp \
  --header 'X-Facebook-Access-Token: ${FACEBOOK_ACCESS_TOKEN}' \
  --header 'X-Facebook-Page-Id: ${FACEBOOK_PAGE_ID}'

Verify: claude mcp list shows fb-mcp connected → call get_page_info.

Getting the credentials

Get a Page Access Token (not a User token) + Page ID from https://developers.facebook.com/tools/explorer (choose Get Page Access Token), granting pages_show_list, pages_read_engagement, pages_manage_posts, pages_manage_engagement, read_insights, and pages_messaging. GET /me?fields=id with the Page token returns the Page ID.

⚠️ Security note

No application-level auth. Anyone who can reach port 9000 and holds a valid token can call every tool. Use only on a trusted LAN/tailnet. To tighten: bind ports to a single host IP ("192.168.x.x:9000:8000"), firewall the port, or add a reverse proxy checking a bearer token.

🤝 Contributing

Contributions, issues, and feature requests are welcome!
Feel free to fork the repo and submit a pull request.

• Create a branch: git checkout -b feature/YourFeature

• Commit your changes: git commit -m 'feat: add new feature'

• Push to the branch: git push origin feature/YourFeature

• Open a pull request 🎉