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 136 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: OAuth account sign-in (DCR)
Sign in to AutoAdy when ChatGPT prompts you. Manual API keys are not accepted by ChatGPT custom connections. Follow the current instructions in Settings → Agents (open the agent guide). Review the discovered tools and complete AutoAdy account sign-in.
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 list_kill_recommendations
“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.
ChatGPT custom MCP connections use OAuth account sign-in, with dynamic client registration (DCR) supported by AutoAdy. They cannot present a manual AutoAdy API key. Other MCP clients that support custom headers can use Authorization: Bearer with an AutoAdy key from Settings → Agents → API Keys.
Yes — it's one MCP server. Every client gets the same 136 tools: audits, performance insights, drop diagnostics, creative analysis, budget changes, pausing, scaling, and ad creation.
Only if your plan allows it. Read tools change nothing and work on the free plan, with these exceptions: diagnose_drop needs a Solo, Growth or Agency plan; run_gaql and run_graph_read are not available on the free plan; and a free key can call analyze_winning_ad 25 times a day, because it reaches a language model. Every other read is unmetered. A free key is read-only: every write tool needs a paid plan (Solo, Growth or Agency), including tools that only change AutoAdy such as switch_account and prepare_website_installation. On a free key they refuse with a message naming the upgrade. Changes to an ad account are capped at 200 per hour per account, and destructive actions are annotated so the assistant asks before acting. Everything is logged and reversible.