MCP Tools DirectoryAbout this integration
MCP server for Meta Marketing API — Facebook & Instagram ad campaign management
- Transport
- stdio
- Authentication
- oauth
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.2.1
- Package
- @mikusnuz/meta-ads-mcp
- Last compatibility test
- Not independently tested
Connect your agent
@mikusnuz/meta-ads-mcpPublisher README and npm manifest were reviewed from hash-pinned captures. This is documented, not runtime-tested. The tool surface includes operations that can create, update, or delete advertising and business resources and therefore requires least-privilege tokens and caller-side confirmation.
Capabilities: Manage Meta campaigns, ad sets, ads, creatives, and media, Read advertising insights and asynchronous reports, Manage audiences, catalogs, automated rules, and experiments, Inspect and manage documented account and business resources
Connected profiles
Additional details
io.github.mikusnuz/meta-ads
Source ↗ · Checked 2026-09-171.2.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17META_ADS_ACCESS_TOKEN
Source ↗ · Checked 2026-09-17@mikusnuz/meta-ads-mcp
Source ↗ · Checked 2026-09-191.4.1
Source ↗ · Checked 2026-09-19Publisher documentation supplies an MCP client command and environment configuration for unattended startup of the npm executable; the package was not executed during review.
Source ↗ · Checked 2026-09-19The server requires a Meta Marketing API access token and ad account ID; additional app, business, and pixel identifiers are optional or tool-specific.
Source ↗ · Checked 2026-09-19The publisher's MCP client configuration launches the reviewed npm artifact through a local npx command, matching the preserved stdio listing connection.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19