Persyst connector
Purchasely MCP connector: subscriptions, paywalls and flows, readable by the whole team
Product, marketing or leadership follow revenue, subscribers and paywall conversion with no Purchasely account and no export.
Updated on November 1, 2026
Your tools
- Connected once, by the admin
- Rights per person, team or client
- Who read what, and when
Everyone’s AI
In short
- Persyst works without an MCP server to install: it is a remote MCP server shared by the team, with no developer tooling on anyone’s computer.
- Read-only: a Management API key with viewing scopes only is enough. Persyst creates, changes, publishes and deletes nothing in Purchasely.
- Purchasely is queried on each question: Persyst stores none of its data, beyond a cache of a few minutes that avoids asking for the same figure twice.
- Each team only sees the apps open to it; user profiles and purchases stay closed until an administrator enables them.
EXAMPLES
What your team can ask
Does the new paywall convert better than the old one since launch?
On the iOS app, since October 6, variant B of the “Annual onboarding” A/B test converts 4.8% of views into a free trial against 3.9% for variant A. Conversion to paid is still to be confirmed: most trials have not ended yet.
Sources consulted
- Purchasely · A/B test statistics
- Purchasely · paywall conversion
How many paying subscribers did we gain and lose this month?
In October, 1,240 paid entries and 860 exits, a net gain of 380. Exits mostly come from monthly plans on Android; annual plans are stable.
Sources consulted
- Purchasely · subscription trends
HOW IT WORKS
Purchasely in your AI, in three steps
Connect Purchasely
An administrator of the Purchasely account creates a Management API key with viewing scopes only. In Data sources, the Persyst administrator pastes it with its expiry date; Persyst checks it before saving it. The Purchasely guide covers each step.
Choose the apps and open access
In Apps, the administrator ticks the ones opened in Persyst, then, in Access management, opens them to the relevant teams, clients or members. The personal data tools stay closed until they are enabled.
Ask from the assistant
Everyone asks in ChatGPT, Claude or Copilot: “what is our paywall conversion by placement this month?”, “which A/B test variant is winning?”. The history keeps track of who looked at which app, and when.
TOOLS
What your assistant can do
Purchasely· 15 tools
Opened team by teamLists the Purchasely apps open to the member, with their identifier and name.
list_purchasely_appsLists an app’s screens (paywalls) and their versions, flows, placements, audiences, campaigns, A/B tests, products, plans, surveys and custom events, with their detail.
list_purchasely_catalogGives the current state: active subscriptions by status, active users, today’s figures, split by platform, plan and state.
get_purchasely_overviewGives MRR, subscription and one-time purchase revenue, churn and refunds over a period.
get_purchasely_revenueGives new subscriptions, reactivations, active base, paid entries and exits, retention by cohort, trials and introductory offers.
get_purchasely_subscription_trendsGives paywall views, taps on “buy”, offer starts and conversions to paid, split by screen, placement, audience, variant, plan, country or platform.
get_purchasely_paywall_conversionGives the funnel from views to purchases, grouped by screen, placement, plan, country or platform.
get_purchasely_funnelGives the paths followed through a flow, step by step.
get_purchasely_flow_pathsGives monthly active users and the number of events per period.
get_purchasely_usageGives the conversion of an app’s campaigns.
get_purchasely_campaign_statsGives the conversion and revenue of each variant of an A/B test.
get_purchasely_ab_test_statsGives how the answers to a survey are distributed.
get_purchasely_survey_resultsGives paywall display latency, SDK versions in use and their adoption, current integration errors.
get_purchasely_app_healthFinds a user by their identifier: transactions, events, devices. Off by default: it exposes personal data.
find_purchasely_userLists subscriptions and one-time purchases, with their detail. Off by default: it exposes personal data.
list_purchasely_purchases
Rights and audit trail
Rights per person, team or client.
Then, inside the tool, only the items you open. The rest does not exist for the AI.
One-click revocation.
Removing a member cuts their access in every AI at once.
A history.
Who used which tool, and when.
Credentials that stay put.
They remain encrypted in Persyst, never in the assistants.
COMPARISON
Persyst or direct access to Purchasely?
| Criterion | Persyst | Without Persyst: direct access to Purchasely |
|---|---|---|
| Who authenticates | The company, once, through an administrator. | Each person, with a Purchasely account or through someone who has one. |
| Installation | None: a remote MCP server, authorized from the assistant. | Nothing to install, but an export or a screenshot to redo for every question. |
| Where credentials live | Encrypted in Persyst, never in the assistant. | One Purchasely account per person, or files passed around by email. |
| Scope | Per person, team or client, then per opened item. | Everything the account allows. |
| History | Who used which tool, and when, for the whole team. | None. |
| When a member leaves | One-click revocation, in every AI. | Account to remove in Purchasely; what was already shared stays shared. |
What this connector does not do
- No writes: no paywall, flow, placement, audience, campaign, A/B test, product or plan is created, changed, published or deleted.
- Paywall content is not readable: Purchasely only returns their metadata.
- No real-time events (webhooks, Server Events), and no store configuration, translations, fonts or colors.
- Purchasely limits the calls per key, especially on dashboards: the assistant is then asked to wait or to shorten the period.
- No personal connection: Purchasely is connected at the organization level, with a team API key.
Questions
Frequently asked questions
Does each member need a Purchasely account?
No. An administrator of the Purchasely account creates a Management API key with viewing scopes only and hands it to the Persyst administrator. Members need neither an account nor an invitation to the console.
Where is the API key stored?
The key is encrypted in the organization’s secrets, never shown again nor written to logs. Persyst checks it with Purchasely before saving it, flags its expiry 14 days ahead and lets you replace it without losing the apps or the access.
Does the assistant see our users’ data?
Not by default. The tools that read a user profile or the list of purchases stay off until an administrator explicitly enables them. The other tools only return aggregated figures and object names.
Can the assistant change a paywall or start an A/B test?
No. The connector is read-only: the assistant can analyze results and suggest a variant, but creating and publishing happen in the Purchasely console.
Does the data stay with Persyst?
Persyst stores none of Purchasely’s data, beyond a cache of a few minutes. The figures read to answer are passed to the assistant of the person asking, like anything else they share with it.
