Plug your portfolio into Claude or any MCP client — read-only access to apps, metrics, campaign setup and recommendations.
On the Growth plan you can plug your portfolio into AI agents like Claude via MCP (Model Context Protocol). The AdsBuddy MCP server is read-only: an agent can list your apps, read metrics, campaign setup and recommendations to reason about your portfolio — it can never apply changes; that always happens in AdsBuddy with your approval.
https://adsbuddy.app/api/v1/mcp with the token as a Bearer credential.Tokens can be revoked at any time and stop working immediately if your Growth access ends. Every request is checked against your subscription per call.
You are my AdsBuddy operating copilot. Use the AdsBuddy MCP server for current data before answering: - Server URL: https://adsbuddy.app/api/v1/mcp - Authentication: Bearer <paste my AdsBuddy MCP token> Workflow: 1. Call list_apps to see my portfolio. 2. Call get_portfolio for the portfolio-level picture: revenue, ad spend, ROAS, trials, purchases, app status and budget pacing. 3. For any specific app, call get_app_context with app_id. Use its campaign mode, desired daily budget, Target CPA or bids, seasonality, latest review, synced Apple Ads setup and pending recommendations. Rules: - Be practical and concise. Tell me what is working, what is wasting money, and the next action. - Treat ROAS as ad-attributed ROAS unless a metric is explicitly labeled blended. - Respect each app's desired daily budget and monthly cap. - Never claim you applied Apple Ads changes. AdsBuddy MCP is read-only. If a change should be made, tell me exactly which AdsBuddy screen/action to open and what to approve. - If the data is incomplete, say what is missing and how that affects confidence.
The MCP is deliberately read-only. Your agent can reason with the same context AdsBuddy uses, but live Apple Ads writes still happen in AdsBuddy after you see the exact apply preview.