Skip to main content
mcpSource-backedReview first Safety Privacy

AdAdvisor MCP Server for Claude

Hosted AdAdvisor MCP server with curated Meta Ads workflows for browsing creatives, launching campaigns, building audiences, and optimizing performance from Claude via streamable HTTP.

HarnessClaude CodeCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • Workflow tools can create or modify Meta Ads campaigns, ad sets, creatives, and audiences when your token has write scope.
  • Bearer tokens grant persistent account access until revoked in AdAdvisor or Meta Business settings.
  • Treat returned spend, conversion, and audience data as business-sensitive before sharing in chat exports.
  • Verify AI-proposed budget or targeting changes before approving tool calls on live ad accounts.

Privacy notes

  • Account IDs, campaign names, creative assets, and performance metrics are sent to AdAdvisor and Meta APIs.
  • Store adv_sk_ API keys in connector headers or secrets managers, not in chat logs or source control.
  • AdAdvisor may retain usage telemetry under its platform terms; review privacy policy before connecting production accounts.

Prerequisites

  • AdAdvisor account with Meta Ads connected and an API key (adv_sk_...) for MCP authentication.
  • Claude Pro, Team, or Enterprise with Connectors support, or another MCP client with streamable HTTP connectors.
  • Meta Ads account permissions sufficient for the campaigns and assets you plan to query or modify.
  • Review of AdAdvisor pricing and plan limits before enabling write workflows in production accounts.

Schema details

Install type
cli
Reading time
4 min
Difficulty score
35
Troubleshooting
Yes
Breaking changes
No
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "adadvisor": {
      "url": "https://api.adadvisor.ai/mcp",
      "type": "http"
    }
  }
}

About this resource

Overview

AdAdvisor provides a hosted Model Context Protocol server aimed at media buyers running Meta Ads. Instead of exposing raw Graph API primitives, it offers curated workflows for browsing creative libraries, launching campaigns, uploading creatives, building retargeting audiences, and optimizing performance directly from Claude and other MCP clients.

Setup and API key guidance are published at adadvisor.ai and the connector is hosted at https://api.adadvisor.ai/mcp.

Features

  • Curated Meta Ads workflows for common media-buying tasks.
  • Query accounts, campaigns, ad sets, ads, metrics, and settings.
  • Browse and preview creative libraries inside chat.
  • Launch conversion campaigns and upload new creatives.
  • Build retargeting audiences and run performance optimization prompts.
  • Streamable HTTP transport with Bearer token authentication.

Use Cases

  • Review active campaign ROAS and pause underperforming ad sets from chat.
  • Browse video and image creatives before launching a seasonal sale.
  • Create a retargeting audience for site visitors who did not purchase.
  • Summarise weekly spend and conversion trends across ad accounts.
  • Draft a new prospecting campaign structure before manual review.

Installation

Claude (Connectors)

  1. Create an AdAdvisor API key (adv_sk_...) under account settings.
  2. In Claude, open Settings → Connectors → Add custom connector.
  3. Set the URL to https://api.adadvisor.ai/mcp and add an Authorization: Bearer adv_sk_... header.
  4. Connect the account and invoke Meta Ads workflow tools in a new conversation.

Claude Code

claude mcp add --transport http adadvisor https://api.adadvisor.ai/mcp
claude mcp list

Other MCP clients

Add the connector using the JSON configuration below in your MCP client settings.

Configuration

{
  "mcpServers": {
    "adadvisor": {
      "url": "https://api.adadvisor.ai/mcp",
      "type": "http"
    }
  }
}

For authenticated setups:

{
  "mcpServers": {
    "adadvisor": {
      "url": "https://api.adadvisor.ai/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer adv_sk_YOUR_KEY"
      }
    }
  }
}

Add the Authorization header with your AdAdvisor API key for authenticated workflow tools.

Examples

Creative library browse

Show me the videos and images in my Meta ad account creative library.

Campaign performance

How are my active conversion campaigns performing this week? Optimize what needs attention.

Retargeting audience

Build a retargeting audience for people who visited my site in the last 30 days but did not purchase.

Security

  • AdAdvisor workflow tools can change live ad spend and targeting; confirm destructive actions.
  • Use least-privilege Meta Business roles for the connected ad account.
  • Rotate adv_sk_ keys if they appear in chat, screenshots, or shared configs.

Troubleshooting

401 or auth errors

Verify the Bearer token uses the adv_sk_ prefix and matches an active AdAdvisor API key.

Empty account data

Confirm the Meta ad account is linked in AdAdvisor and the key has access to that business.

Connector timeout

Retry after a few seconds; hosted endpoints may cold-start during peak traffic.

Write action blocked

Check Meta account permissions and AdAdvisor plan limits for campaign creation tools.

Duplicate Check

No existing adadvisor slug or adadvisor.ai source URL was found in content/mcp/. This entry is distinct from generic marketing automation MCP servers because it targets AdAdvisor's curated Meta Ads workflows rather than raw Graph API wrappers.

Source citations

Add this badge to your README

