Meta Ads MCP (official, remote)
Score = points from 5 automated checks. Not a quality or security rating. Methodology
- Install20/20
- Handshake5/30
- Maintenance25/25
- Docs15/15
- License0/10
Vendor-hosted
Official Meta-hosted ads MCP server (open beta announced 2026-04-29). Listed under the vendor-hosted rule (Our review, Oct 24, 2026).
Sources: https://developers.facebook.com/documentation/ads-commerce/ads-ai-connectors/ads-mcp-server/ads-mcp-server-overview · https://developers.facebook.com/documentation/ads-commerce/ads-ai-connectors/ads-mcp-server/ads-mcp-server-get-started · https://developers.facebook.com/blog/post/2026/07/16/meta-ads-mcp-server/ · https://www.facebook.com/business/news/advertising-week-new-york-2026
Transport: Needs credentials to confirm transport · probed 2026-10-28 without credentials
Score 65/100 · Tools — · Token cost — · Compare · Last tested 2026-10-26 · Server version not reported · Remote endpoint https://mcp.facebook.com/ads (streamable-http)
Summary: Meta Ads MCP (official, remote) requires credentials or a backing service before it will list tools.
Evidence summary
- Handshake
- auth-gated
- Tools listed
- —
- Context cost
- Not measured ranking
- Login
- Needs OAuth sign-in
- Tested
- 2026-10-26
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | Endpoint https://mcp.facebook.com/ads reachable over streamable-http (HTTP 401) in 0.1s; no install step for remote servers. |
| handshake | auth-gated | 5 | Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.facebook.com/.well-known/oauth-protected-resource/ads; metadata lists authorization server https://www.facebook.com/ads). We do not sign in; not counted as working until a credentialed test exists. |
| maintenance | pass | 25 | Vendor-hosted rule: scored from vendor release note 2026-10-06 (https://www.facebook.com/business/news/advertising-week-new-york-2026), 20 days before test. Registry: Not found in the official MCP registry (search 'facebook' and 'meta' on 2026-10-26; only third-party Meta Ads servers and io.github.facebook/devtools, a different endpoint). |
| docs | pass | 15 | official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://developers.facebook.com/documentation/ads-commerce/ads-ai-connectors/ads-mcp-server/ads-mcp-server-overview, https://developers.facebook.com/documentation/ads-commerce/ads-ai-connectors/ads-mcp-server/ads-mcp-server-get-started). |
| license | fail | 0 | Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source). |
Local-model readiness
Not yet tested (no tools/list response without credentials).
What we tested and what we didn't
Tested on 2026-10-26
- We attempted an MCP initialize to the vendor's hosted endpoint with no credentials and got HTTP 401, so we never reached the tool list (Method details:
initializePOST answered 401;tools/listnot sent) - Auth response: HTTP 401, WWW-Authenticate resource_metadata https://mcp.facebook.com/.well-known/oauth-protected-resource/ads, OAuth metadata lists authorization server https://www.facebook.com/ads. Login is an OAuth sign-in; we did not sign in
- Vendor docs: official MCP docs page; states the endpoint URL; client setup instructions (15/15)
- Maintenance: dated vendor source, vendor release note 2026-10-06 (25/25)
- License: a hosted service has no license to cite (0/10)
Not tested
- Security: not audited (hosted service; no code to review, no permission or data-flow analysis)
- Behaviour after signing in, or with a real account
- Source code, repository activity or an open-source license (none published for the hosted service)
- Performance, rate limits or load
- Real tasks (no functional task runs yet)
Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that it is safe to give it access to your data.
Known security issues
Not checked (remote-only): hosted endpoint, version unknown.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
No tool list: this server did not list tools without credentials in our test, so tool changes are not tracked.
Raw test record (JSON)
{
"name": "meta-ads-remote",
"version": null,
"registry": "remote",
"status": "auth-gated",
"tested": "2026-10-26",
"tools_count": null,
"tools_schema_tokens_est": null,
"deprecated": false,
"archived": null,
"tests": {
"install": [
"pass",
20,
"Endpoint https://mcp.facebook.com/ads reachable over streamable-http (HTTP 401) in 0.1s; no install step for remote servers."
],
"handshake": [
"auth-gated",
5,
"Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.facebook.com/.well-known/oauth-protected-resource/ads; metadata lists authorization server https://www.facebook.com/ads). We do not sign in; not counted as working until a credentialed test exists."
],
"maintenance": [
"pass",
25,
"Vendor-hosted rule: scored from vendor release note 2026-10-06 (https://www.facebook.com/business/news/advertising-week-new-york-2026), 20 days before test. Registry: Not found in the official MCP registry (search 'facebook' and 'meta' on 2026-10-26; only third-party Meta Ads servers and io.github.facebook/devtools, a different endpoint)."
],
"docs": [
"pass",
15,
"official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://developers.facebook.com/documentation/ads-commerce/ads-ai-connectors/ads-mcp-server/ads-mcp-server-overview, https://developers.facebook.com/documentation/ads-commerce/ads-ai-connectors/ads-mcp-server/ads-mcp-server-get-started)."
],
"license": [
"fail",
0,
"Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
]
}
}Install
https://mcp.facebook.com/ads
Tools listed
Not available (handshake did not complete without credentials).
Quick config
{
"mcpServers": {
"meta-ads-mcp-official-remote": {
"type": "http",
"url": "https://mcp.facebook.com/ads"
}
}
}Add to config Opens the config generator with this server selected.
Setup
Without credentials it said (verbatim): Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.facebook.com/.well-known/oauth-protected-resource/ads; metadata lists authorization server https://www.facebook.com/ads). We do not sign in; not counted as working until a credentialed test exists.
- Install. No install step: it is a remote server at https://mcp.facebook.com/ads.
- Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools. In our test it did not list tools without credentials.
{
"mcpServers": {
"meta-ads-mcp-official-remote": {
"type": "http",
"url": "https://mcp.facebook.com/ads"
}
}
}Not tested with credentials We have not tested this with real credentials.
Test history
No dated events yet.
Related: MCP servers that need an OAuth sign-in · How to secure AI API keys
FAQ
Is Meta Ads MCP (official, remote) deprecated?
No. meta-ads-remote was not deprecated or archived when we last tested it on 2026-10-26.
What replaces Meta Ads MCP (official, remote)?
Nothing; Meta Ads MCP (official, remote) is not deprecated as of 2026-10-26.
Does Meta Ads MCP (official, remote) need an API key?
Not an API key: it needs an OAuth sign-in. Without signing in, the endpoint returned HTTP 401 with an OAuth challenge and did not list tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.