Name: Fictura
Author: co.fictura

Tools observed via MCP handshake

search_docs — Full-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
list_docs — The 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 gue
read_doc — The complete markdown of one documentation page. Accepts a site-relative path such as '/implementation/welcome/sdk-quickstart' (a full docs.fictura.co URL works
get_app_setup — The 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
get_setup_status — What is actually configured for this app: the setup checklist, every Fictura feature toggle and whether it is on, and which third-party integrations (Stripe, Re
get_analytics — This app's real numbers. `overview` gives headline metrics (users, trials, trial→paid rate, events by name, cancel reasons, 14-day activity). `funnel` gives the
get_attribution_report — Where installs and revenue actually came from. `summary` is the headline attribution picture (installs, organic vs non-organic, revenue). `kpis` breaks the same
list_users — The app's users, most recently active first — each with an identity label, event count, last seen, and derived churn state (in_trial, converted, cancelled, expi
get_user — One user's identity (every stitched device / account / RevenueCat id), event breakdown, churn state and recent activity. Accepts the Fictura master user id, or
check_entitlement — The 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}
get_tracking_plan — Every 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
list_surfaces — Every paywall and onboarding flow, what is actually being served at each placement (running experiment > live > none), and the valid placement names. IMPORTANT:
get_surface — The full configuration of one paywall or onboarding flow, plus its version history. Note that configs never contain price strings — prices resolve at render tim
list_templates — The 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
list_experiments — Every experiment with status and, for running or finished ones, full Bayesian results — exposures, conversions, and the probability each variant is best.
get_experiment — One experiment with its variants and full Bayesian results.
get_acquisition_report — `roas` gives per-campaign spend, attributed installs/trials/paying users, revenue, CPI, CAC and ROAS, plus blended totals and explicitly-unattributed revenue —
get_store_analytics — Store-reported numbers synced from Appfigures: downloads, re-downloads, updates, uninstalls, store revenue after the store's cut (subscriptions, in-app purchase
list_campaigns — Campaigns 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
list_creators — Creator records with a 28-day funnel per creator (clicks, installs, trials, paying users) and the tracking links tagged to each.
get_link_infrastructure — How 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
get_push_config — Whether push is set up and who could receive it: registered-device counts per billing cohort (all / paid / trial / free) and whether OneSignal is configured. Re
list_store_products — This 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 pro
list_error_issues — The error feed: grouped issues with level, status, event and user counts, a 14-day sparkline, plus the app's uptime summary. Defaults to unresolved issues only.
get_error_issue — One issue in full: the group, its 50 most recent occurrences with stack traces, release and environment, and 30 days of daily counts. This is the tool to reach
search_error_issues — Find issues by text in the title or culprit, platform, or release (first or last seen in). Returns the same rows as list_error_issues, filtered.
get_error_issue_brief — One issue condensed for fixing it: latest stack (resolved when source maps exist), in-app frames, breadcrumbs before it, facets (release, OS, device, screen), c
update_error_issue — Resolve, ignore or reopen an issue, assign it, set its priority, or add a note. Only works when the app allows MCP writes (Issues settings → Let MCP keys change
get_trace — Every span of one trace (app → backend → dependencies) as a tree: names, services, start offsets, durations, HTTP status and errors, plus the error events linke
get_paywall_doc — The JSON document a Studio (visual editor) paywall is made of, with its status and version, plus the reference to the document model. Read this before save_payw
validate_paywall_doc — Runs a document through the same parser and renderer a save uses and reports what is wrong, if anything. Changes nothing.
save_paywall_doc — Replaces a draft paywall's document with the one given, as a new version (History in the dashboard shows it as `mcp: <note>` and can roll it back). Refused for
create_paywall_draft — Creates a draft paywall from a Studio template (template_key, from list_templates — the webview ones) or from a document you wrote. It is never made live: going
pair_editor — Connects to the paywall editor a person has open, using the 6-character code shown under “Pair an agent” in the Studio. Returns a pairing_id for the editor_* to
editor_get_doc — The document exactly as it is on the person's screen (unsaved changes included), which paywall it is, the screen they are on and the node they have selected, pl
editor_set_doc — Replaces the document in the person's open editor with the one given. It is NOT saved: the person sees the change, can undo it, and saves it themselves. The doc
unpair_editor — Stops this pairing. The editor shows that the agent left.
get_onboarding_doc — The JSON document a builder-made onboarding flow is made of, with its status and version, plus the reference to the document model. Read this before save_onboar
validate_onboarding_doc — Runs a document through the same parser, step-key check and renderer a save uses and reports what is wrong, if anything. Changes nothing.
save_onboarding_doc — Replaces a draft flow's document with the one given, as a new version (the dashboard's history shows it as `mcp: <note>` and can roll it back). Refused for a li
create_onboarding_draft — Creates a draft onboarding flow from a document you wrote (see get_onboarding_doc's reference). It is never made live: going live is done in the dashboard. Need
start_appsflyer_import — Import everything AppsFlyer holds for this app: installs and the channel, campaign, adset and ad behind each one, in-app events and purchases, uninstalls, reins
get_appsflyer_import_status — Whether AppsFlyer is connected, the latest import run (status, progress, rows imported, duplicates skipped, people created, date range covered, error if it stop
get_appsflyer_attribution_summary — What the AppsFlyer import brought in about where people came from: people with an imported attribution, split by media source (organic included) and acquisition

when	check	result	http	latency	detail
51 min ago	mcp initialize	ok	200	131 ms	server fictura 1.0.0 · protocol 2025-06-18 · 44 tools
10 h ago	mcp initialize	ok	200	124 ms	server fictura 1.0.0 · protocol 2025-06-18 · 44 tools
19 h ago	mcp initialize	ok	200	109 ms	server fictura 1.0.0 · protocol 2025-06-18 · 44 tools
27 h ago	mcp initialize	ok	200	101 ms	server fictura 1.0.0 · protocol 2025-06-18 · 44 tools
35 h ago	mcp initialize	ok	200	104 ms	server fictura 1.0.0 · protocol 2025-06-18 · 44 tools
2 d ago	mcp initialize	ok	200	102 ms	server fictura 1.0.0 · protocol 2025-06-18 · 44 tools
2 d ago	mcp initialize	ok	200	102 ms	server fictura 1.0.0 · protocol 2025-06-18 · 44 tools
2 d ago	mcp initialize	ok	200	102 ms	server fictura 1.0.0 · protocol 2025-06-18 · 44 tools
3 d ago	mcp initialize	ok	200	102 ms	server fictura 1.0.0 · protocol 2025-06-18 · 44 tools
3 d ago	mcp initialize	ok	200	125 ms	server fictura 1.0.0 · protocol 2025-06-18 · 44 tools

Fictura

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from