@cesteral/meta-mcp

MCPattested
v1.3.0UnknownApache-2.0Updated 2mo agonpmGitHub

Meta Ads MCP Server - Campaign entity management and reporting via the configured Meta Graph API (default: v25.0)

Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
241Downloads/wk
2mo agoLast update
Package
AuthorUnknown
LicenseApache-2.0
Version1.3.0
Sourcenpm+mcp-registry
npm@cesteral/meta-mcp
GitHubcesteral/mcp-open-advertising
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 2128234
Dependencies60 resolved · 2 with advisories
Tool surface21 tools · 1 privileged
Security scan⚠ Warnings (2)v1.3.0 · todayHow well does this scan work?
HIGH@opentelemetry/auto-instrumentations-node@0.67.3Prometheus exporter process crash via malformed HTTP request · transitiveHIGH@opentelemetry/sdk-node@0.208.0Prometheus exporter process crash via malformed HTTP request · transitive
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

21 tools · 1 privileged
Statically extracted from the published packagev1.3.0 · 10h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

meta_bulk_operations_workflowStep-by-step guide for Meta Ads bulk operations: batch create entities, batch update entities, batch status changes, and batch bid adjustments. Covers partial failure handling and verification.

Step-by-step guide for Meta Ads bulk operations: batch create entities, batch update entities, batch status changes, and batch bid adjustments. Covers partial failure handling and verification.

No input schema was published for this tool.

adAccountIdMeta Ad Account ID (e.g., act_123456789)

Meta Ad Account ID (e.g., act_123456789)

No input schema was published for this tool.

operationOperation type: 'create', 'update', 'status', or 'bids' (default: status)

Operation type: 'create', 'update', 'status', or 'bids' (default: status)

No input schema was published for this tool.

meta_campaign_setup_workflowStep-by-step guide for creating a complete Meta Ads campaign structure (Campaign > Ad Set > Ad Creative > Ad)

Step-by-step guide for creating a complete Meta Ads campaign structure (Campaign > Ad Set > Ad Creative > Ad)

No input schema was published for this tool.

creative_upload_workflowprivilegedStep-by-step guide for uploading creative assets and creating Meta Ads creatives (images and videos)

Step-by-step guide for uploading creative assets and creating Meta Ads creatives (images and videos)

No input schema was published for this tool.

creativeTypeType of creative to create: image or video

Type of creative to create: image or video

No input schema was published for this tool.

cross_platform_campaign_setupGuide for setting up a coordinated multi-platform campaign across DV360 (dv360-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), Meta Ads (meta-mcp), LinkedIn (linkedin-mcp), TikTok (tiktok-mcp), Pinterest (pinterest-mcp), Snapchat (snapchat-mcp), and Amazon DSP (amazon-dsp-mcp). Covers platfo…

Guide for setting up a coordinated multi-platform campaign across DV360 (dv360-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), Meta Ads (meta-mcp), LinkedIn (linkedin-mcp), TikTok (tiktok-mcp), Pinterest (pinterest-mcp), Snapchat (snapchat-mcp), and Amazon DSP (amazon-dsp-mcp). Covers platfo…

No input schema was published for this tool.

totalBudgetTotal campaign budget across all platforms (e.g., '50000' for $50,000)

Total campaign budget across all platforms (e.g., '50000' for $50,000)

No input schema was published for this tool.

objectiveCampaign objective: 'awareness', 'consideration', or 'conversion' (default: conversion)

Campaign objective: 'awareness', 'consideration', or 'conversion' (default: conversion)

No input schema was published for this tool.

cross_platform_performance_comparisonGuide for comparing campaign performance across DV360 (via dbm-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), and Meta Ads (meta-mcp). Normalizes metrics, identifies top performers, and recommends budget reallocation.

Guide for comparing campaign performance across DV360 (via dbm-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), and Meta Ads (meta-mcp). Normalizes metrics, identifies top performers, and recommends budget reallocation.

No input schema was published for this tool.

dateRangeDate range for comparison (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom YYYY-MM-DD format)

Date range for comparison (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom YYYY-MM-DD format)

No input schema was published for this tool.

meta_entity_duplication_workflowStep-by-step guide for duplicating Meta Ads campaigns, ad sets, and ads using meta_duplicate_entity — covers A/B testing, scaling, and common patterns.

Step-by-step guide for duplicating Meta Ads campaigns, ad sets, and ads using meta_duplicate_entity — covers A/B testing, scaling, and common patterns.

No input schema was published for this tool.

entityTypeEntity type to duplicate: campaign, adSet, or ad

Entity type to duplicate: campaign, adSet, or ad

No input schema was published for this tool.

entityIdID of the entity to duplicate

ID of the entity to duplicate

No input schema was published for this tool.

meta_entity_update_workflowStep-by-step guide for safely updating Meta Ads entities: fetch current state, build partial update payload, execute update, and verify changes. Covers campaigns, ad sets, ads, ad creatives, and custom audiences.

Step-by-step guide for safely updating Meta Ads entities: fetch current state, build partial update payload, execute update, and verify changes. Covers campaigns, ad sets, ads, ad creatives, and custom audiences.

No input schema was published for this tool.

meta_insights_reporting_workflowGuide for querying Meta Ads performance insights with breakdowns and attribution

Guide for querying Meta Ads performance insights with breakdowns and attribution

No input schema was published for this tool.

entityLevelReporting level: account, campaign, adset, ad

Reporting level: account, campaign, adset, ad

No input schema was published for this tool.

meta_targeting_discovery_workflowStep-by-step guide for researching Meta Ads audiences: search interests, browse categories, build targeting specs, and estimate reach before ad set creation.

Step-by-step guide for researching Meta Ads audiences: search interests, browse categories, build targeting specs, and estimate reach before ad set creation.

No input schema was published for this tool.

goalResearch goal: 'interests' (search by keyword), 'categories' (browse available options), or 'build' (assemble targeting spec). Default: interests

Research goal: 'interests' (search by keyword), 'categories' (browse available options), or 'build' (assemble targeting spec). Default: interests

No input schema was published for this tool.

meta_tool_schema_explorationGuide for discovering and understanding Meta MCP tools, resources, and schemas

Guide for discovering and understanding Meta MCP tools, resources, and schemas

No input schema was published for this tool.

meta_troubleshoot_entityDiagnostic workflow for troubleshooting Meta Ads entity issues

Diagnostic workflow for troubleshooting Meta Ads entity issues

No input schema was published for this tool.

21 of 21 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Meta Ads MCP Server - Campaign entity management and reporting via the configured Meta Graph API (default: v25.0)

Keywords
mcpmodel-context-protocoladvertisingmeta-adsfacebook-ads
Alternatives
Comparing tool surfaces…

Tools exposed

21 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-29 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · 2 carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

167 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+155 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.