Meta Ads MCP Server (JSKIM)
Meta Marketing API campaigns, audiences, and ad insights via 135 dedicated management tools.
Data last scanned today · Reviewed today
Overview
This server provides extensive integration with the Meta Marketing API v25.0, enabling programmatic control over Facebook and Instagram advertising workflows. It exposes 135 individual tools designed to handle full-funnel ad management, from creating campaigns and ad sets to uploading creative assets for carousel ads. Beyond basic campaign management, the tool supports advanced operations such as custom and lookalike audience generation, dynamic product catalog management, and automated rule creation based on CPA or ROAS performance thresholds. Users can also pull performance reports, search the public ad library, or run controlled A/B experiments.
Our verdict
With a security score of 24/100, this server carries a high risk level. It lacks a read-only mode, meaning any connected instance grants full write access to your advertising account via the Meta Marketing API. Furthermore, as a community-maintained project that has not been editorially reviewed and relies on a single contributor, users should exercise caution before deploying this in environments where accidental ad spend changes could have significant financial consequences.
- Supports 135 distinct operations for comprehensive Meta ad management
- Lightweight codebase with only two direct dependencies
- MIT license allows for transparent modification and usage
- Includes real, documented tool descriptions for complex API workflows
- High security risk due to lack of read-only operating mode
- Community-maintained with no official support from Meta
- Single contributor increases the bus-factor risk profile
Setup
{
"mcpServers": {
"mikusnuz-meta-ads-mcp": {
"args": [
"-y",
"@mikusnuz/meta-ads-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| list_campaigns | List campaigns with filtering and pagination | low |
| get_campaign | Get campaign details by ID | low |
| create_campaign | Create a new campaign | medium |
| update_campaign | Update campaign settings | medium |
| delete_campaign | Delete a campaign | high |
| copy_campaign | Copy an existing campaign with ad sets and ads | medium |
| get_campaign_adsets | List ad sets within a campaign | low |
| get_campaign_ads | List ads within a campaign | low |
| get_campaign_leads | Get leads from a campaign | low |
| list_adsets | List ad sets with filtering | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Which Meta Marketing API version does this server use?
This MCP server is built for version 25.0 of the Meta Marketing API.
›Which environment variables are mandatory for operation?
You must provide a valid META_ADS_ACCESS_TOKEN and a numeric META_AD_ACCOUNT_ID, which should not include the 'act_' prefix.
›Are specific Meta IDs required to use business or conversion tools?
Yes, you must provide a META_BUSINESS_ID to use business tools and a META_PIXEL_ID to use conversion-related tools.
›How should I handle large date ranges when generating reports?
For large date ranges, you should use the create_async_report tool to initiate the process and then retrieve the results using get_async_report.
›Are App ID and App Secret required for all operations?
No, they are optional but are required if you need to perform token exchange or debugging tasks.
Badge
Maintain this server? Add the live badge to your README.