Skip to main content

Plans & pricing

No. Aeris tools that read data are on every plan. Actions that would spend money or change a live campaign are always gated behind your normal Aeris approval — the assistant drafts, you approve. Nothing changes about your Aeris billing when you connect an assistant.
Yes — but that’s an assistant-side limit, not Aeris. Free ChatGPT and free Claude don’t include custom connectors:
AssistantMinimum plan for MCP
Claude DesktopPro, Team, or Max
ChatGPTPlus, Pro, or Business (with Developer mode on)
CursorAny paid tier
Free tiers of these products can’t add custom connectors. If you upgrade later, the Aeris connector is already there — no re-setup.
No connection fee, no per-request charge. Tool calls run against your Aeris account like any other in-product query.

Security & data

Whatever your account can see in Aeris. If you’re a viewer on one workspace and an owner on another, the assistant sees exactly the same data across both — no more, no less.
Every tool call is a direct request from the assistant to Aeris. We answer, and the assistant summarizes the answer in the chat. Nothing is stored on the assistant’s servers beyond the chat transcript itself. If you delete the chat in Claude / ChatGPT / Cursor, that transcript is gone; Aeris keeps its own audit log the same way it does for in-product actions.
Aeris runs an OAuth 2.1 authorization server with PKCE and Dynamic Client Registration. When you click Connect in your assistant, it registers itself with our server, opens a browser to tryaeris.ai/mcp/consent, you sign in (passwordless email OTP if you’re not already), and grant scoped access. No copy-pasting API keys.
By default, Read and Draft. Read covers reporting, audits, and connected-account status. Draft covers preparing campaigns, optimizations, and AEO fixes for your review. Apply — pushing changes back to the ad platforms — is off by default; Aeris asks you to approve per action when the assistant proposes something that would actually spend money or change a live campaign.

Managing connections

Two ways:
  1. From your assistant — remove the Aeris connector in the assistant’s settings. This just stops the assistant from making calls; the OAuth token stays alive on our side until it naturally expires (30 days).
  2. From Aeris (definitive) — sign in at tryaeris.ai, open Connections, find the assistant, and revoke. The token is invalidated immediately and any in-flight call fails auth on the next call.
Doing both is fine. If you’re worried a token has leaked, use option 2.
Add the connector again in the assistant with the same URL (https://mcp.tryaeris.ai/mcp). The assistant does a fresh OAuth flow; you’ll see the consent screen again.
Not from the same install of the assistant. The MCP connector is a single credential per assistant. If you need to switch, revoke and reconnect with the other account.
Your home workspace — the same one your Aeris dashboard defaults to. Cross-org support (a switch_org tool that lets the assistant pick a different workspace mid-chat) is on the roadmap for advertiser groups managing multiple brands.

Troubleshooting

Aeris only surfaces channels you’ve connected in Aeris itself. If you haven’t connected Google Ads / Meta / etc. yet, do that at tryaeris.ai/connections and the assistant will pick it up on the next tool call — no reconnect needed.
Assistants render tool-result images differently. Claude Desktop and ChatGPT show inline PNGs; older clients may show a code block or nothing. If you’re on an out-of-date client, upgrade and reconnect.
The assistant’s dynamic-registration call couldn’t reach us. Delete the connector, restart the assistant, and re-add it. If it persists, email us at [email protected] with the reference id the assistant shows.

Next steps

Connect to Claude

5 steps, ~60 seconds.

Connect to ChatGPT

Developer mode required.
Still stuck? [email protected].