Fictura
OnlineNewPaywalls, onboarding, subscription analytics, A/B tests, attribution and errors for mobile apps.
What it can do: 80 tools
search_docsread-onlyFull-text search across the Fictura docs, grouped by page. Use this before answering any 'how do I…' question about the SDK, API, paywalls, entitlements, links or webhooks — the docs are the source of truth and are regenlist_docsread-onlyThe full documentation index — every page path, grouped by section, with a one-line description. Use it to find the right page when a search term is hard to guess. No API key required.read_docread-onlyThe complete markdown of one documentation page. Accepts a site-relative path such as '/implementation/welcome/sdk-quickstart' (a full docs.fictura.co URL works too). If the path is wrong, the closest real paths come bacget_app_setupread-onlyThe real values needed to wire the Fictura SDK into a codebase: the API base URL, this app's publishable SDK key (gk_…), and the RevenueCat webhook URL. ALWAYS call this before generating integration code — never leave aget_setup_stepread-onlyWhat to do for one of Fictura's six setup steps, ready to follow: the instructions, this app's real values (so there is nothing to fill in), the full text of that step's docs pages, and how to check it worked. Call thisget_setup_statusread-onlyWhere this app has got to: the six setup steps and which are really done, worked out from data that has arrived, then the billing state, every Fictura feature toggle and whether it is on, and which third-party integratioupdate_app_identitySaves what the app IS to Apple, Google and the web: the iOS bundle ID and Apple Team ID (which build the Universal Links file), the Android package and signing fingerprints (which build the App Links file), both store adcreate_tracking_linkCreates a tracking link and returns its shareable URL. A tap is logged as a click, then redirected to destination_url with the click's id, which is how an install is credited to the link. A tap from a computer goes to deget_analyticsread-onlyThis app's real numbers. `overview` gives headline metrics (users, trials, trial→paid rate, events by name, cancel reasons, 14-day activity). `funnel` gives the ordered conversion funnel with per-step drop-off. `cohorts`get_attribution_reportread-onlyWhere installs and revenue came from, on the same definitions as the dashboard and the API. An install is a device's first SDK launch (install_at) in the range; server-only users are never installs. Non-organic = installlist_usersread-onlyThe app's users, most recently active first — each with an identity label, event count, last seen, and derived churn state (in_trial, converted, cancelled, expired, billing_issue, grace_period, paused, refunded, none). Cget_userread-onlyOne user's identity (every stitched device / account / RevenueCat id), event breakdown, churn state and recent activity. Accepts the Fictura master user id, or any identifier the app knows them by — a device id, accountcheck_entitlementread-onlyThe authoritative paid/not-paid verdict for one user, unified across Stripe, RevenueCat, App Store and Play — the same answer GET /api/v1/entitlements/{user_id} returns to a server. Note: `environment` is SANDBOX when thget_tracking_planread-onlyEvery event this app has ever sent, with volume, last-seen, and whether capture is switched off. Use it before adding instrumentation so you reuse the existing event name instead of introducing a near-duplicate — the namget_event_analyticsread-onlyOne tab of the dashboard's Events page with the exact numbers behind it. overview: totals against the previous period and every event with users, count, previous count, worked and failed, plus key events. screens: views,list_surfacesread-onlyEvery paywall and onboarding flow, what is actually being served at each placement (running experiment > live > none), and the valid placement names. IMPORTANT: read `placements` before writing a placement string into coget_surfaceread-onlyThe configuration of one paywall or onboarding flow, plus its version history (version, note, date). A served design's compiled html is left out (html_bytes gives its size) and a Studio doc shows as doc: true; read the dlist_templatesread-onlyThe one-click starter templates available for paywalls or onboarding flows, with the template key and what each looks like. Use this when asked to add a paywall so you pick a real template key rather than inventing one.list_experimentsread-onlyEvery experiment with status and, for running or finished ones, full Bayesian results — exposures, conversions, and the probability each variant is best.get_experimentread-onlyOne experiment with its variants and full Bayesian results.create_experimentCreate an A/B test as a DRAFT: nobody sees it until start_experiment. 2 to 4 arms, each pointing at a paywall or onboarding flow of this app on the experiment's surface (ids from list_surfaces); one arm may be a holdoutstart_experimentStart a draft: from now on its arms are served to the users who pass its targeting. Refused when another test is running or paused on the same surface and placement. Only works when the app allows MCP writes.pause_experimentPause a running test: nobody new enrolls, and users already in it keep their arm. resume_experiment picks it up again. Only works when the app allows MCP writes.resume_experimentResume a paused test so new users enroll again. Refused when another test now holds its surface and placement. Only works when the app allows MCP writes.stop_experimentStop a running or paused test for good without rolling anything out: everyone gets the live config again. It can't be restarted. Rolling out a winner is done by a person in the dashboard. Only works when the app allows Mget_acquisition_reportread-only`roas` gives per-campaign spend, installs (install_at in the range, split exact / weak / modelled, fraud-flagged kept out of CPI), trials, paying users, cohort revenue (paid in the range by installs from the range), CPI,get_store_analyticsread-onlyStore-reported numbers synced from Appfigures: downloads, re-downloads, updates, uninstalls, store revenue after the store's cut (subscriptions, in-app purchases, ads), top countries, the ratings snapshot, recent reviewslist_campaignsread-onlyCampaigns read live from a connected ad platform: status, daily budget and ad sets. Returns a not_connected result rather than failing when the provider is not set up. This calls the provider's API, so prefer get_acquisilist_creatorsread-onlyCreator records with a funnel per creator for the last 28 days in the app's time zone (non-bot clicks, installs split exact / weak / modelled, trials, paying users, cohort net revenue and ROAS against the deal cost) andget_link_infrastructureread-onlyHow links reach the app. `app_links` is the most important for integration work: it returns the iOS team id, bundle id, Android package and SHA-256 fingerprints that Fictura serves in the Universal Links / App Links assoget_push_configread-onlyWhether push is set up and who could receive it: registered-device counts per billing cohort (all / paid / trial / free) and whether OneSignal is configured. Returns counts and configuration only — never device tokens orlist_store_productsread-onlyThis app's auto-renewable subscriptions in App Store Connect: product id, billing period and Apple review state. Use it to check that a paywall references a product that actually exists. Pass subscription_id to also fetclist_error_issuesread-onlyStart here to see what is broken: grouped issues from the backend and the app together, each with its source, level, status, event and user counts. Newest activity first, unresolved only. Console lines from the app are hsearch_error_issuesread-onlyFind an issue by text in its title or culprit, across every issue the app has. Use it when you know the error message, exception type or function. Same filters and rows as list_error_issues.search_error_eventsread-onlySingle occurrences across issues, newest first, or counts with group_by. Use it to answer which release or route an error hits, whether a person hit it, or what failed in one trace. Open one with get_error_event.get_error_eventread-onlyOne occurrence: frames with source lines and variables, request, tags, contexts, breadcrumbs, causes and trace id. Pass issue_id for its latest event, or event_id. Use it to see why one error happened. Long events give uget_error_issueread-onlyOne issue with its status, history, 30 days of daily counts and recent occurrences. The newest occurrence has its stack and frames, the older ones are one-line summaries. Use it to see how an issue behaves over time. Forget_error_issue_briefread-onlyUse this first when asked to fix an error. One issue condensed: in-app frames with their source lines, the request, tags, breadcrumbs before it, log lines from the same trace, facets (release, OS, device, route), cause cget_issue_tag_valuesread-onlyHow often each value of one tag or facet appears on one issue in the last 30 days. Use it to see where an issue concentrates: which release, route, device, logger or person. Leave out key to list the keys there are.get_issue_activityread-onlyWhat people and Fictura did to one issue, newest first: status changes, assignments, priority, notes with their text, tickets, regressions. Use it before changing an issue, to see who already looked at it.
…and 40 more.
Connect it
claude mcp add --transport http fictura https://mcp.fictura.co/mcpSettings → Connectors → Add custom connector
URL: https://mcp.fictura.co/mcp{
"mcpServers": {
"fictura": {
"url": "https://mcp.fictura.co/mcp"
}
}
}{
"servers": {
"fictura": {
"type": "http",
"url": "https://mcp.fictura.co/mcp"
}
}
}Questions
What does Fictura do?
Paywalls, onboarding, subscription analytics, A/B tests, attribution and errors for mobile apps. It exposes 80 tools to AI assistants.
What tools does Fictura provide?
80 tools, including search_docs, list_docs, read_doc, get_app_setup, get_setup_step, get_setup_status, update_app_identity, create_tracking_link, get_analytics, get_attribution_report, list_users, get_user….
How do I connect Fictura to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://mcp.fictura.co/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does Fictura require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is Fictura online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes Fictura?
fictura.co. The official MCP Registry verified that the publisher controls this domain before accepting the listing.
Similar in Analytics & BI
-
Google MonitoringOnlineOfficialPopular
Gain visibility into the performance, availability, and health of your apps and infrastructure.
-
beehiivOnline · sign-in requiredOfficialPopular
Manage beehiiv newsletters, posts, podcasts, community, subscribers, and analytics.
-
Kong KonnectOnline · sign-in requiredOfficialPopular
Manage Kong Konnect AI and API gateways, routes, plugins, and analytics from your agent.
-
UserpilotOnline · sign-in requiredOfficialPopular
Product analytics, user and company insights, surveys and NPS, reports, dashboards, and more.
-
PaddleOnline · sign-in requiredOfficial
Query and manage Paddle Billing: pricing, subscriptions, payments, revenue reports and webhooks.
-
Avalara E-Invoicing & Live ReportingOnline · sign-in requiredOfficial
Provides access to Avalara E-Invoicing and Live Reporting APIs for document statuses and compliance