Skip to main content
This section is for AI agents, and for the person pointing one at Qonversion. Three surfaces, and they do different jobs:

​
Have an agent integrate the SDK

Paste this into Claude Code, Cursor, Codex or any coding agent working in your app’s repository.

Integrate the Qonversion SDK using the official documentation.

Open in Cursor
Prefer to do it by hand? The steps are in the quick start.

​
Connect an agent to your project data

The Qonversion MCP server exposes the REST API v4 resource surface as tools: customers, users, identities, purchases, user properties, entitlements, products, remote configurations, experiments, segments, analytics, exports, events, scheduled reports, integrations and project settings, plus Apple Ads reports as a closed beta — the same reports are also readable through REST API v4.
Claude Code
Setup for Claude Desktop, Cursor, VS Code, Windsurf, Zed, Codex and stdio clients: MCP Server. Two things to know before you point an agent at a project:
  • Access mirrors your dashboard role. The agent authenticates as you over OAuth 2.1, and each tool is gated by its own scope. No API key is handed to the model.
  • Destructive tools stop and ask. delete_*, revoke_*, detach_* and the deprecated regenerate_project_secret return a short-lived token addressed to you, not to the agent, and completing the action requires echoing the resource id verbatim and giving a reason.

​
Let an agent read these docs

  • MCP: https://documentation.qonversion.io/mcp — search and fetch pages, no authentication.
  • Markdown of any page: append .md to the URL, for example https://documentation.qonversion.io/docs/quickstart.md.
  • Page index: llms.txt — every page, one line each.
  • Whole corpus: llms-full.txt — the full text in one file. It is large; prefer the MCP server or single pages when the context window matters.
  • In-page buttons: every page has a copy control that yields markdown, or hands the page to Claude or ChatGPT.

​
Call the API directly

For a backend, a cron job or a warehouse sync, use the REST API v4 with a project Secret Key. Operation ids are verb-based, and errors carry type, code and field-level detail so an agent can correct itself without parsing prose. Lists paginate, but not all with the same parameters — read the resource guide before writing one pager for everything. Start at API reference. Keep Secret Keys on a server — see Project keys — and check the limits that apply to the surface you are calling, in Rate limits for the SDK and in Apple Ads for the Apple Ads report and series.

​
Next steps

MCP & API

Which surface to pick, and where the two differ.

MCP Server

Tool list, per-client setup, scopes, confirmation flow.

Apple Ads via MCP

Reading campaign performance from an agent, and the ways the numbers are easy to misread.

llms.txt

What the file is and where it lives.