Meta Social Technologies MCP server
Commit 12. Nov. 2026Verwalte Meta Developer Apps, Webhooks, Compliance und die API-Health über einen agentischen Plugin-Marketplace.
Auch bekannt als facebook/agentic-tools, agentic-tools
- Stars
- 25
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 1.0.0
- Letzter Commit
- 12. Nov. 2026
- Lizenz
- MIT
Was ist Meta Social Technologies MCP?
Meta Social Technologies ist ein MCP server. Verwalte Meta Developer Apps, Webhooks, Compliance und die API-Health über einen agentischen Plugin-Marketplace.
Zusammenfassung generiert aus dem README des Projekts
Über Meta Social Technologies MCP server
Der Meta Social Technologies MCP bietet einen Marketplace für agentische Plugins, die speziell für Entwickler auf der Meta for Developers Plattform entwickelt wurden. Er ermöglicht es Nutzern, Meta-Anwendungen zu verwalten, einschließlich Einstellungen, Webhooks, Compliance und App-Review-Prozessen. Der Server fungiert als Remote-Endpoint, was bedeutet, dass es sich nicht um einen lokalen Prozess handelt, sondern über OAuth in deinem gewählten AI-Client verbunden und authentifiziert werden muss.
Entwickler können diesen Server mit Clients wie Claude Code, Cursor und Codex nutzen. Das System ist als Multi-Plugin-Marketplace organisiert, bei dem spezifische Produktgruppen als eigenständige Plugins ausgeliefert werden. So bietet das devtools-Plugin beispielsweise spezialisierte Skills wie app-health-check, webhook-setup und api-health. Einige Workflows, wie etwa whatsapp-business-integration, erfordern die Verbindung sowohl dieses Servers als auch des WhatsApp Business Tools MCP servers, um korrekt zu funktionieren.
Was du damit machen kannst
- 1WhatsApp-Marketingpreise konfigurierenDer Server hilft dabei, Strategien für Feiertage zu erklären und die genehmigten maximalen Preiseinstellungen für WhatsApp Direct Sends einzurichten.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Meta Social Technologies MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenMeta Social Technologies MCP in Claude Code installieren
$ claude mcp add --transport http agentic-tools https://mcp.facebook.com/devtoolsMeta Social Technologies MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"agentic-tools": {
"url": "https://mcp.facebook.com/devtools"
}
}
}Meta Social Technologies MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"agentic-tools": {
"type": "http",
"url": "https://mcp.facebook.com/devtools"
}
}
}Meta Social Technologies MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"agentic-tools","type":"http","url":"https://mcp.facebook.com/devtools"}'Meta Social Technologies MCP in Codex installieren
$ codex mcp add agentic-tools --url https://mcp.facebook.com/devtoolsMeta Social Technologies MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.agentic-tools] url = "https://mcp.facebook.com/devtools"
Meta Social Technologies MCP in Gemini CLI installieren
$ gemini mcp add -s user --transport http agentic-tools https://mcp.facebook.com/devtoolsMeta Social Technologies MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"agentic-tools": {
"url": "https://mcp.facebook.com/devtools",
"type": "http"
}
}
}Automatisierte Checks
Geluften am 13. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Server benötigt einen Score von 80, keine kritischen Befunde und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarfacebook/agentic-tools is public and reachablegithub.com/facebook/agentic-tools ↗Bestanden
- Paket nennt dieses Repository als QuelleNicht geprüft
- Build-Provenienz (Sigstore-Attestierung)Nicht geprüft
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-12github.com/facebook/agentic-tools ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeHTTPS endpoint answered 401 (sign-in required)Bestanden
README
Auf GitHub ansehenAgentic Tools
Meta Agentic Tools is Meta's marketplace of agent plugins and skills for developers building apps and integrations on the Meta Social Technologies Developer Platform (developers.facebook.com), also known as Meta for Developers: Social Technologies. Manage the Meta apps you build there: settings, webhooks, compliance, app review, and API health, via the Meta Social Technologies MCP.
[!NOTE] Meta Social Technologies MCP was formerly known as Meta Developer Tools MCP. The server endpoint, the
devtoolsplugin id, and thedevtools_tool name prefix are unchanged, so existing installs and client configurations keep working.
This repo is structured as a multi-plugin marketplace: each product group ships as a self-contained plugin under plugins/, so it can host additional developer plugins alongside the first one, the Meta Social Technologies Developer plugin (devtools). The skills follow the open Agent Skills standard (SKILL.md), so the same skills work in Claude Code, Cursor, and Codex.
Developer Platform workflows call Meta Social Technologies MCP (
https://mcp.facebook.com/devtools).whatsapp-business-integrationspans it and WhatsApp Business Tools MCP;whatsapp-business-marketing-messages-max-price-setupuses only the WhatsApp server.The
devtoolsplugin does not bundle WhatsApp Business Tools MCP (https://mcp.facebook.com/whatsapp_business_tools). Add and authenticate that server separately as shown under Install via Vercel, following each skill's declared dependencies.
Installation
Claude Code
claude plugin marketplace add facebook/agentic-tools
claude plugin install devtools@facebook
Then connect the MCP server (its config is bundled with the plugin):
/mcp → connect to devtools → authenticate
Cursor
Install the devtools plugin from the Cursor marketplace, then authenticate the MCP server:
- Open the Cursor marketplace and install the
devtoolsplugin (published from this repo). The plugin bundles the skills and the Meta Social Technologies MCP config. - Authenticate the remote Meta Social Technologies MCP server (
devtools): Settings → MCP, then complete the OAuth flow.
To try it before it's published, copy or symlink plugins/devtools to ~/.cursor/plugins/local/devtools, then run Developer: Reload Window.
Codex
Install the skills with the built-in installer, pointing it at this repo:
$skill-installer
Then add the Meta Social Technologies MCP server to ~/.codex/config.toml:
[mcp_servers.devtools]
url = "https://mcp.facebook.com/devtools"
[mcp_servers.whatsapp_business_tools]
url = "https://mcp.facebook.com/whatsapp_business_tools"
Codex will run its OAuth flow on first use. Restart Codex after editing the config.
WhatsApp Max Price
whatsapp-business-marketing-messages-max-price-setup is grouped under plugins/devtools/skills/marketing-messages/. The leaf name and command identity are unchanged. Claude and Cursor explicitly scan both ./skills/ and ./skills/marketing-messages/ so existing flat skills remain available; Codex retains its recursive ./skills/ root. The grouping folder has no SKILL.md, inherited instructions or automatic namespace. Install the existing devtools plugin, or install just the skill from meta/agentic-tools with your client's skill installer. The repository organization does not rename the existing facebook marketplace ID or devtools@facebook plugin identifier.
Add whatsapp_business_tools at https://mcp.facebook.com/whatsapp_business_tools and complete OAuth in your client. The skill declares this dependency in metadata.mcp; installation does not authenticate it or grant Max Price eligibility. You can connect MCP first and then invoke the installed skill. Some clients require a reload. Without the skill, the existing template tools retain their guidance and confirmation gates.
The skill uses the Holiday 2026 guide for ladder-up/leap strategies, newly opted-in versus dormant cohort advice, and country-specific A/B test planning. Recommendations are relative to current published rates, not automatic country overrides or resolved monetary bids. Live rates, reach estimates and monetary normalization are not supplied by the current account/template tools; missing inputs require a strategy explanation or explicit-value fallback. Exact-preview approval remains mandatory. The skill does not schedule price changes or send messages. For new account/phone setup, use whatsapp-business-integration separately.
Install via Vercel (skills.sh)
The skills are also listed on Vercel's skills directory, skills.sh, and install with the skills CLI into any agent it supports:
# A single skill
npx skills add facebook/agentic-tools --skill <name>
# All skills
npx skills add facebook/agentic-tools --skill '*'
[!WARNING] This installs the skill text only. It does NOT install or authenticate the MCP server — you must add it separately, or the skills cannot run.
Add the servers each installed skill requires. whatsapp-business-integration uses both servers below; whatsapp-business-marketing-messages-max-price-setup needs only whatsapp_business_tools. The example uses Claude Code's http transport name; for Cursor, omit type and keep each URL.
{
"mcpServers": {
"devtools": {
"type": "http",
"url": "https://mcp.facebook.com/devtools"
},
"whatsapp_business_tools": {
"type": "http",
"url": "https://mcp.facebook.com/whatsapp_business_tools"
}
}
}
Then complete the OAuth flow for each server in your own agent (for example /mcp in Claude Code), and restart or reload the agent if it does not pick up the new server.
The skills live under plugins/devtools/skills/ rather than a top-level skills/ folder. If npx skills add facebook/agentic-tools -l reports no skills, name one with --skill <name> or pass --full-depth.
Skills
| Skill | Description |
|---|---|
/app-health-check |
Full app audit — settings, security, compliance, and app review in one report |
/webhook-setup |
End-to-end webhook subscription wizard with test verification |
/app-review-prep |
App Review readiness check — requirements, privileges, and submission history |
/debug-webhooks |
Troubleshoot webhook delivery issues — inspect, test, and fix subscriptions |
/compliance-check |
Compliance audit — violations, required actions, and remediation guidance |
/api-health |
API health monitoring — rate limits, call volume, and deprecation warnings |
/api-integration |
Start a new API integration — fetches setup guides, auth, permissions, and code examples |
/search-docs |
Search Meta developer documentation for API guides and references |
/debug-access-token |
Diagnose an access token issue (expired, wrong scopes, wrong app, invalid) without the token ever entering the agent context |
/whatsapp-business-integration |
Set up WhatsApp Business messaging end to end, from the app to the first sent message |
/app-setup |
Set up an app for a product integration — create or pick the app, connect a business portfolio, and add use cases |
/whatsapp-business-marketing-messages-max-price-setup |
Explain holiday/cohort choices and configure explicitly approved Max Price settings for Direct sends; WhatsApp MCP only |
Architecture
agentic-tools/
├── server.json # Public MCP registry listing (registry.modelcontextprotocol.io)
├── .github/
│ └── workflows/
│ └── publish-mcp-registry.yml # Publishes server.json to the registry via GitHub OIDC
├── .claude-plugin/
│ └── marketplace.json # Claude Code / Codex marketplace manifest
├── .cursor-plugin/
│ └── marketplace.json # Cursor marketplace manifest (lists plugins by source)
├── .cursor/
│ └── mcp.json # Meta Social Technologies MCP config for manual Cursor setup
└── plugins/
└── devtools/ # The Meta Social Technologies Developer plugin
├── .claude-plugin/
│ └── plugin.json # Claude Code plugin manifest
├── .cursor-plugin/
│ └── plugin.json # Cursor plugin manifest
├── .codex-plugin/
│ └── plugin.json # Codex plugin manifest
├── .mcp.json # MCP config for Claude Code / Codex (auto-bundled)
├── mcp.json # MCP config for Cursor (auto-discovered)
├── skills/ # Skill definitions (SKILL.md per workflow)
│ ├── app-health-check/
│ ├── webhook-setup/
│ ├── app-review-prep/
│ ├── debug-webhooks/
│ ├── compliance-check/
│ ├── api-health/
│ ├── api-integration/
│ ├── search-docs/
│ ├── debug-access-token/
│ ├── whatsapp-business-integration/
│ ├── app-setup/
│ └── marketing-messages/
│ └── whatsapp-business-marketing-messages-max-price-setup/
│ ├── SKILL.md
│ └── references/
│ ├── scenarios.md
│ └── holiday-2026.md
└── hooks/
├── session-init.sh # Session-start hook
└── session-context.json # Context injected at session start
The Meta Social Technologies MCP is a remote server — it is not bundled as a process; users authenticate it in their agent.
License
MIT
Meta Social Technologies MCP Fragen
Wie füge ich Meta Social Technologies MCP zu Claude Code hinzu?
Führe claude mcp add --transport http agentic-tools https://mcp.facebook.com/devtools in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Meta Social Technologies MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Was kann ich mit diesem MCP server verwalten?
Du kannst Meta App-Einstellungen, Webhooks, Compliance, App-Reviews und die API-Health verwalten.
Enthält dieser Server WhatsApp Business Tools?
Nein, das devtools-Plugin enthält nicht den WhatsApp Business Tools MCP; du musst diesen Server separat hinzufügen und authentifizieren.
Wird der Server lokal gehostet?
Nein, der Meta Social Technologies MCP ist ein Remote-Server, den Nutzer innerhalb ihres Agents authentifizieren müssen.