Overview
Connect Meta Ads by providing a Meta access token. Mistle uses the token to route the bundled Meta Ads CLI and MCP server through the Meta Marketing API. This integration is a thin wrapper around Meta’s APIs. The token’s Meta app, business, user, system-user, and ad-account permissions determine what agents can read or change. Mistle does not grant, inspect, or enforce Meta permissions beyond storing the token for the connection and routing tool traffic through managed egress.Configuring Meta Access
Before creating the connection, make sure:- You have access to the Meta business, app, user, or system user that owns the token.
- The token is allowed to access the ad accounts and Marketing API operations you want agents to use.
- Write permissions are granted in Meta when agents should create, update, or delete Meta Ads resources.
Connect In Mistle
Open Integrations in the dashboard, choose Meta Ads, then select Access token. Enter:| Field | Value |
|---|---|
| Access token | Meta access token |
Using The Tools
After the connection is added to a sandbox profile, agents can use:- the Meta Ads CLI for named commands and raw Graph API requests
- the Meta Ads MCP server for discoverable tool calls
Self-Hosted Target Config
Self-hosted deployments can enablemetaads-default with an empty config:
v25.0. Operators can set graph_api_version when a deployment must pin a different supported Meta Graph API version: