Meta Social Technologies MCP

io.github.facebookPublished by GitHub account facebookv1.0.0Updated Oct 24, 2026

Manage Meta apps: creation, configuration, webhooks, permissions, compliance, and App Review.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Meta's remote MCP server for managing Meta developer apps: settings, webhooks, permissions, compliance, App Review and API health.

What you can do
  • Manage Meta apps: creation, configuration, permissions and settings
  • Set up and troubleshoot webhooks, including subscription testing and delivery debugging
  • Check App Review readiness, privileges and submission history
  • Audit compliance violations and get remediation guidance
  • Monitor API health: rate limits, call volume and deprecation warnings
  • Search Meta developer documentation and diagnose access token problems
When to use it
Useful when you build or maintain apps on the Meta for Developers platform and want an assistant to audit app configuration, prepare App Review, fix webhook delivery, or check API limits and deprecations without leaving the chat.
Requirements
A remote streamable HTTP endpoint at mcp.facebook.com/devtools; no local package or CLI. Requires a Meta for Developers account and completion of an OAuth flow in the client (Claude Code, Cursor, Codex or another MCP-capable agent). Network access to the endpoint.
Before you install
OAuth grants the server access to your Meta developer account and apps; review the scopes requested. Some workflows change app configuration, such as creating or fixing webhook subscriptions, so confirm before letting the assistant write. The token-debugging workflow is described as keeping the token out of the agent context, but treat access tokens as sensitive.

Installation

In SourceWeft

  1. Open Meta Social Technologies MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.facebook%2Fdevtools/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "meta-social-technologies": {
      "type": "http",
      "url": "https://mcp.facebook.com/devtools"
    }
  }
}

README

Agentic 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 devtools plugin id, and the devtools_ 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.

All skills call the remote Meta Social Technologies MCP server (https://mcp.facebook.com/devtools). There is no standalone CLI — the skills drive the MCP for all their work, so connect it after install.

Installation

Claude Code

bash
claude plugin marketplace add facebook/agentic-toolsclaude 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:

  1. Open the Cursor marketplace and install the devtools plugin (published from this repo). The plugin bundles the skills and the Meta Social Technologies MCP config.
  2. 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:

text
$skill-installer

Then add the Meta Social Technologies MCP server to ~/.codex/config.toml:

toml
[mcp_servers.devtools]url = "https://mcp.facebook.com/devtools"

Codex will run its OAuth flow on first use. Restart Codex after editing the config.

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:

bash
# A single skillnpx skills add facebook/agentic-tools --skill <name>
# All skillsnpx 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 Meta Social Technologies MCP server to your agent's MCP config:

json
{  "mcpServers": {    "devtools": {      "type": "streamable-http",      "url": "https://mcp.facebook.com/devtools"    }  }}

Then complete the OAuth flow 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

SkillDescription
/app-health-checkFull app audit — settings, security, compliance, and app review in one report
/webhook-setupEnd-to-end webhook subscription wizard with test verification
/app-review-prepApp Review readiness check — requirements, privileges, and submission history
/debug-webhooksTroubleshoot webhook delivery issues — inspect, test, and fix subscriptions
/compliance-checkCompliance audit — violations, required actions, and remediation guidance
/api-healthAPI health monitoring — rate limits, call volume, and deprecation warnings
/api-integrationStart a new API integration — fetches setup guides, auth, permissions, and code examples
/search-docsSearch Meta developer documentation for API guides and references
/debug-access-tokenDiagnose an access token issue (expired, wrong scopes, wrong app, invalid) without the token ever entering the agent context

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/        └── 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

Source: README.md at commit 865dfb2

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 12, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts