AutoAdy’s MCP server isn’t Claude-only. It speaks the open Model Context Protocol over streamable HTTP, so ChatGPT connectors (developer mode) and any MCP-capable client — desktop agents, IDE assistants, custom agents you build — can audit, diagnose, and manage your Facebook and Instagram ad accounts by chat.
You get the same 60+ tools everywhere: full account audits, drop diagnostics, performance breakdowns, kill lists you review before anything is paused, budget scaling that respects Meta’s learning phase, and creative workflows.
OpenAI supports custom remote MCP servers through connectors in developer mode. The exact menu location changes as ChatGPT rolls the feature out, so follow OpenAI’s current documentation to enable developer mode and add a connector — then use:
Server URL: https://www.autoady.io/api/mcp Auth: Authorization: Bearer YOUR_KEY
Create your key at Settings → API Keys (autoady.io/settings) — it’s shown once, and you can revoke it anytime from the same page.
Any client that speaks MCP over streamable HTTP works. Point it at the server URL and send your key as a header — the only key-based path this server accepts:
https://www.autoady.io/api/mcp Authorization: Bearer YOUR_KEY
Clients that implement OAuth 2.1 for remote MCP servers can skip keys entirely — AutoAdy supports the full authorization flow, the same one claude.ai uses.
“Run a full audit of my ad account and tell me what needs attention.”
calls run_full_audit
“Why did my cost per lead double last week?”
calls diagnose_drop
“Break down performance by campaign for the last 30 days.”
calls get_campaign_insights
“Which ads are wasting budget? Show me the list before pausing anything.”
calls apply_all_kills
“Increase the budget on my best campaign by 20%.”
calls scale_budget_relative
Yes, through ChatGPT's connector support for remote MCP servers, available in developer mode. Availability varies by ChatGPT plan and rollout, so check OpenAI's current docs for where to enable it — once you can add a custom MCP connector, point it at https://www.autoady.io/api/mcp.
Create an API key at autoady.io under Settings, in the API Keys tab, and send it as an Authorization: Bearer YOUR_KEY header. That header is the only key-based path. Clients that cannot set headers should use OAuth 2.1, which AutoAdy supports in full.
Yes — it's one MCP server. Every client gets the same 60+ tools: audits, performance insights, drop diagnostics, creative analysis, budget changes, pausing, scaling, and ad creation.
Only if your plan allows it. Read tools work on every plan; write tools require Pro, are capped at 200 changes per hour per ad account, and destructive actions are annotated so the assistant asks before acting. Everything is logged and reversible.