Show that AdAdvisor MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/adadvisor-mcp-server.svg)](https://heyclau.de/entry/mcp/adadvisor-mcp-server)

How it compares

AdAdvisor MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldAdAdvisor MCP Server for Claude

Hosted AdAdvisor MCP server with curated Meta Ads workflows for browsing creatives, launching campaigns, building audiences, and optimizing performance from Claude via streamable HTTP.

Open dossier
AutoRFP.ai MCP Server for Claude

Official AutoRFP.ai remote MCP server for read-only access to RFP projects, requirements, approved content library search, and organisation tags from Claude and other MCP clients via OAuth.

Open dossier
Auxen MCP Server for Claude

Official Auxen.ai remote MCP server for listing GPU models and instances, checking account balance, and provisioning or destroying inference instances from Claude via OAuth 2.1 or API keys.

Open dossier
Baselight MCP Server for Claude

Official Baselight remote MCP server for searching and querying a catalog of 70,000+ public datasets from Claude via OAuth or x-api-key authentication.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorAdAdvisorAutoRFP.aiAuxen AIBaselight
Added2026-06-142026-06-142026-06-142026-06-14
Platforms
Claude CodeCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesWorkflow tools can create or modify Meta Ads campaigns, ad sets, creatives, and audiences when your token has write scope. Bearer tokens grant persistent account access until revoked in AdAdvisor or Meta Business settings. Treat returned spend, conversion, and audience data as business-sensitive before sharing in chat exports. Verify AI-proposed budget or targeting changes before approving tool calls on live ad accounts.The connection is read-only; it cannot create, edit, or delete AutoRFP.ai records. Each user inherits their own AutoRFP.ai permissions, so MCP results reflect that user's normal app access. OAuth tokens grant persistent read access until revoked in AutoRFP.ai or the MCP client. Do not share OAuth-approved connector sessions across users or paste access tokens into public issues.provision_model creates billable GPU instances; confirm model, region, and cost before approving tool calls. destroy_instance permanently removes running instances and cannot be undone through MCP. API keys prefixed auxen_live_* operate on production resources; use auxen_test_* keys in development. OAuth tokens grant persistent account access until revoked in Auxen or the MCP client.Query tools may return large result sets; scope filters to avoid excessive data transfer. Some datasets are community-contributed; validate schema and quality before production use. OAuth tokens and API keys grant persistent catalog access until revoked. Do not run unreviewed SQL-like queries against sensitive production mirrors without safeguards.
Privacy notesAccount IDs, campaign names, creative assets, and performance metrics are sent to AdAdvisor and Meta APIs. Store adv_sk_ API keys in connector headers or secrets managers, not in chat logs or source control. AdAdvisor may retain usage telemetry under its platform terms; review privacy policy before connecting production accounts.MCP tool results can expose RFP project names, requirement text, approved answer content, and organisation tag vocabulary. Search queries sent to the content library are processed by AutoRFP.ai under its own data-handling terms. Public support notes should describe connector scope, not full requirement or library excerpts.MCP tool results can expose account balance, instance IDs, model names, and deployment metadata. Provisioning requests are processed by Auxen.ai under its own data-handling and billing terms. Do not paste live API keys or OAuth tokens into public issues or shared chat logs.Search terms and query filters are sent to Baselight and may appear in usage logs. Dataset rows returned through MCP may include PII or licensed third-party content subject to dataset terms. Avoid pasting raw dataset excerpts containing personal data into public channels.
Prerequisites
  • AdAdvisor account with Meta Ads connected and an API key (adv_sk_...) for MCP authentication.
  • Claude Pro, Team, or Enterprise with Connectors support, or another MCP client with streamable HTTP connectors.
  • Meta Ads account permissions sufficient for the campaigns and assets you plan to query or modify.
  • Review of AdAdvisor pricing and plan limits before enabling write workflows in production accounts.
  • AutoRFP.ai account with access to the projects and content library you want to query.
  • Claude Pro, Team, or Enterprise plan with Connectors support, or another MCP client with custom remote connectors.
  • Claude organisation admin for the one-time org connector setup in Claude Team/Enterprise environments.
  • Knowledge of your AutoRFP.ai data residency region (APAC, EU, or US) to select the correct MCP endpoint.
  • Auxen.ai account with billing enabled for production instance provisioning.
  • Claude Pro, Team, or Enterprise with Connectors support, or another MCP client with remote HTTP connectors.
  • OAuth 2.1 + PKCE flow support in your MCP client, or an Auxen API key prefixed with auxen_live_ or auxen_test_.
  • Understanding that provision_model and destroy_instance are destructive and may incur GPU charges.
  • Baselight account with API access or OAuth authorisation for dataset queries.
  • Claude Pro, Team, or Enterprise with Connectors support, or another MCP client with remote HTTP connectors.
  • Understanding of the dataset topics you plan to query to narrow catalog searches effectively.
  • Compliance review if exported dataset rows may contain regulated or personal data.
Install
claude mcp add --transport http adadvisor https://api.adadvisor.ai/mcp
claude mcp add --transport http autorfp https://api.autorfp.ai/mcp
claude mcp add --transport http auxen https://api.auxen.ai/mcp
claude mcp add --transport http baselight https://api.baselight.app/mcp
Config
{
  "mcpServers": {
    "adadvisor": {
      "url": "https://api.adadvisor.ai/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer adv_sk_YOUR_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "autorfp": {
      "url": "https://api.us.autorfp.ai/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "auxen": {
      "url": "https://api.auxen.ai/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer auxen_live_YOUR_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "baselight": {
      "url": "https://api.baselight.app/mcp",
      "type": "http",
      "headers": {
        "x-api-key": "YOUR_BASELIGHT_API_KEY"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.