Meta Business MCP
Allows listing Instagram accounts associated with a Meta Business, with read-only access.
Provides tools for inspecting Meta Business assets, including ad accounts, campaigns, ads insights, and pages, as well as creating reviewable proposals for budget or delivery status changes.
Intended for WhatsApp Business API integration, but write operations including messaging are excluded from the initial version.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Meta Business MCPlist my ad accounts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Meta Business MCP
Meta Business MCP is an open-source-ready skeleton for an auditable Model Context Protocol gateway over Meta Business APIs.
The goal is not to build an autonomous marketing agent. The goal is a safe, self-hosted operations gateway that can eventually let MCP clients inspect Meta Business assets, normalize performance data, and create reviewable proposals without exposing broad Graph API access.
This project is not affiliated with, endorsed by, or sponsored by Meta or OpenAI.
Current status
This repository is a public skeleton. It intentionally does not call live Meta APIs yet.
Included:
TypeScript workspace with strict builds.
Initial MCP tool contracts.
Real stdio MCP server entrypoint.
Default-safe policy primitives.
Allowlisted Meta API boundary.
Proposal hashing and state-transition primitives.
Audit redaction helpers.
Docs, examples, and tests.
Excluded from v1:
Meta writes.
Posting, messaging, WhatsApp, deletes, budget changes, or campaign activation.
Raw lead export or lead PII retrieval.
Generic
graph_request,meta_api_call, arbitrary URL fetch, or browser automation.Clara-specific prompts, account IDs, workflows, thresholds, CRM integrations, or private playbooks.
Related MCP server: facebook-business-mcp
Tool contracts
Initial contracts:
meta_connection_statusmeta_ad_accounts_listmeta_campaigns_listmeta_ads_insights_querymeta_pages_listmeta_instagram_accounts_listsearchfetchmeta_proposal_create_budget_changemeta_proposal_create_delivery_status_change
Every handler currently returns a safe skeleton response until an allowlisted Meta operation and mocked contract tests exist.
Development
npm install
npm run typecheck
npm test
npm run buildRun the stdio server skeleton:
npm --workspace @meta-business-mcp/server run dev:stdioInstall it in Codex:
codex mcp add meta-business -- \
npm --prefix /absolute/path/to/meta-business-mcp \
--workspace @meta-business-mcp/server \
run dev:stdioSee docs/install.md for Codex and ChatGPT setup notes.
Security defaults
Read-only by default.
No raw Meta token in tool arguments or outputs.
No generic Graph proxy.
No live credentials required for tests.
No lead values in the skeleton.
No Meta mutation methods in the allowlisted client boundary.
See docs/threat-model.md and docs/architecture.md.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/guangyusong/meta-business-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server