What can I do with this?
Facebook is one of the most efficient ways to advertise online. See how we connect businesses with all the right people on any device with Facebook marketing.
Facebook is one of the most efficient ways to advertise online. See how we connect businesses with all the right people on any device with Facebook marketing.
Facebook is one of the most efficient ways to advertise online. See how we connect businesses with all the right people on any device with Facebook marketing.
Authentication and permission requirements have not been reviewed here. Check the provider documentation for the required keys, OAuth scopes and account access before sending a request.
Check provider documentation ↗Account-free API calls have not been verified for this profile. You can inspect specifications and prepare requests in the explorer without running them.
Requests run only when you choose to send them. Browser access depends on the provider’s CORS policy.
https://mcp.facebook.com/ads1. 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.
Documentation reviewed · Connection not runtime-tested.
These are the details currently listed in our catalog. Omitted fields are unknown, not necessarily unsupported. Confirm current requirements in the provider’s documentation.
Facebook is one of the most efficient ways to advertise online. See how we connect businesses with all the right people on any device with Facebook marketing.
Use the linked Facebook Ads provider documentation to check setup and supported capabilities.
Read documentationManage Meta advertising through a Meta-hosted MCP server: reporting, campaigns, catalogs, signals, experiments and activity logs, subject to the authorizing account’s permissions. Supported operations are limited to those exposed by this implementation. Publisher evidence reviewed 2026-11-12. This review does not establish a working connection.
View publisher evidenceStreamable HTTP. 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. 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. Documentation reviewed 2026-11-12; not runtime-tested.
Read connection instructionsAPI Tracker summarizes available catalog information. Missing fields mean we have not established those details; they do not mean a feature is unsupported. Confirm current requirements with the provider.
Read our methodologyWe don't have videos for this API yet. Get in touch to suggest profile updates.
We don't have tips for this API yet. Get in touch if you want to submit a tip.
Share the profile or add a listing badge to your website. Sharing is optional and does not affect placement or verification.
A directory listing, not a certification or Official MCP badge.