Meta Social Technologies MCP

What Meta Social Technologies MCP does

Meta Social Technologies MCP MCP server provides agent access to the Meta Social Technologies Developer Platform, also known as Meta for Developers. It is intended for developers managing Meta apps and integrations rather than for general social media posting. The available workflows cover application settings, webhook subscriptions, compliance status, App Review preparation, API health, documentation lookup, API integration setup, and access-token diagnosis.

The repository packages these workflows as the devtools plugin. The plugin was previously called Meta Developer Tools MCP, but the remote endpoint, plugin identifier, and devtools_ tool prefix remain unchanged. The repository is organized as a marketplace that can contain multiple plugins; the documented plugin here is the Meta Social Technologies Developer plugin.

How it works

Meta Social Technologies MCP MCP server is hosted remotely at https://mcp.facebook.com/devtools. The repository does not run a local MCP process and does not provide a standalone command-line interface. Instead, the installed agent skills send their work to the remote server after the user connects and authenticates it.

The skills follow the Agent Skills standard and provide task-oriented workflows such as /app-health-check, /webhook-setup, /app-review-prep, /debug-webhooks, /compliance-check, /api-health, /api-integration, /search-docs, and /debug-access-token. The access-token workflow is described as diagnosing token problems without placing the token into the agent context.

Setup and configuration

Claude Code users add the facebook/agentic-tools marketplace, install devtools@facebook, then use /mcp to connect to devtools and authenticate. Cursor users install the devtools plugin from its marketplace, open Settings → MCP, and complete the OAuth flow. A local plugin copy can be placed under ~/.cursor/plugins/local/devtools for testing before publication.

Codex users install the skills with the built-in skill installer, add the server URL under [mcp_servers.devtools] in ~/.codex/config.toml, and restart Codex after changing the file. Codex performs OAuth on first use. The plugin includes MCP configuration for the supported clients, but users still need to connect the remote server.

Tools and capabilities

The Meta Social Technologies MCP MCP server supports these documented workflows:

• Audit app settings, security, compliance, and App Review status.
• Configure webhook subscriptions and verify test delivery.
• Investigate webhook delivery failures and subscription problems.
• Check compliance violations, required actions, and remediation guidance.
• Review API rate limits, call volume, and deprecation warnings.
• Prepare App Review by checking requirements, privileges, and submission history.
• Start API integrations with setup guidance, authentication details, permissions, and code examples.
• Search Meta developer documentation for guides and references.
• Diagnose expired, incorrectly scoped, mismatched, or invalid access tokens.

Limitations and notes

The server is remote, so its workflows depend on access to the Meta endpoint and successful authentication. It is not a locally bundled process. The repository documentation names Claude Code, Cursor, and Codex as supported installation targets; it does not document other client-specific setup paths. No environment variables are specified for running the server because the documented configuration uses the remote URL and OAuth authentication.

The repository is licensed under MIT. The endpoint and devtools naming are retained for compatibility with existing installations that used the former Meta Developer Tools MCP name.