facebook-ads-mcp-server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor exact implementation activity, MCP interface, permission and setup changes.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Meta/Facebook advertising analytics and account management

What we know

facebook-ads-mcp-server — MCP integration. Specific capability not verified. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Maintenance / activity evidence

GitHub exact repo pushed_at 2026-08-05T09:45:30Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Meta Ads token can expose sensitive ad metrics and, with elevated scopes, campaign changes; confirm exact tool list. Reported action classes: campaign management, if exposed and authorized. Complete write authority is not verified.
Python 3.10+, pip dependencies and Meta token with ads_read scope
Sensitive access: Meta advertising account data and access token

Meta Ads token can expose sensitive ad metrics and, with elevated scopes, campaign changes; confirm exact tool list.
Public tracking suitability is not an installation safety audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

365 repository stars

Stars observed Oct 10, 2026.

Repository total for gomarble-ai/facebook-ads-mcp-server.

All limitations / Review context

Has facebook-ads-mcp-server changed its documented MCP interface, authentication or privilege boundaries, and does it merit promotion?

Limited editorial listing; known permission implications disclosed, no independently established publication blocker.

Meta Ads token can expose sensitive ad metrics and, with elevated scopes, campaign changes; confirm exact tool list.
Public tracking suitability is not an installation safety audit.
Python 3.10+, pip dependencies and Meta token with ads_read scope
Meta advertising account data and access token
Reviewed write actions: campaign management, if exposed and authorized
Sensitive access: Meta advertising account data and access token
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Upstream credential and permission scopes must be validated before runtime use.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Exact GitHub pushed_at 2026-08-05T09:45:30Z

Original activity observations

GitHub exact repo pushed_at 2026-08-05T09:45:30Z

Technical identity

github.com/gomarble-ai/facebook-ads-mcp-server

Exact implementation source: https://github.com/gomarble-ai/facebook-ads-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: gomarble-ai/facebook-ads-mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
gomarble-ai/facebook-ads-mcp-server
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Warning

API token on process arguments is sensitive; use vendor-supported safer deployment if available.
Meta Ads permissions and account access needed.
Exact vendor-specific credential revoke procedure not established from checked official Setup documentation; may be external or not applicable. Do not invent.
Authentication and credentials depend on a real account/deployment; documentation evidence is not a runtime verification.
Requires review of install side effects, credentials, remote scripts, or privileged application/database access before execution. Multiple publisher-documented README steps combined as an ordered excerpt; not a verbatim single publisher code block.
Replace the supplied credential/path placeholders privately; use only the named configuration schema.
Its sample puts Meta token in CLI args; warn about process listings and config exposure. Prefer Meta token with only ads_read for read-only use. GoMarble-assisted token creation is a third-party authentication flow.
The token shown on process arguments may have been exposed in local logs; do not delete advertising campaigns.
Publisher UI / connection instruction, not a shell command.
MCP100 client-scope note: this Claude Code CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
Connection / UI instruction · Publisher instructions · Review before use
```
Use official GoMarble installer at https://gomarble.ai/mcp, or clone gomarble-ai/facebook-ads-mcp-server and `pip install -r requirements.txt`.
```
Configure / authenticate
Publisher instructions
Meta Ads access token required; GoMarble installer can provision one. Follow publisher credential handling.
Advanced configuration · claude desktop json · Publisher instructions
claude desktop json · Publisher instructions
{ "mcpServers": { "fb-ads-mcp-server": { "args": [ "/ABSOLUTE/PATH/facebook-ads-mcp-server/server.py", "--fb-token", "YOUR_META_ACCESS_TOKEN" ], "command": "python" } } }
Check connection
Suggested check
Check account/campaign discovery read-only; do not create or alter campaigns to test.
Remove / uninstall / revoke
MCP100 setup guide
Remove MCP host registration and stop local Python server; separate Meta token management remains with Meta.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove fb-ads-mcp-server

Official Documentation & Sources

What it does

facebook-ads-mcp-server — MCP integration. Specific capability not verified. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Meta/Facebook advertising analytics and account management

Representative uses

Meta/Facebook advertising analytics and account management

Limitations

Meta Ads token can expose sensitive ad metrics and, with elevated scopes, campaign changes; confirm exact tool list.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Exact GitHub pushed_at 2026-08-05T09:45:30Z

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Python 3.10+, pip dependencies and Meta token with ads_read scope
Permissions: Meta Ads token can expose sensitive ad metrics and, with elevated scopes, campaign changes; confirm exact tool list.
Data handling: Meta advertising account data and access token
Cost: Provider or usage fees possible; verify current pricing
Risk and cautions: Meta Ads token can expose sensitive ad metrics and, with elevated scopes, campaign changes; confirm exact tool list.

Access scope and cautions

Write actions: Not verified campaign management, if exposed and authorized
Sensitive access: Meta advertising account data and access token
Risk level: high
Security notes: Meta Ads token can expose sensitive ad metrics and, with elevated scopes, campaign changes; confirm exact tool list. Public tracking suitability is not an installation safety audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T03:38:00Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Meta/Facebook advertising analytics and account management.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Installation command omitted unless verified or clearly package-specific; do not infer npx/uvx entrypoints. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Python 3.10+, pip dependencies and Meta token with ads_read scope

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: campaign management, if exposed and authorized. Recorded permission context: Meta Ads token can expose sensitive ad metrics and, with elevated scopes, campaign changes; confirm exact tool list.

What data-handling boundary should I consider?

Meta advertising account data and access token Recorded sensitive-access context: Meta advertising account data and access token.

What limitations and risks should I check before use?

Meta Ads token can expose sensitive ad metrics and, with elevated scopes, campaign changes; confirm exact tool list. Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted. Exact GitHub pushed_at 2026-08-05T09:45:30Z. Public tracking suitability is not an installation safety audit. Upstream credential and permission scopes must be validated before runtime use.