Meta Developer Tools MCP: What It Does, How to Use It and Where It Stops for WhatsApp
Meta shipped an official MCP server. It is a genuinely useful developer tool. It also cannot run a single WhatsApp campaign. Knowing the difference saves you a lot of confusion.
For a long time the answer to does Meta have an official MCP was no. That changed in 2026 when Meta launched the Developer Tools MCP, a hosted Model Context Protocol server that lets an AI assistant like Claude, ChatGPT or Cursor reach into your Meta developer account without you ever opening the dashboard. If you build on the Meta platform, it is worth setting up.
It is easy to expect more from it than it offers. Because it carries the Meta name and touches WhatsApp, it is worth being clear up front about what it is not: it does not run WhatsApp Business messaging from your assistant. This guide explains what the Meta Developer Tools MCP actually does, how to connect it and exactly where its job ends and running WhatsApp campaigns begins.
What the Meta Developer Tools MCP is
The Model Context Protocol is a standard way for an AI assistant to call external tools. The Meta Developer Tools MCP is Meta’s own MCP server, aimed squarely at developers building apps and integrations on the Meta platform. Instead of leaving your editor to dig through the dashboard, you ask your assistant and it queries your app configuration, health and status for you.
It is a remote, hosted server, so there is nothing to run locally. It reads from your existing Meta developer account and, in one narrow case, makes changes. Everything it does falls into monitoring and app maintenance, not customer-facing operations.
What it can do: the ten tools
The server exposes ten tools in the devtools namespace, grouped by how much access they need.
No permission requiredOpen to anyone connected
devtools_discoverySearches Meta’s developer documentation, so you can ask for the right endpoints and permissions in plain language.devtools_api_changelogSurfaces changelog products and feeds, so you hear about breaking changes before they break you.Read scopeMonitoring only
devtools_app_listLists the apps you can access and your permission level on each.devtools_appInspects a single app’s settings, security, platform restrictions and data protection details.devtools_app_reviewChecks App Review status and what you still need to submit.devtools_complianceSurfaces required actions and violations, including the Data Access renewal deadlines that quietly cost people their app access.devtools_api_usageMonitors your Graph API rate limits and flags deprecations.devtools_webhook_listShows your webhook topics and current subscriptions.Manage scopeWrites, webhooks only
devtools_webhook_manageCreates, updates or deletes webhook subscriptions.devtools_webhook_testSends a sample payload to a subscription so you can confirm it works.That is the whole surface. Read scope is monitoring only. Manage scope adds exactly one capability: webhook subscriptions. Nothing else.
How to use it
Setup takes a few minutes and needs no keys in a config file.
- Add the connector. In Claude, ChatGPT, Cursor or Codex, add a custom or remote MCP connector pointing at https://mcp.facebook.com/devtools. The server uses Streamable HTTP.
- Sign in with OAuth. Authenticate with your existing Meta developer account and approve either the read scope or, if you want webhook management, the manage scope for a specific app. No App ID or App Secret is copied anywhere.
- Start with your apps. Ask the assistant to list your apps, then work from there. It is in a gradual beta, so access is rolling out over time.
Useful things to ask once it is connected:
- List the Meta apps I can access and my permission level on each.
- What is the App Review status of my app and what do I still need to submit?
- Are there any compliance actions or Data Access renewal deadlines I am about to miss?
- Show my current Graph API rate limits and any deprecations affecting my app.
- Help me set up a WhatsApp Business integration. Which Graph API endpoints and permissions do I need?
- Subscribe my app to the messages webhook topic and send a test payload.
Where it stops: it builds the integration, it does not run the messaging
Notice the shape of that last pair of prompts. The Meta Developer Tools MCP is brilliant at helping you set up and monitor a WhatsApp Business integration. It points you at the right endpoints, tells you which permissions to request, tracks your App Review, then wires up and tests your webhooks. That is real. It removes a lot of dashboard busywork.
But look at what it explicitly cannot do. By Meta’s own description, it cannot submit App Review, cannot change app settings, cannot manage campaigns or ads and cannot alter any configuration beyond webhooks. And most importantly for anyone with a customer list: it never sends a WhatsApp message, never holds a contact, never manages a template and never runs a campaign.
That is not a gap in the product. It is the point of the product. The Developer Tools MCP is for building and maintaining the app. Sending messages to your customers is a completely different job that lives on the WhatsApp Business API.
Running WhatsApp Business is a different job
Once your integration is live, the actual work begins. None of it is something the Developer Tools MCP touches. A single real broadcast needs:
- A managed audience of contacts with tags, countries and custom fields you can segment on the fly.
- Approved, personalized templateswhere placeholders map to the right contact fields, not to Meta’s sample values.
- Consent and opt-out handlingthat protects your number’s quality rating.
- Throttling and quality management so you are not flagged for firing messages as fast as the API accepts them.
- Scheduling and follow-up sequences, because real campaigns are send now, then follow up in two days with everyone who did not reply.
- Delivery and read analytics summarized so you can ask how a campaign did and get a straight answer.
You could hand-code all of this against the raw WhatsApp Business API. Most people running a business would rather it already existed and worked from the assistant they already use.
Where DripRaven fits
DripRaven is the operational layer the Developer Tools MCP is not. It is a WhatsApp MCP serverthat runs on the official WhatsApp Business API. Where Meta’s MCP helps you build the app, DripRaven lets your assistant run the messaging on top of it.
Connected to DripRaven, your assistant can:
- Manage the audience. Add, update and import contacts, then build live segments from tags, countries and custom fields by describing them.
- Handle templates properly. List, create, sync and update WhatsApp templates, set the variable mapping so personalization fills from your contact fields, then preview a broadcast before anything sends.
- Run broadcasts safely. Send through the official WhatsApp Business API with approved templates, on your own connected number.
- Schedule and drip. Send now or later, then chain messages into multi-step sequences that follow up automatically after a launch.
- Report back. Ask how a campaign performed and get sent, delivered and read numbers in plain language.
And because DripRaven speaks MCP, the same campaigns run from Claude, ChatGPT, Antigravity and any other MCP-capable assistant. You connect your own WhatsApp Business number once. Your message costs are billed to you by Meta directly.
Meta Developer Tools MCP and DripRaven, side by side
| Task | Meta Developer Tools MCP | DripRaven |
|---|---|---|
| Inspect app settings and permissions | Yes | Not its job |
| Check App Review status | Yes | Not its job |
| Monitor Graph API rate limits and deprecations | Yes | Not its job |
| Manage webhook subscriptions | Yes, manage scope | Handled for you |
| Search Meta developer documentation | Yes | Not its job |
| Send a WhatsApp broadcast via the Business API | No | Yes |
| Manage contacts and live segments | No | Yes |
| Approve and personalize templates | No | Yes |
| Schedule and drip sequences | No | Yes |
| Delivery and read analytics in plain language | No | Yes |
| Who it is for | Developers building and maintaining an app | Anyone running WhatsApp campaigns |
Frequently asked questions
What is the Meta Developer Tools MCP?
It is Meta’s official Model Context Protocol server for developers, announced in mid 2026. It lets an AI assistant like Claude, ChatGPT or Cursor read your Meta app configuration, App Review status, compliance actions, rate limits and webhook subscriptions. It can also create and delete webhook subscriptions, without you opening the Meta for Developers dashboard.
How do I connect the Meta Developer Tools MCP?
It is a hosted remote server at https://mcp.facebook.com/devtools that uses OAuth. Add it as a custom or remote connector in Claude, ChatGPT, Cursor or Codex, sign in with your existing Meta developer account and approve the read or manage scope. There is no App ID or App Secret to copy into a config file. It is in a gradual beta rollout.
Can the Meta Developer Tools MCP send WhatsApp messages?
No. It is a developer tool for inspecting and monitoring your app and managing webhooks. It never sends a WhatsApp message, holds a contact list, manages templates or runs a campaign. It can help you set up and monitor a WhatsApp Business integration, but it cannot operate your messaging.
How do I actually run WhatsApp Business campaigns from my assistant?
Connect an operational layer that sends through the WhatsApp Business API. DripRaven is MCP-native and lets your assistant manage contacts and segments, approve and personalize templates, send and schedule broadcasts, run drip sequences and report delivery and read rates, all in plain language.
Do the Meta Developer Tools MCP and DripRaven overlap?
No, they are complementary. The Meta Developer Tools MCP helps a developer build and maintain the app behind your WhatsApp integration. DripRaven runs the messaging on top of the WhatsApp Business API once that integration is live. One is for building, the other is for operating.
The takeaway
The Meta Developer Tools MCP is a real and welcome step. It brings your app settings, App Review, compliance, rate limits and webhooks into the assistant you already code in. It can even point you at the right pieces to build a WhatsApp Business integration. Use it for exactly that.
Just do not expect it to run your messaging, because that was never its job. Meta ships the platform and the developer tooling around it. The layer that turns the WhatsApp Business API into campaigns you can run by chat, contacts, templates, broadcasts, schedules and analytics, is what DripRaven builds.
Related reading
- The WhatsApp MCP server for AI agents
- Send a WhatsApp broadcast by chat
- Run WhatsApp from Claude
- Run WhatsApp from ChatGPT
- All DripRaven integrations
Run your WhatsApp campaigns from the assistant you already use
The Meta Developer Tools MCP helps you build the integration. DripRaven runs the messaging on top of it. Connect your WhatsApp Business number once, then send, segment and follow up in plain language.