AdAdvisor MCP Server

The materials explicitly state that no keys or environment variables are required. No user-supplied API key, OAuth token, or other highly sensitive local credential is disclosed as necessary, so the direct credential exposure surface appears low.

The tool connects to the remote endpoint api.adadvisor.ai. Its stated purpose is to query ad accounts, campaigns, ad sets, ads, metrics, and settings, which implies relevant business data may be sent to that service for processing; this egress is consistent with the stated function but is still a data-externalization scenario.

The system flags this tool as having code-execution capability, indicating it runs a local service/process. However, the materials do not show requests for system privileges beyond normal MCP operation, nor do they reveal execution behavior clearly unrelated to its stated purpose.

By description, it can access Meta Ads business data including accounts, campaigns, ad sets, ads, metrics, and settings. That scope is aligned with its core function. The materials do not state that it reads/writes local files or requests extra resource permissions, so this currently looks like normal business-data access, though the exact least-privilege boundary is not transparent.

Positive signals include distribution via an official registry, an official-source flag, and updates within the last year. However, there is no open-source repository, no declared license, no README, and 0 community stars, which limits source/dependency auditability and weakens community validation. Source credibility lowers the risk, but the lack of transparency still warrants caution.