Connect Meta Ads
Manage Meta advertising through a Meta-hosted MCP server: reporting, campaigns, catalogs, signals, experiments and activity logs, subject to the authorizing account’s permissions.
Setup evidence reviewed 2026-11-12. Documentation review does not establish a successful connection.
Credentials and permissions
Use OAuth, a user access token, or an Employee-role system user access token. Admin-role system user tokens are not supported. Tokens require ads_mcp_management plus ads_read or ads_management. Additional tools may require catalog_management, business_management, pages_show_list or instagram_basic. Request only the permissions your workflow needs.
Set up your connection
1. Choose your access path. A Meta developer app is not mandatory: Meta links a separate no-app setup guide at https://www.facebook.com/business/help/1456422242197840. The following steps cover using your own Meta app. 2. Create or reuse a Meta developer app at https://developers.facebook.com/apps and add the “Create & manage ads with ads MCP server” use case. For OAuth, configure your MCP client’s redirect URL in Facebook Login for Business. 3. In Claude Code, replace META_APP_ID with your app ID and run: claude mcp add --transport http --client-id META_APP_ID meta-ads https://mcp.facebook.com/ads Complete the client’s OAuth flow and approve the requested permissions using your Facebook account or Meta Managed Account. 4. For programmatic access, obtain a user token through Graph API Explorer or your own OAuth flow, or generate an Employee-role system user token. Include the required permissions and send it in the Authorization: Bearer ACCESS_TOKEN header. Keep the real token in your client’s secret storage. 5. Start with a read-only request such as “List my ad accounts.” Check that the expected account is accessible before requesting campaign changes. The server also exposes write operations; review the target account and proposed changes before approving them. If authentication fails, check the Meta app use case, the client redirect URL, token permissions and system-user role. An unauthenticated initialize returned HTTP 401 with OAuth resource metadata on 2026-11-12. This confirms an authentication challenge, not a successful login or tool execution.
Server endpoint
https://mcp.facebook.com/adsTransport: Streamable HTTP
Publisher documentation
Check these sources for current account requirements and client support before connecting.