← Back to AutoAdy

Use AutoAdy in Claude

What this is

AutoAdy ships a Model Context Protocol (MCP) connector, so you can manage your Meta (Facebook & Instagram) ad accounts by chatting with Claude — or any MCP-compatible assistant. Ask “how are my ads doing?”, “why did my CPL spike?”, or “pause the losers” and the connector answers with live data from your account: 60+ tools covering audits, performance breakdowns, drop diagnostics, budget moves, scaling plans, and ad creation.

In clients that support interactive MCP Apps (Claude Desktop today), results render as live views inside the chat — ranked top-performer cards, a sortable campaign table, an account-health score, and a review-and-confirm flow for pausing ads. Text-first clients get the same data as clean text.

Before you start

  • An AutoAdy account with your Meta ad account connected — start here if you don’t have one.
  • On claude.ai no API key is needed — you’ll sign in to AutoAdy in the browser when connecting (OAuth). For Claude Code, the Desktop extension, or any key-based setup, create a key under Settings → API keys → Create key; copy it immediately — it’s shown once, and you can revoke it anytime from the same page.

Claude (claude.ai)

Add AutoAdy to Claude

That opens Claude’s Add custom connector dialog with the name and URL already filled in — press Add to confirm. Claude flags it as suggested by an external link, which is expected; check the URL reads https://www.autoady.io/api/mcp before adding.

Prefer to do it by hand? Open Settings → Connectors → Add custom connector and paste this URL — no API key needed:

https://www.autoady.io/api/mcp

Either way, Claude opens an AutoAdy sign-in window; approve access and you’re connected.

Then start a new conversation and ask something like “show my top performing ads from the last 30 days using AutoAdy”. Results are text-based on claude.ai today; interactive views are coming as Claude expands MCP Apps support for custom connectors.

Claude Code (CLI)

Claude Code connects to AutoAdy over streamable HTTP with your API key in a header — the most reliable setup. Add it from your terminal:

claude mcp add --transport http autoady https://www.autoady.io/api/mcp \
  --header "Authorization: Bearer YOUR_KEY"

Or add it to your project’s .mcp.json directly:

{
  "mcpServers": {
    "autoady": {
      "type": "http",
      "url": "https://www.autoady.io/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

Restart Claude Code, run /mcp to confirm autoady is connected, then ask “list my ad accounts” or “audit my account”.

Why a key instead of OAuth here: Claude Code’s browser “Approve” step relies on a local loopback callback that can hang in the CLI. The header-key setup skips that entirely and gives the same tools. (OAuth remains the recommended path on claude.ai, which uses a browser redirect rather than a loopback.)

Claude Desktop — one-click install (interactive views)

Claude Desktop renders AutoAdy’s interactive views — live ad cards, sortable tables, and the review-and-confirm kill flow, right in the chat. Installing takes under a minute:

  1. Download the AutoAdy extension (.mcpb)
  2. Double-click the downloaded file — Claude Desktop opens an install dialog.
  3. Paste your AutoAdy API key when asked, and click Install.
  4. Start a new chat and try: “show my top performing ads from the last 30 days”.

About the install warning: Claude Desktop shows a standard notice for every extension installed outside its built-in directory — it isn’t specific to AutoAdy. Our extension is a small, dependency-free forwarder (~80 lines) whose only job is relaying your chat’s tool calls to autoady.io with your API key. It reads no files and contacts no other servers — you can verify this yourself: rename the .mcpb to .zip and open server/index.js.

Advanced alternative: add the server manually via npx mcp-remote https://www.autoady.io/api/mcp --header "Authorization: Bearer YOUR_KEY" in claude_desktop_config.json.

Other MCP clients

Any client that speaks MCP over streamable HTTP works: point it at https://www.autoady.io/api/mcp with an Authorization: Bearer YOUR_KEY header. That is the only key-based path — a client that cannot set headers should use OAuth 2.1 instead.

Things to try

  • “Run a full audit of my ad account”
  • “Show my top performing ads from the last 30 days”
  • “Why did my leads drop last week?”
  • “How healthy is my account?”
  • “Which ads should I pause? Let me review the list first”
  • “Plan how to scale my best campaign without resetting learning”

Safety and permissions

  • Read tools (insights, audits, diagnostics) are available on every plan.
  • Write tools (pausing, budgets, launching ads) require a Pro plan, are capped at 200 changes per hour per ad account, and destructive actions are annotated so your assistant asks before acting.
  • Kill recommendations always render for review before anything is paused.
  • Every change is logged in AutoAdy and reversible from AutoAdy or Ads Manager.
  • Your API key acts as you — treat it like a password. Revoke it anytime in Settings.

Questions? See our privacy policy or contact us.

Privacy PolicyTerms of ServiceData DeletionContact