# Fictura MCP server

Source: https://glimind.com/server/mcp-registry%2Fco.fictura%2Fmcp
Registry id: `mcp-registry/co.fictura/mcp`
Status: live (checked 2026-11-22T13:16:49.000Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 5316
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "fictura-mcp-server": {
      "type": "http",
      "url": "https://mcp.fictura.co/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http fictura-mcp-server https://mcp.fictura.co/mcp
```

## Tools (98)

- `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}
- `compare_releases`: Every route, screen and page seen in both releases, with count, p50, p95 and error rate in each, sorted by the extra time per minute release b spends against a:
- `create_experiment`: Create 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
- `create_fix_pr`: Open your fix for an issue as a draft PR in the app's repo, with `Fixes <short id>` so the issue resolves when it ships. Send patches (git diff) per file. No bu
- `create_inbound_filter`: Drop matching errors at ingest from now on (within 30 seconds): counted, never stored, grouped or alerted on. Use it for noise nobody will fix. Kinds as in list
- `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
- `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
- `create_pull_request`: Open any change as a draft PR on a new branch in one of the repos connected to Fictura. Optionally tie it to an issue. Nothing under .github/. Needs "Let MCP ke
- `create_ticket`: Create a ticket for an error issue in GitHub Issues, Linear or Jira (connected on the Tools tab). The body is short and redacted. One GitHub issue per error iss
- `create_tracking_link`: Creates 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 insta
- `delete_inbound_filter`: Stop dropping what one inbound filter matches; new events land again within 30 seconds. Events it already dropped are not recovered. Take the id from list_inbou
- `edit_draft_onboarding`: Edit a draft onboarding flow (never live version).
- `edit_draft_paywall`: Edit a draft paywall (never live version).
- `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
- `get_acquisition_report`: `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 
- `get_ai_usage`: Model calls by model (gen_ai spans): calls, per minute, error rate, p50 to p99, total time, input and output tokens; and MCP tool calls by tool (mcp.server span
- `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_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_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
- `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_attribution_report`: Where 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;
- `get_endpoint_summary`: Everything about one row of the Performance page, to answer 'why is this slow?': count, error rate, p50 to p99 and the change against the window before; where t
- `get_error_event`: One occurrence: frames with source lines and variables, request, tags, contexts, breadcrumbs, causes and trace id. Pass issue_id for its latest event, or event_
- `get_error_issue`: One 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 
- `get_error_issue_brief`: Use 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 
- `get_error_settings`: This app's error settings (auto-resolve days, built-in noise rules, crash-free threshold, digest, code links, retention, whether MCP may write) and tracing sett
- `get_event_analytics`: One 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, previou
- `get_experiment`: One experiment with its variants and full Bayesian results.
- `get_fix_run`: A fix run's status, root cause, plan, files, tests, cost so far, and its pull request.
- `get_issue_activity`: What people and Fictura did to one issue, newest first: status changes, assignments, priority, notes with their text, tickets, regressions. Use it before changi
- `get_issue_tag_values`: How 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, logg
- `get_jobs`: Work done outside requests: background tasks, queue publish and process, and cron runs, with counts, failures and timings; each cron with its last run, its usua
- `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_mobile_vitals`: The mobile app's vitals from real devices: cold (and warm) app start, time to initial display (ttid) and full display (ttfd), slow and frozen frame percentages,
- `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
- `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
- `get_performance_overview`: How fast the app is right now, backend and frontend: backend requests per minute, p95 and error rate against the window before; screen and page load times; then
- `get_pull_request_status`: The PRs tied to an issue (opened by Fictura or linked), with state, draft, CI checks, merge and the release that shipped it.
- `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
- `get_setup_status`: Where 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 t
- `get_setup_step`: What 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 th
- `get_span`: One span in full: name, op, service, timing, status, every attribute, the errors that happened in it, and the log lines written while it ran. Take the trace_id 
- `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
- `get_surface`: The 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 giv
- `get_trace`: One trace (app → backend → dependencies) as a tree: names, services, start offsets, durations, HTTP status and errors, plus the error events linked to it. Take 
- `get_tracing_health`: Who is sending traces in the last 24 hours: each service with its SDK and version, frontend or backend, last span, span count, average sample rate and environme
- `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 
- `get_uptime_monitor`: The URL Fictura pings every minute for this app, whether it is up or down, the last check, consecutive failures, when the current downtime started, and availabi
- `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 
- `get_web_vitals`: The web app's Core Web Vitals from real browsers: a 0 to 100 performance score (LCP 30%, INP 30%, CLS 15%, FCP 15%, TTFB 10%, Google's thresholds), each vital's
- `link_pull_request`: Tie an existing GitHub PR (by URL) to an issue. When it merges, Fictura resolves the issue in the release that ships it. Only works when the app allows MCP writ
- `list_alert_rules`: This app's alert rules with their triggers, conditions, channels and throttles. defaults_active means no rule is enabled, so the built-in defaults listed there 
- `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 funnel per creator for the last 28 days in the app's time zone (non-bot clicks, installs split exact / weak / modelled, trials, paying us
- `list_dependencies`: The HTTP hosts and database tables the app's services call, by total time spent: calls, calls per minute, error rate, p50 to p99, 4xx and 5xx. kind http, db or 
- `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
- `list_error_alerts`: Every error alert Fictura fired, newest first: when, which trigger, the issue and its source, the channels, and whether it was delivered. Use it to check an ale
- `list_error_issues`: Start 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 activ
- `list_experiments`: Every experiment with status and, for running or finished ones, full Bayesian results — exposures, conversions, and the probability each variant is best.
- `list_inbound_filters`: This app's inbound filters: rules that drop a matching error at ingest, counted but never stored or alerted on. exc_type and release match exactly, message is a
- `list_monitors`: Every performance monitor: what it watches (metric, ops, route), its threshold and window, and its state (ok, firing, no_data) with the last value read. A firin
- `list_releases`: Releases from the app and the backend, newest first: crash-free sessions, users and adoption for the app, crash-free and error-free requests for the backend. Us
- `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_surfaces`: Every paywall and onboarding flow, what is actually being served at each placement (running experiment > live > none), and the valid placement names. IMPORTANT:
- `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_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
- `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
- `pause_experiment`: Pause 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
- `read_attribution`: Read attribution data from your Fictura app.
- `read_deep_link_config`: Read deep-link configuration from your Fictura app.
- `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
- `read_documentation`: Read Fictura documentation for the agent.
- `read_errors`: Read error issues from your Fictura app.
- `read_experiments`: Read experiments from your Fictura app.
- `read_funnel`: Read funnel configuration from your Fictura app.
- `read_paywalls`: Read live paywalls from your Fictura app.
- `read_users`: Read users from your Fictura app.
- `resume_experiment`: Resume 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.
- `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
- `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 
- `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 
- `search_error_events`: Single 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
- `search_error_issues`: Find 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 
- `search_logs`: Application log lines from the backend SDK, newest first, or counts with group_by. Use it to see what happened around an error: pass trace_id for one request's 
- `search_traces`: With no filters: every route and screen with its count, error rate, p50, p95 and slowest dependency. With any filter: matching spans from the backend and the ap
- `set_uptime_monitor`: Set or replace the URL Fictura pings every minute (three failures in a row mark it down and alert). A new URL starts over as unknown. enabled false pauses it. O
- `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
- `start_experiment`: Start 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 place
- `start_fix_run`: Start a hosted fix run: Fictura's AI finds the root cause and, if allowed, opens a draft PR. It spends the app's own Anthropic money, capped per run and per day
- `stop_experiment`: Stop 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
- `unpair_editor`: Stops this pairing. The editor shows that the agent left.
- `update_app_identity`: Saves 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 
- `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
- `update_error_issues`: The same change on up to 100 issues: resolve, ignore or reopen them, assign them, set their priority, or add a note to each. Answers per issue, with counts. Onl
- `update_tracing_settings`: Set the share of traces the SDKs keep, and the hosts the app's SDK sends trace headers to (replacing the list). A field you leave out keeps its value. SDKs read
- `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.
- `validate_paywall_doc`: Runs a document through the same parser and renderer a save uses and reports what is wrong, if anything. Changes nothing.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
