Home / MCP registry index / io.github.mcp-dir/meta_ads-mcp

Meta Ads (Facebook & Instagram)

io.github.mcp-dir/meta_ads-mcp in the official MCP registry. Endpoint https://api.mcp.ai/p_meta_ads. Source: github.com/mcp-dir/meta_ads-mcp.

The registry describes it as: Read and manage Meta Ads campaigns, ad sets, ads, audiences, pages and Business Manager. You provide

We read its 44 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http meta-ads-mcp https://api.mcp.ai/p_meta_ads

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "meta-ads-mcp": {
      "url": "https://api.mcp.ai/p_meta_ads"
    }
  }
}

VS Code

code --add-mcp '{"name":"meta-ads-mcp","type":"http","url":"https://api.mcp.ai/p_meta_ads"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

meta_ads_list_accounts meta_ads_status meta_ads_campaigns meta_ads_today meta_ads_roas meta_ads_ads meta_ads_realtime meta_ads_adset_detail meta_ads_pages_list meta_ads_pages_insights meta_ads_pages_posts meta_ads_pages_post_insights meta_ads_business_list meta_ads_business_accounts meta_ads_business_pages meta_ads_business_users meta_ads_business_pixels meta_ads_media_list_images meta_ads_media_list_videos meta_ads_audience meta_ads_campaign_write_create meta_ads_campaign_write_update meta_ads_campaign_write_pause meta_ads_campaign_write_activate meta_ads_campaign_delete meta_ads_adset_write_create meta_ads_adset_write_update meta_ads_adset_delete meta_ads_creative_write_create_creative meta_ads_creative_write_create_ad meta_ads_creative_write_update_ad meta_ads_creative_delete meta_ads_media_write_upload_image meta_ads_media_write_upload_video meta_ads_media_write_get_upload_command meta_ads_audience_write_create meta_ads_audience_write_add_users meta_ads_audience_delete show_version report_bug connect toolkit_info marketplace authenticate

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-meta-ads-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-meta-ads-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Social media MCP servers