{"id":"co.fictura/mcp","slug":"co-fictura-mcp","title":"Fictura","description":"Paywalls, onboarding, subscription analytics, A/B tests, attribution and errors for mobile apps.","version":"0.1.2","publisher":{"kind":"domain","id":"fictura.co","label":"fictura.co","url":"https://fictura.co"},"website":"https://docs.fictura.co/connections/outgoing/mcp-server","repository":"https://github.com/Apex-Byte-Technologies/fictura-mcp","remotes":[{"type":"streamable-http","url":"https://mcp.fictura.co/mcp","headers":[{"description":"Optional Fictura MCP key (fk_mcp_...) from Dashboard > Setup > Coding agents (MCP). Leave it out to sign in with your Fictura account (OAuth) instead.","isSecret":true,"name":"X-API-Key"}]}],"packages":[{"registryType":"npm","registryBaseUrl":"https://registry.npmjs.org","identifier":"@fictura/mcp","version":"0.1.2","transport":{"type":"stdio"},"environmentVariables":[{"description":"Fictura MCP key (fk_mcp_...) from Dashboard > Setup > Coding agents (MCP). Leave it out to sign in with your Fictura account in the browser instead. The documentation tools work either way.","format":"string","isSecret":true,"name":"FICTURA_MCP_KEY"},{"description":"Override the Fictura API base URL. Leave unset unless Fictura support asks you to change it.","format":"string","default":"https://api.fictura.co","name":"FICTURA_API_BASE"}]}],"published":"2026-10-29","updated":"2026-10-29","status":"online","auth":"","latency_ms":926,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"search_docs","title":"Search Fictura documentation","description":"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 change. Returns page paths; pass one to read_doc for the full text. No API key required.","read_only":true},{"name":"list_docs","title":"List Fictura documentation pages","description":"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_only":true},{"name":"read_doc","title":"Read a Fictura documentation page","description":"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 API key required.","read_only":true},{"name":"get_app_setup","title":"Get this app's Fictura credentials and endpoints","description":"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 in what you write. The SDK key is publishable and safe to commit in app source; it identifies the app, not a person.","read_only":true},{"name":"get_setup_step","title":"Get the instructions for one setup step","description":"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 that step's docs pages, and how to check it worked. Call this when a person pastes a setup prompt, and follow what it returns rather than recalling the SDK from memory. Steps in order: install, connect, events, attribution, errors, performanc","read_only":true},{"name":"get_setup_status","title":"Get setup progress, integrations and feature status","description":"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 toggle and whether it is on, and which third-party integrations (Stripe, RevenueCat, Slack, App Store Connect, …) are connected. Use it to check a setup step worked, and to check a feature is enabled before writing code that depends on it — ","read_only":true},{"name":"update_app_identity","title":"Save this app's bundle ID, Team ID and store details","description":"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 fingerprints (which build the App Links file), both store addresses and the website. Send only the fields you know. Every value is checked before saving, because a bad one makes links fail with no error anywhere. A value already saved is no","read_only":false},{"name":"create_tracking_link","title":"Create a tracking link","description":"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 install is credited to the link. A tap from a computer goes to desktop_url instead, or to the app's website when destination_url is a store page. Use the store address for a real campaign, or the app's own scheme (myapp://) for a link that opens","read_only":false},{"name":"get_analytics","title":"Get funnel, overview or cohort analytics","description":"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 across billing outcomes — what converted users did that cancelled users didn't. Below ~100 users in a step the sample is too small to read. `stores` splits payi","read_only":true},{"name":"get_attribution_report","title":"Get attribution, install and KPI reporting","description":"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; server-only users are never installs. Non-organic = installs with an attribution that is exact (store referrer, Apple Ads, claimed or opened link, clipboard, code, product page, ad id), weak (UTM only) or modelled (Android/web IP match wit","read_only":true},{"name":"list_users","title":"List users","description":"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 does not flood the context; `total` reports how many matched before the cap.","read_only":true},{"name":"get_user","title":"Get one user's full history","description":"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.","read_only":true},{"name":"check_entitlement","title":"Check whether a user is subscribed","description":"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 test purchases, so always check it before granting production access; a cancellation only flips will_renew (access runs to expires_at); and an unknown user is a ","read_only":true},{"name":"get_tracking_plan","title":"Get the event tracking plan","description":"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 same string an experiment later names as its primary metric.","read_only":true},{"name":"get_event_analytics","title":"Read a tab of the Events page","description":"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, previous count, worked and failed, plus key events. screens: views, users and time per screen. taps: taps per screen and element. broken_taps: dead and rage taps. sessions: length, bounce, entry and exit screens, platforms, versions, recent sessio","read_only":true},{"name":"list_surfaces","title":"List paywalls, onboarding flows and placements","description":"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 configured ∪ observed, so a name that appears only under `observed` is usually a typo in the app — and a placement that does not exist renders nothing at all, with ","read_only":true},{"name":"get_surface","title":"Get one paywall or onboarding flow's config","description":"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 gives its size) and a Studio doc shows as doc: true; read the design with get_paywall_doc or get_onboarding_doc. Note that configs never contain price strings — prices resolve at render time from the PurchasesAdapter's packages, so never copy ","read_only":true},{"name":"list_templates","title":"List built-in paywall and onboarding templates","description":"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.","read_only":true},{"name":"list_experiments","title":"List experiments","description":"Every experiment with status and, for running or finished ones, full Bayesian results — exposures, conversions, and the probability each variant is best.","read_only":true},{"name":"get_experiment","title":"Get one experiment","description":"One experiment with its variants and full Bayesian results.","read_only":true},{"name":"create_experiment","title":"Create a draft experiment","description":"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 surface (ids from list_surfaces); one arm may be a holdout with no target (it keeps the live config). Exactly one control; the first arm when none is marked. Defaults: mode notify (report the winner, don't ship it), new users only, the def","read_only":false},{"name":"start_experiment","title":"Start an experiment","description":"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 placement. Only works when the app allows MCP writes.","read_only":false},{"name":"pause_experiment","title":"Pause an experiment","description":"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_only":false},{"name":"resume_experiment","title":"Resume an experiment","description":"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.","read_only":false},{"name":"stop_experiment","title":"Stop an experiment","description":"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 a person in the dashboard. Only works when the app allows MCP writes.","read_only":false},{"name":"get_acquisition_report","title":"Get paid acquisition performance","description":"`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, CAC and ROAS = net cohort revenue ÷ spend — the same numbers as get_attribution_report kpis grouped by campaign. `blended` is the whole app by payment date and `unattributed` the ","read_only":true},{"name":"get_store_analytics","title":"Get App Store and Google Play analytics (Appfigures)","description":"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 category chart positions. Money is in micros of `currency`. Store revenue is a separate figure from RevenueCat revenue; never add the two. Returns connected: false ","read_only":true},{"name":"list_campaigns","title":"List live ad campaigns","description":"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 historical numbers.","read_only":true},{"name":"list_creators","title":"List creators and their performance","description":"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 users, cohort net revenue and ROAS against the deal cost) and the tracking links tagged to each.","read_only":true},{"name":"get_link_infrastructure","title":"Get deep link and tracking domain configuration","description":"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 ios_ready and android_ready. Get these wrong and BOTH files fail SILENTLY — they parse, associate nothing, report no error, and links simply keep opening the br","read_only":true},{"name":"get_push_config","title":"Get push notification configuration","description":"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 recipients.","read_only":true},{"name":"list_store_products","title":"List App Store subscription products","description":"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 ladder for that one product (Apple scopes price points per subscription, so there is no global list).","read_only":true},{"name":"list_error_issues","title":"List error issues","description":"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 activity first, unresolved only. Console lines from the app are hidden unless include_console is true. Pass next_cursor to read on.","read_only":true},{"name":"search_error_issues","title":"Search error issues","description":"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 and rows as list_error_issues.","read_only":true},{"name":"search_error_events","title":"Search error events","description":"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 failed in one trace. Open one with get_error_event.","read_only":true},{"name":"get_error_event","title":"Get one error event in full","description":"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_id. Use it to see why one error happened. Long events give up variables, then library frames, then breadcrumbs, and `truncated` says what went: call again with section to read that part whole.","read_only":true},{"name":"get_error_issue","title":"Get one error issue","description":"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 summaries. Use it to see how an issue behaves over time. For a fix, get_error_issue_brief is shorter; for source lines and variables, use get_error_event.","read_only":true},{"name":"get_error_issue_brief","title":"Get an issue brief and a fix prompt","description":"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 the same trace, facets (release, OS, device, route), cause chain, and a ready-to-use fix prompt.","read_only":true},{"name":"get_issue_tag_values","title":"Count the values of one tag on an issue","description":"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, logger or person. Leave out key to list the keys there are.","read_only":true},{"name":"get_issue_activity","title":"Get an issue's history","description":"What 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.","read_only":true},{"name":"search_logs","title":"Search log lines","description":"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 lines, or q and level to search. Lines are kept 14 days, and the default range is the last 24 hours.","read_only":true},{"name":"search_traces","title":"Search spans and slow routes","description":"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 app, or count, avg, p50, p95 and errors with group_by. Use it to find what is slow or failing, then open one with get_trace. Spans are kept 30 days.","read_only":true},{"name":"get_trace","title":"Get one distributed trace","description":"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 the trace_id from an event or from search_traces. Use it to see where the time went or what failed first. Long traces page with next_cursor.","read_only":true},{"name":"list_error_alerts","title":"List alerts that fired","description":"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 alert went out, or what paged someone.","read_only":true},{"name":"list_alert_rules","title":"List alert rules","description":"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 apply. Use it to see what will and won't alert.","read_only":true},{"name":"list_releases","title":"List releases and their health","description":"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. Use it to tell whether a release made things worse. crashed_sessions counts crashes and bad exits; abnormal_sessions is the bad exits (no crash report, an AbnormalExit issue). `release` (version+build) is the name every tool takes.","read_only":true},{"name":"update_error_issue","title":"Change an error issue","description":"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).","read_only":false},{"name":"update_error_issues","title":"Change several error issues","description":"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. Only works when the app allows MCP writes (Issues settings → Let MCP keys change issues).","read_only":false},{"name":"list_inbound_filters","title":"List inbound filters","description":"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 glob (* = anything, any case), environment is exact and `simulator` also drops simulator events. discarded_7d counts drops per reason.","read_only":true},{"name":"create_inbound_filter","title":"Add an inbound filter","description":"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_inbound_filters; environment `simulator` drops events from simulators and emulators. Refuses an exact duplicate. Only works when the app allows MCP writes.","read_only":false},{"name":"delete_inbound_filter","title":"Delete an inbound filter","description":"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_inbound_filters. Only works when the app allows MCP writes.","read_only":false},{"name":"get_uptime_monitor","title":"Get the uptime monitor","description":"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 availability over 24 hours and 7 days. monitor is null when none is set.","read_only":true},{"name":"set_uptime_monitor","title":"Set the uptime monitor","description":"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. Only works when the app allows MCP writes.","read_only":false},{"name":"get_error_settings","title":"Get error and tracing settings","description":"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 settings (sample rate, hosts that get trace headers). connection_can_write says whether this connection's write tools will work.","read_only":true},{"name":"update_tracing_settings","title":"Change tracing settings","description":"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 it from their config within a minute. Only works when the app allows MCP writes.","read_only":false},{"name":"get_performance_overview","title":"Performance overview","description":"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 the routes that take the most total time, the slowest screens and pages, and the slowest dependencies (HTTP hosts, database tables). Start here, then open one with get_endpoint_summary.","read_only":true},{"name":"get_endpoint_summary","title":"Explain one route, screen or dependency","description":"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 the time goes inside each request (database, HTTP and model calls, and the backend routes a screen waited on); what the slowest 10% have that the rest don't (release, status, device…) and which inner spans grow most in them; who calls a depe","read_only":true},{"name":"list_dependencies","title":"List dependencies by time spent","description":"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 all (default). Open one with get_endpoint_summary (op http.client or db).","read_only":true},{"name":"get_span","title":"Get one span","description":"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 and span_id from get_trace.","read_only":true},{"name":"get_ai_usage","title":"AI model and MCP tool calls","description":"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 spans). Prompt and completion text is never stored, so it is never here.","read_only":true},{"name":"get_jobs","title":"Background tasks, queues and crons","description":"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 usual gap, and late: true when it has not run for twice that gap.","read_only":true},{"name":"compare_releases","title":"Compare two releases","description":"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: what got slower or faster. Also what appears in only one of them. Take release names from list_releases or get_tracing_health; package@version+build works too, and a version alone is every build of it.","read_only":true},{"name":"get_web_vitals","title":"Web vitals","description":"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 p75 with its good / needs improvement / poor counts, and pages ranked by opportunity (how much the score would rise if that page scored 100).","read_only":true},{"name":"get_mobile_vitals","title":"Mobile vitals","description":"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, and JS stall time; overall, per screen (busiest first) and per release. Each with p50, p75, p95 and the sample count. platform ios, android or both (default).","read_only":true},{"name":"list_monitors","title":"List performance monitors","description":"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 firing monitor has an open issue: issue_id opens with get_error_issue.","read_only":true},{"name":"get_tracing_health","title":"Is tracing working?","description":"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 environments; how many of the app's traces reached a backend (joined traces: zero means the app is not sending traceparent to the API, or the backend is not traced); what span ingest refused per day this week (invalid, rate limited, over the daily q","read_only":true},{"name":"create_ticket","title":"File an error issue in GitHub, Linear or Jira","description":"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 issue. Only works when the app allows MCP writes.","read_only":false},{"name":"link_pull_request","title":"Link a pull request to an error issue","description":"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 writes.","read_only":false},{"name":"create_fix_pr","title":"Open a draft fix PR for an error issue","description":"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 build, CI or .github changes. Needs \"Let MCP keys open pull requests\".","read_only":false},{"name":"create_pull_request","title":"Open a draft pull request","description":"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 keys open pull requests\".","read_only":false},{"name":"get_pull_request_status","title":"Pull requests for an error issue","description":"The PRs tied to an issue (opened by Fictura or linked), with state, draft, CI checks, merge and the release that shipped it.","read_only":true},{"name":"start_fix_run","title":"Ask Fictura's AI to fix an error issue","description":"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. Poll get_fix_run. Needs MCP writes and AI fixes on.","read_only":false},{"name":"get_fix_run","title":"Progress of an AI fix run","description":"A fix run's status, root cause, plan, files, tests, cost so far, and its pull request.","read_only":true},{"name":"get_paywall_doc","title":"Get a Studio paywall's document","description":"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 — keep node ids, change only what was asked. Prices are never typed: use {{ products.<slot>.price }} and the other product variables.","read_only":true},{"name":"validate_paywall_doc","title":"Check a paywall document without saving it","description":"Runs a document through the same parser and renderer a save uses and reports what is wrong, if anything. Changes nothing.","read_only":true},{"name":"save_paywall_doc","title":"Save a DRAFT paywall's document","description":"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. Products, translations and other settings are kept.","read_only":false},{"name":"create_paywall_draft","title":"Create a new DRAFT Studio paywall","description":"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.","read_only":false},{"name":"pair_editor","title":"Pair with an open Studio editor","description":"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 either side stops it.","read_only":false},{"name":"editor_get_doc","title":"Read the document open in the paired editor","description":"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 you got — keep node ids, change only what was asked.","read_only":true},{"name":"editor_set_doc","title":"Put a document on the paired editor's canvas","description":"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. Needs an MCP key that can edit.","read_only":false}],"server_info":{"name":"fictura","version":"1.0.0"},"category":"analytics","tags":["project","cloud","developer"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-10-29","stars":0,"badges":["new"],"sponsor":null,"page":"https://agentsindex.org/agents/co-fictura-mcp/"}