Skip to main content
Meta Ads is a Dev Testing integration. Meta hosts the Ads MCP server and OAuth flow. daoco supplies its fixed Meta App ID for this custom-platform connection, so workspace users do not enter client IDs, secrets, endpoints, or scopes. Before Connect is enabled, a daoco operator must add Meta’s Create & manage ads with ads MCP server use case to the existing daoco Meta app, register the tenant MCP callback in Facebook Login for Business, and configure that app as FACEBOOK_CLIENT_ID. Meta Ads intentionally shares this app identity with daoco’s existing Meta integrations; a separate MCP_META_ADS_CLIENT_ID is not used. Meta’s hosted MCP does not require the app secret.

​
Connect Meta Ads

1

Enable Dev Testing

A workspace owner or admin must enable Dev Testing integrations in Settings -> Preview features.
2

Open the Meta Ads card

In daoco, open Connections -> Integrations -> Dev Testing and choose Meta Ads.
3

Choose Connect

Choose Connect. A Meta authorization window opens immediately; there is no workspace configuration form.
4

Approve account access

Sign in with a Meta user who can access the Business or ad account and approve the permissions requested by Meta’s hosted server.
5

Verify from chat

Ask /integration for an ad-account list, campaign list, or performance report before requesting an approved write.
Meta’s hosted server includes write tools. daoco requires approval for consequential changes, and Meta separately enforces the AI-agent capability rules configured for each ad account and catalog. Some accounts may not have every tool yet.