Fictura

MCP server · hosted · installable · v0.1.2 · co.fictura/mcp

Online · tested 1h agoNEW · 2h agoSeen in the registry 1h ago

Paywalls, onboarding, subscription analytics, A/B tests, attribution and errors for mobile apps.

What it does

Fictura is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES

Local installYES

Live checkOnline · 44 tools

Version0.1.2

Packagesnpm

PriceNot in the registry

First seen29 Oct 2026

Last checked1h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)

Hosted endpoint

https://mcp.fictura.co/mcp streamable-http

In Claude Code: claude mcp add --transport http fictura https://mcp.fictura.co/mcp

Install package

NPM @fictura/mcp v0.1.2 · runs locally (stdio)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "fictura": {
      "url": "https://mcp.fictura.co/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1h ago

ONLINE Fictura answered an MCP connection on 29 Oct 2026 and introduced itself as fictura 1.0.0 (MCP protocol 2025-06-18).

44 tools offered to AI assistants

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 or webhooks — the docs are the source of truth and are regenerated on every code
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 guess. No API key required.
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 too). If the path is wrong, the closest real paths come back as suggestions. No
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 call this before generating integration code — never leave a placeholder API key
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, RevenueCat, Slack, Sentry, App Store Connect, …) are connected. Use it to check wh
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 ordered conversion funnel with per-step drop-off. `cohorts` compares behaviour
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 window down by source, campaign, link or day. `installs` lists individual insta
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, expired, billing_issue, grace_period, paused, refunded, none). Capped so a large app
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 any identifier the app knows them by — a device id, account id or RevenueCat id.
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} returns to a server. Note: `environment` is SANDBOX when the verdict rests on t
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 event name instead of introducing a near-duplicate — the name chosen here is the
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: read `placements` before writing a placement string into code. The list is conf

Show 32 more

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 time from the PurchasesAdapter's packages, so never copy a price literal out of (or
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 so you pick a real template key rather than inventing one.
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 — always keep attributed and blended figures apart when reporting these. `spend` g
get_store_analytics · Store-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 reviews with text, and cate
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 set up. This calls the provider's API, so prefer get_acquisition_report for hist
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 that Fictura serves in the Universal Links / App Links association files, plus
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. Returns counts and configuration only — never device tokens or individual recipien
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 product that actually exists. Pass subscription_id to also fetch Apple's price ladd
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. `synthetic: true` marks console lines the SDK captured, not crashes.
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 for when asked to fix a production error. When the app uploaded source maps, eac
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), cause chain, and a ready-to-use fix prompt.
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 issues).
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 linked to the trace. Take the trace_id from an occurrence in get_error_issue. Use it
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_paywall_doc, and edit the document you got rather than writing one from scratch — ke
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 a live paywall — copy it in the dashboard first. Needs an MCP key that can edit.
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 live is done in the dashboard. Needs an MCP key that can edit.
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_* tools. The code works once and for 10 minutes; a pairing lasts 24 hours or until e
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, plus the document model reference. Read this before editor_set_doc and edit what y
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 document is validated first and refused with the problems if it does not parse. Nee
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_onboarding_doc, and edit the document you got rather than writing one from scratch — k
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 live flow. Needs an MCP key that can edit. Translations, overrides and the exit se
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. Needs an MCP key that can edit.
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, reinstalls, ad revenue and retargeting traffic. All twelve raw-data reports are walke
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 stopped), and whether an import has ever finished. Call before start_appsflyer_impor
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 vs retargeting, plus the top campaigns. Filters on the install date. Imported v

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.

Fact	Value	Evidence	Source	Last confirmed
Install package	@fictura/mcp	DECLARED	SRC-001 Official MCP Registry	1h ago
Hosted endpoint	https://mcp.fictura.co/mcp	DECLARED	SRC-001 Official MCP Registry	1h ago
Package registries	npm	DECLARED	SRC-001 Official MCP Registry	1h ago
Local install (package)	yes	DECLARED	SRC-001 Official MCP Registry	1h ago
Remote access (hosted)	yes	DECLARED	SRC-001 Official MCP Registry	1h ago
Website	https://docs.fictura.co/connections/outgoing/mcp-server	DECLARED	SRC-001 Official MCP Registry	1h ago
Repository	https://github.com/Apex-Byte-Technologies/fictura-mcp	DECLARED	SRC-001 Official MCP Registry	1h ago
Registry status	active	DECLARED	SRC-001 Official MCP Registry	1h ago
Version	0.1.2	DECLARED	SRC-001 Official MCP Registry	1h ago
MCP server	yes	DECLARED	SRC-001 Official MCP Registry	1h ago

Change history

NEW29 Oct 2026
first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Is Fictura still online?

Free alerts · no account

Do you run Fictura? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor FicturaLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Questions about Fictura

How do I connect Fictura?

Use the hosted endpoint https://mcp.fictura.co/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Fictura offer?

When Electra Index connected on 29 Oct 2026, it listed 44 tools: search_docs, list_docs, read_doc, get_app_setup, get_setup_status, get_analytics, get_attribution_report, list_users and more. The full list is in "Live check" above.

Is Fictura online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.