Ask your app data
what to optimize next.

It is a hosted Model Context Protocol endpoint that gives compatible AI clients structured tools for understanding acquisition, onboarding funnels, conversion, revenue, attribution, events, and integration health. With optional write scopes, it can also propose and execute separately approved Apple Ads and TikTok Ads changes.

Any client that supports remote Streamable HTTP MCP and browser-based OAuth can connect. The client adds one Postback endpoint, then opens a browser so you can approve access to a specific app.

Yes. MCP access is included in every paid Postback plan. You do not pay for a separate MCP add-on, and the same connection can use the analytics, funnel, attribution, revenue, and approved ad-action tools available to your account.

No. Postback hosts the remote Streamable HTTP endpoint. Add the Postback URL to your AI client and complete authorization in the browser—there is no local package, background process, or server for you to maintain.

Read access cannot write data. If you explicitly grant an ad-network write scope, the client can propose and execute provider changes only after a signed-in person approves the exact plan in Postback. It cannot create, update, or delete apps, integrations, billing settings, SDK keys, or attribution records.

No. Every client uses the same clean endpoint. Postback completes authorization in the browser and sends short-lived credentials through the Authorization header, never in the URL.

Yes. Read tools query the current acquisition, funnel, conversion, revenue, attribution, and integration data in Postback. Before a write-capable flow proposes a change, Postback also reads the current Apple Ads or TikTok Ads state so the plan starts from the value that is live now.

Revoke the connection from Postback. Access tokens are short-lived, refresh tokens rotate, and reuse of an old refresh token revokes the complete grant automatically.