Three big drops this cycle: MCP server (Beta) — your first chance to plug Qonversion straight into Claude, ChatGPT, Cursor, or any MCP-compatible AI agent. Smarter conditional logic in No-Code — Variables got richer and User Properties now drive component behavior. Public API now covers ~90% of the Dashboard — almost anything you can click, your code can call.
Qonversion MCP Server is in Beta
Plug Qonversion into AI? Yep. We did that.
Our MCP (Model Context Protocol) server is now in beta — your subscriptions, paywalls, customers, and analytics, exposed to AI agents through ~50 typed tools. Connect it once via OAuth, then ask Claude to summarize last week's MTR by country, have an agent set up a new offering for your holiday test, or wire Qonversion into an automated weekly audit. No more "open the dashboard, copy a number, paste it into Slack."
What's inside:- OAuth-based connection — secure, scoped access (no long-lived API keys to babysit)
- ~50 typed tools across products, offerings, entitlements, customers, experiments, segments, remote configs, automations, integrations, project settings, events, exports, analytics, and No-Code screens
- Destructive action protection — agents must confirm with a token + reason before any delete. Your data stays put even when a model gets bold ideas
- Works with Claude, ChatGPT (MCP), Cursor, Codex — and any other MCP-compatible client
No-Code Builder: Smarter Conditional Logic
Paywalls used to be one-size-fits-all. Not anymore.
Two equal upgrades to conditional logic in No-Code this cycle: Variables got richer, and User Properties can now drive component behavior. Show different content based on who's looking — country, plan, any custom property you set via the SDK.
Variables — four new types:- Product variables — reference a product (e.g.,
primary) anywhere on a screen. Swap the underlying product later (holiday SKU, regional pricing) and every reference updates automatically. Bonus: a single product variable can resolve to different products for different customers — set conditions on the variable itself. - User variables — auto-populated from user info. Use in components (personalize display) or in conditional logic (branch on user data).
- Device variables — auto-populated from device info. Use in display or branching.
- Custom variables — define your own, set the value, reuse anywhere.
A new Variables sidebar in Settings keeps it all in one place.
User Properties in Conditional Logic:User Properties are Qonversion's per-user parameters (set via the SDK — the same ones you already use in segments and integrations). You can now drive paywall conditional logic from them: show a different headline if country == "JP", swap the offer if plan == "free", hide the upsell if a custom property says trial-ending.
Public API Now Covers (Almost) the Whole Dashboard
If you're building on top of Qonversion, this is the cycle.
The Public API now covers roughly 90% of what the Dashboard can do — analytics, exports, configuration, automation. Almost anything a teammate can click in the dashboard, your code (or AI agent) can call programmatically.
New endpoints across:- Analytics — chart cards, chart-meta, currencies, cohorts, LTV (with trial conversion), insights
- Exports — list and inspect export history
- Configuration — segments, entitlement definitions, scheduled reports, automations, project store settings (Apple/Google)
All HMAC-authenticated, project-scoped, double-validated. Same backend that powers the MCP server — so anything your AI agent can do, your code can do too.
Closing
A big cycle. AI agents now have a real seat at the Qonversion table, your No-Code paywalls can finally read who's on the other side of the screen, and the Public API is wide enough to build serious integrations on.
Kamo
Head of Product at Qonversion
Kamo leads product strategy at Qonversion, shaping the tools that help apps grow subscription revenue.
