Meta Social Technologies MCP

Updated: Sep 8, 2026

Copy for LLM

For developers building apps and integrations on the Meta Social Technologies Developer Platform (developers.facebook.com) — the Meta Social Technologies MCP server helps you manage the Meta apps and integrations you build there. It gives your AI agent and IDE assistant a single entry point for that day-to-day work. It enables an agent to read your app configuration, monitor API health, check App Review status, configure webhook subscriptions, look up the API changelog, and search developer documentation.

Note: Meta Social Technologies MCP was formerly known as Meta Developer Tools MCP. The server endpoint and the devtools_ tool name prefix are unchanged, so existing client configurations keep working. The server is rolling out gradually and may not be available to everyone yet.

Overview

The following table summarizes the server details:

Attribute	Value
Server name	`Meta Social Technologies`
Transport	Streamable HTTP
Endpoint	`https://mcp.facebook.com/devtools`
Authentication	Meta developer account sign-in (OAuth)
Status	Beta - interface and tool set may change

Set up your IDE or agent client

The Meta Social Technologies MCP server is a remote server. Clients that support remote MCP servers can connect to the endpoint directly. For clients that only support local (stdio) servers, use the mcp-remote⁠ bridge, which proxies the remote server over stdio.

Configure your client using one of the sections below, then complete the OAuth sign-in to authenticate. Client-specific authentication steps are noted where they apply.

Claude Code and Desktop

Claude Code — run the following command to add the server:

claude mcp add --transport http meta_social_technologies https://mcp.facebook.com/devtools

Then run /mcp in a session and select meta_social_technologies to authenticate.

Claude Desktop — open Settings > Connectors > Add custom connector, then set:

Name: Meta Social Technologies
URL: https://mcp.facebook.com/devtools

OpenAI Codex App and ChatGPT

Codex App — open Settings (the gear icon, bottom left) > MCP Servers > Add servers, choose Streamable HTTP, then set:

Name: Meta Social Technologies
URL: https://mcp.facebook.com/devtools
Authentication: OAuth

Click Authenticate and complete the OAuth sign-in.

Restart the Codex App and verify that the new server entry appears in the ~/.codex/config.toml file.

ChatGPT — enable Developer Mode under Settings > Connectors > Advanced settings, then go to Settings > Connectors and create a connector with:

Name: Meta Social Technologies
URL: https://mcp.facebook.com/devtools
Authentication: OAuth

Meta Social Technologies appears in the composer’s Developer mode menu during conversations.

Cursor

Cursor reads MCP servers from mcp.json — ~/.cursor/mcp.json for all projects, or .cursor/mcp.json for a single project. The Cursor app and the Cursor CLI share this file.

Add the server to mcp.json:

{
  "mcpServers": {
    "Meta Social Technologies": {
      "url": "https://mcp.facebook.com/devtools",
      "type": "http"
    }
  }
}

You can also add it from the app: open Settings > Tools & Integrations > New MCP Server, which opens mcp.json for you to paste the entry above.

After saving, Cursor lists Meta Social Technologies under Tools & Integrations with a Needs login action. Click it to start the OAuth sign-in.

In the Cursor CLI, MCP uses the same mcp.json configuration. If a server requires OAuth, Cursor prompts you to authenticate interactively the first time the server is used.

The Meta Social Technologies MCP server authenticates with your Meta developer account over OAuth, so the same sign-in flow works with every client. You no longer need to add an App ID or App Secret to your client config. To authenticate, connect the server, sign in, and choose which apps to grant access to, as described in Sign-in flow.

After you add the server to your client (see Set up your IDE or agent client):

Start the connection. Many clients begin the OAuth flow automatically when the server is added. Others require you to click Connect or Authenticate first. For example, run /mcp in Claude Code and select Authenticate, or click Authenticate in a desktop client.
Sign in. Your browser opens to sign in with your Meta account. If it doesn’t open automatically, copy the link your client prints and open it manually.
Grant access. On the consent screen, select the apps you want the server to access.
Confirm. Return to your client and verify your connection.

You’ll need to complete the sign-in flow again when you restart the client.

Scopes

Each connected app supports two scopes, which you set per app in your Business Integrations settings.

Scope	Access
Read	Read-only access to everything the server exposes: app configuration and settings, App Review status, compliance status, API usage and health, and webhook topics and subscriptions.
Manage	Everything in Read, plus webhook writes: creating, updating, and deleting webhook subscriptions, and sending test payloads. Webhooks are the only area the server can write to.

Sending a test payload requires Manage even though it stores nothing, because it makes Meta deliver a real event to your callback URL. Keeping it out of Read means a read-only grant can never be steered into triggering deliveries.

You can manage the scopes or revoke access at any time at facebook.com⁠ > Settings > Business Integrations.

Troubleshooting

The following table describes common error messages:

Message	What it means
“It looks like this app isn’t available”	Your account doesn’t have approved access yet.
“Facebook login is currently unavailable for this app”	Your MCP client may not be supported yet.

Verify your connection

After adding the server, confirm your agent can see the tools:

