Meta Ads MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| META_ADS_ENV_FILE | No | Path to the env file containing the Meta Ads settings. If not set, the server checks $XDG_CONFIG_HOME/meta-ads/meta-ads.env, then ~/.config/meta-ads/meta-ads.env. | |
| META_ADS_ACCOUNT_ID | Yes | The ad account ID, with or without the act_ prefix. | |
| META_ADS_API_VERSION | No | Optional. The Graph API version. The default is v23.0. | v23.0 |
| META_ADS_ACCESS_TOKEN | Yes | The Meta access token for the ad account. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Meta Marketing API for one configured ad account: campaigns, ad sets, ads, creatives, insights, and Instagram media. Read tools are safe. Every write spends or can spend real money. Before EVERY create, update, copy, status change, or deletion, show the exact change, including budget in account currency, targeting, placements, and status, and obtain explicit user confirmation in the current request. New and copied objects are always PAUSED. Setting ACTIVE needs its own confirmation after the user reviewed the paused object. Budgets are in the minor currency unit. Set user_confirmed only for a specifically approved action; it is not blanket permission. Load the meta-ads skill for campaign recipes.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Check the Meta access token, its permissions and expiry, and the configured ad account. |
| listA | List one edge of the ad account or of another object. Examples: campaigns of the account, ads of a campaign, media or stories of an Instagram account. |
| getA | Get one campaign, ad set, ad, creative, or other object by ID. |
| insightsC | Get performance insights for the ad account, a campaign, an ad set, or an ad. |
| targeting_searchC | Search targeting options: interests, locations, locales, or categories. |
| createA | Create a campaign, ad set, creative, or ad in the configured ad account. Campaigns, ad sets, and ads are always created PAUSED. Requires explicit user confirmation. |
| updateA | Update fields of a campaign, ad set, or ad, for example budget, targeting, or name. Does not change status; use set_status. Requires explicit user confirmation. |
| set_statusA | Set a campaign, ad set, or ad to ACTIVE, PAUSED, or ARCHIVED. ACTIVE starts ad spend and needs its own explicit confirmation after the user reviewed the object. |
| copyA | Copy a campaign, ad set, or ad. The copy is always PAUSED. Requires explicit user confirmation. |
| deleteA | Delete a campaign, ad set, ad, or creative. Requires explicit confirmation of this exact deletion. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes: auth_status, insights, targeting_search, copy, and set_status are unambiguous, and update is explicitly separated from set_status. The generic list/get/create/update/delete verbs operate across several object types, so boundaries are mostly clear from descriptions but not as crisp as a fully specific set.
The set mixes bare imperative verbs (list, get, create, update, copy, delete), noun-style tools (insights), and compound snake_case names (auth_status, targeting_search, set_status). It is readable and all snake_case-compatible, but there is no single predictable naming pattern throughout.
Ten tools is well-scoped for a Meta Ads management server, covering authentication, reads, writes, status changes, copying, deletion, targeting lookup, and insights without excessive surface area. Each tool appears to earn its place.
The surface covers the core campaign, ad set, ad, and creative lifecycle plus insights, targeting, and auth, so it is largely complete for the stated purpose. Minor gaps exist, such as updating creative fields explicitly and preview/review or bulk/reporting operations, but agents can work around most of them.