Restart the IDE or agent client.
Ask the agent to list the tools it has from the meta social technologies server. You should see the 11 tools listed below.
Run a low-risk read tool. For example, devtools_app_list to list your apps, or devtools_api_changelog to look up available changelog products.

If the agent reports no tools or an authentication error, re-check the endpoint URL and confirm you completed the sign-in flow.

Tools

The Meta Social Technologies MCP exposes 11 tools. Each tool is namespaced with the devtools_ prefix. Most app-scoped tools take an app_id and require the Read or Manage scope; the changelog, documentation-search, and skill-invocation tools work without app-scoped permissions.

`devtools_discovery`

Search Meta developer documentation for API guides, references, and tutorials. Use this when an agent needs to find the right doc to answer a how-to question or ground its next step. Works without app-scoped permissions.

Actions:search_docs

Example prompt: “Search the Meta developer docs for how to set up WhatsApp Cloud API webhooks.”

`devtools_app_list`

List the Meta apps you can access through the Meta Social Technologies MCP server. Returns the apps where you hold a developer, admin, or tester role and have granted the server access, along with the permissions you granted (read or manage) and your role on each app. Supports pagination. Use this first to discover the app_id values the other tools need.

Actions:list

Example prompt: “List all the Meta apps I have access to.”

`devtools_app`

Inspect the settings, permissions, and configuration of a Meta app. Use this when an agent needs to know how an app is set up; its basic and advanced settings, security configuration, platform restrictions, or data protection officer details.

Actions:basic_settings, advanced_settings, security, restrictions, data_protection_officer

Example prompt: “Show the basic settings and security configuration for app 1234567890.”

`devtools_app_review`

Check App Review for the permissions and features your app requests. Use this when an agent needs to look up the status of a review, see what an app is approved for, or understand what’s required to submit.

Actions:status, history, privileges, requirements

Example prompt: “What’s the App Review status for app 1234567890, and which permissions is it approved for?”

`devtools_compliance`

Check the compliance status of a Meta app, open required actions, violations, and recommendations. Use this when an agent needs to confirm an app is in good standing before launching a feature or submitting for review.

Actions:status

Example prompt: “Check whether app 1234567890 has any open compliance actions or violations.”

`devtools_api_usage`

Monitor API health for a Meta app so an agent has operational visibility into an integration. Use this to see whether an app is approaching its rate limits, how much call volume it’s driving, and which APIs it depends on are deprecated.

Actions:rate_limits, call_volume, deprecations

Example prompt: “Is app 1234567890 close to any rate limits, and are there deprecations I should plan for?”

`devtools_webhook_list`

List the webhook topics available to a Meta app and the subscriptions currently configured on it, including the subscribed fields. Use this to see what an app can subscribe to and what it’s already receiving.

Actions:list_topics, list_subscriptions

Example prompt: “List the webhook topics and current subscriptions for app 1234567890.”

`devtools_webhook_manage`

Create, update, and delete webhook subscriptions on a Meta app. Use this when an agent is wiring an app to receive updates from a Meta product (for example, Messenger Platform message events or WhatsApp Cloud API events). Subscribing requires a live HTTPS callback URL that passes Meta’s verification. Requires the Manage scope.

Actions:subscribe, unsubscribe, update_fields

Example prompt: “Subscribe app 1234567890 to the page topic for the feed and messages fields, using https://example.com/webhook as the callback URL.”

`devtools_webhook_test`

Send a test payload to a webhook subscription so you can verify the receiving endpoint is reachable and handles the event correctly. Use this during initial integration and after callback-URL changes. The field must belong to an active subscription on the topic. List subscriptions first to find valid topic and field combinations. Requires the Manage scope, because it makes Meta deliver a real event to your callback URL.

Actions:test_send

Example prompt: “Send a test event to the messages field on the page topic for app 1234567890.”

`devtools_api_changelog`

Find Meta platform changelog products and their public changelog and RSS URLs, so an agent can point a developer to “what changed recently?” without browsing manually. Works without app-scoped permissions.

Actions:list_products, get_changelog_url, get_rss_url

Example prompt: “What changelog products are available, and what’s the RSS feed URL for business messaging?”

`devtools_skill_invocation`

Record the start and end of a Meta Social Technologies skill so completion rates can be measured. This is an advisory marker that agents emit around a workflow; it does not read or change anything about your apps, needs no app permissions, and does not affect what any other tool can do. You will normally see it used automatically rather than invoking it yourself.

Actions:start, end

Feedback

If you have feedback or want to see more tools, share your feedback⁠.

MCP overview

Meta Social Technologies MCP

Overview

Set up your IDE or agent client

Claude Code and Desktop

OpenAI Codex App and ChatGPT

Cursor

OAuth sign-in

Sign-in flow

Scopes

Troubleshooting

Verify your connection

Tools

devtools_discovery

devtools_app_list

devtools_app

devtools_app_review

devtools_compliance

devtools_api_usage

devtools_webhook_list

devtools_webhook_manage

devtools_webhook_test

devtools_api_changelog

devtools_skill_invocation