Fictura MCP server
Provides access to App Store subscription products and App Store analytics within Fictura, letting agents inspect store products and app performance alongside funnels, experiments, and attribution data.
Enables AI agents to integrate Fictura into Expo apps by reading the app's real SDK key and API base, consulting Fictura docs and existing placements, and writing paywall/onboarding integration code without placeholders.
Provides Google Play analytics within Fictura's mobile growth platform, enabling agents to query store performance alongside funnels, experiments, attribution, and crash data.
Supports React Native apps by helping agents integrate Fictura's SDK and place paywalls or onboarding flows at the correct placements within the app.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fictura MCP serverCreate a draft annual paywall from a template so I can review it"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Fictura is the growth platform for Expo and React Native apps: paywalls and onboarding flows built in the Studio editor, subscription analytics and funnels, A/B experiments, attribution and ad spend, deep links, App Store and Google Play analytics, and error tracking with stack traces. This server puts all of it in reach of Claude, ChatGPT, Codex, Cursor, VS Code, Windsurf, Gemini CLI and any other MCP client.
https://mcp.fictura.co/mcpStreamable HTTP, stateless, JSON responses. https://api.fictura.co/mcp serves the same server.
What your agent can do
Ask | What happens |
"Add Fictura to this Expo app and show the onboarding flow at the right placement." | Reads the app's real SDK key and API base ( |
"Why did trial-to-paid drop last week? Show me where people leave the funnel." | Pulls the funnel with drop-off per step and compares cohorts ( |
"Fix the top crash in the latest release." | Finds the issue, reads its source-mapped stack, breadcrumbs and a fix prompt ( |
"Draft an annual-plan paywall from a template so I can review it in Studio." | Picks a real template ( |
More: "Which campaigns paid back this month?" (get_acquisition_report), "Which experiment is winning, and how sure are we?" (list_experiments), "Are Universal Links set up right?" (get_link_infrastructure).
Related MCP server: KrystalView MCP Server
Connect
One-click
Both buttons add the URL only; sign in with your Fictura account when the editor asks. If the buttons do nothing on your system, open these links directly:
cursor://anysphere.cursor-deeplink/mcp/install?name=fictura&config=eyJ1cmwiOiJodHRwczovL21jcC5maWN0dXJhLmNvL21jcCJ9
vscode:mcp/install?%7B%22name%22%3A%22fictura%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.fictura.co%2Fmcp%22%7DClaude (claude.ai, Claude Desktop, Cowork)
Open Customize → Connectors, select + Add, then Add custom connector.
Name it
Fictura, pastehttps://mcp.fictura.co/mcpand select Continue.Keep the detected sign-in settings, select Add, then connect and sign in with Fictura. To use an MCP key instead, choose No sign in and add the key under Request headers as
X-API-Key.
On Team and Enterprise plans an Owner adds the connector first under Organization settings → Connectors, then each member connects.
ChatGPT
Go to chatgpt.com/plugins, select +, then Add custom MCP server.
Enter
https://mcp.fictura.co/mcpand choose OAuth for authentication.Select Create as a plugin, then sign in with Fictura.
Your account or workspace policy must allow custom MCP servers.
Claude Code
Install the plugin from this repository. It adds the server and a skill that makes Claude read your app's real setup before it writes integration code:
claude plugin marketplace add Apex-Byte-Technologies/fictura-mcp
claude plugin install fictura@ficturaOr add only the server:
claude mcp add --transport http fictura https://mcp.fictura.co/mcpThen run /mcp, pick fictura and sign in. To use an MCP key instead:
claude mcp add --transport http fictura https://mcp.fictura.co/mcp \
--header "X-API-Key: $FICTURA_MCP_KEY"Codex (CLI, IDE extension, ChatGPT desktop app)
codex mcp add fictura --url https://mcp.fictura.co/mcp
codex mcp login ficturaWith an MCP key instead of sign-in, keep the key in an environment variable:
export FICTURA_MCP_KEY=fk_mcp_...
codex mcp add fictura --url https://mcp.fictura.co/mcp --bearer-token-env-var FICTURA_MCP_KEYThe same thing in ~/.codex/config.toml:
[mcp_servers.fictura]
url = "https://mcp.fictura.co/mcp"
bearer_token_env_var = "FICTURA_MCP_KEY"Cursor
Use the button above, or add this to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"fictura": {
"url": "https://mcp.fictura.co/mcp"
}
}
}With an MCP key, add "headers": { "X-API-Key": "${env:FICTURA_MCP_KEY}" } to the fictura entry.
VS Code
Use the button above to sign in with Fictura. To use an MCP key instead, add this to .vscode/mcp.json; VS Code asks for the key once and stores it securely.
{
"inputs": [
{
"type": "promptString",
"id": "fictura-mcp-key",
"description": "Fictura MCP key (fk_mcp_...)",
"password": true
}
],
"servers": {
"fictura": {
"type": "http",
"url": "https://mcp.fictura.co/mcp",
"headers": { "X-API-Key": "${input:fictura-mcp-key}" }
}
}
}Windsurf
Open the Cascade panel's ... menu, then Open MCP config file, and add:
{
"mcpServers": {
"fictura": {
"serverUrl": "https://mcp.fictura.co/mcp",
"headers": { "X-API-Key": "${env:FICTURA_MCP_KEY}" }
}
}
}Gemini CLI
gemini extensions install https://github.com/Apex-Byte-Technologies/fictura-mcpThe installer asks for an optional MCP key and keeps it in your system keychain. Change it later with gemini extensions config fictura.
Claude Desktop with a local bridge (npx)
For clients that only run local (stdio) servers, the @fictura/mcp package bridges to the hosted server. In Claude Desktop, open Settings → Developer → Edit Config and add:
{
"mcpServers": {
"fictura": {
"command": "npx",
"args": ["-y", "@fictura/mcp"],
"env": { "FICTURA_MCP_KEY": "fk_mcp_..." }
}
}
}The bridge reads FICTURA_MCP_KEY and, optionally, FICTURA_API_BASE (default https://api.fictura.co). Claude Desktop also supports the custom connector above, which needs no local install.
Authentication
Option | How | Best for |
Sign in with Fictura (OAuth 2.1) | Add the URL only. Your client opens Fictura's sign-in; on the consent screen you pick one app and an access level (read, or read and edit drafts). | Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code |
MCP key | Create one in the Fictura dashboard under Setup → Coding agents (MCP). Send it as | CI, scripts, clients without MCP sign-in |
None | Connect without signing in. | Reading the Fictura docs before you have an account |
Without sign-in or a key, only the three documentation tools work: search_docs, list_docs and read_doc. Every other tool answers with how to connect.
A key is read-only unless you tick Can edit draft paywalls when you create it (those keys start with fk_mcpw_). The AppsFlyer import needs a key created with Can connect and import data. App data over MCP needs an active Fictura subscription with AI access.
Tools
44 tools and one prompt. "Read" tools change nothing.
Area | Tool | What it does | Access |
Docs |
| Search Fictura documentation | No sign-in |
Docs |
| List Fictura documentation pages | No sign-in |
Docs |
| Read a Fictura documentation page | No sign-in |
Setup |
| Get this app's Fictura credentials and endpoints | Read |
Setup |
| Get integration and feature status | Read |
Setup |
| List App Store subscription products | Read |
Setup |
| Get deep link and tracking domain configuration | Read |
Setup |
| Get push notification configuration | Read |
Analytics |
| Get funnel, overview or cohort analytics | Read |
Analytics |
| Get the event tracking plan | Read |
Users |
| List users | Read |
Users |
| Get one user's full history | Read |
Users |
| Check whether a user is subscribed | Read |
Paywalls & onboarding |
| List paywalls, onboarding flows and placements | Read |
Paywalls & onboarding |
| Get one paywall or onboarding flow's config | Read |
Paywalls & onboarding |
| List built-in paywall and onboarding templates | Read |
Paywalls & onboarding |
| Get a Studio paywall's document | Read |
Paywalls & onboarding |
| Check a paywall document without saving it | Read |
Paywalls & onboarding |
| Save a DRAFT paywall's document | Edit drafts |
Paywalls & onboarding |
| Create a new DRAFT Studio paywall | Edit drafts |
Paywalls & onboarding |
| Get an onboarding flow's document | Read |
Paywalls & onboarding |
| Check an onboarding document without saving it | Read |
Paywalls & onboarding |
| Save a DRAFT onboarding flow's document | Edit drafts |
Paywalls & onboarding |
| Create a new DRAFT onboarding flow | Edit drafts |
Studio editor |
| Pair with an open Studio editor | Read |
Studio editor |
| Read the document open in the paired editor | Read |
Studio editor |
| Put a document on the paired editor's canvas (not saved) | Edit drafts |
Studio editor |
| End the pairing with the editor | Read |
Experiments |
| List experiments | Read |
Experiments |
| Get one experiment | Read |
Acquisition |
| Get attribution, install and KPI reporting | Read |
Acquisition |
| Get paid acquisition performance | Read |
Acquisition |
| List live ad campaigns | Read |
Acquisition |
| List creators and their performance | Read |
Store |
| Get App Store and Google Play analytics (Appfigures) | Read |
Errors |
| List error issues | Read |
Errors |
| Search error issues | Read |
Errors |
| Get one error issue with stack traces | Read |
Errors |
| Get an issue brief and a fix prompt | Read |
Errors |
| Change an error issue | Write, if the app allows it |
Errors |
| Get one distributed trace | Read |
AppsFlyer import |
| Get AppsFlyer import status | Read |
AppsFlyer import |
| Start the AppsFlyer import | Write, import key |
AppsFlyer import |
| Summarize imported AppsFlyer attribution | Read |
Prompt: integrate_fictura_sdk (Integrate the Fictura SDK) walks the agent through wiring @fictura/sdk into an Expo / React Native app with the app's real credentials.
Security
The app comes from your sign-in or key, never from the agent. No tool takes an app id, so there is no argument an agent could pass to read another app's data. A sign-in reaches only the one app you chose on the consent screen.
Drafts never go live. The paywall and onboarding tools create and edit drafts only. Saving a live paywall or flow is refused, and going live is a click in the Fictura dashboard. Every save is a new version you can roll back; the history marks it
mcp: <note>.The editor stays yours.
editor_set_docchanges the canvas of a Studio editor you paired with a one-time code. It does not save; you see the change, can undo it, and save it yourself.Other writes are opt-in.
update_error_issueworks only after you turn on Let MCP keys change issues in the app's Issues settings.start_appsflyer_importneeds a key created with Can connect and import data.Revocation is immediate. A revoked or invalid key is rejected on its next request with an error, never silently downgraded.
Keep keys out of code. MCP keys (
fk_mcp_...) read revenue and user data: store them in environment variables or your client's secret storage, never in a repository. The SDK key thatget_app_setupreturns (gk_...) is different: it is publishable and safe to ship in your app.
Report a vulnerability as described in SECURITY.md.
This repository
This repository holds the public listing files for the hosted server. The server itself runs at Fictura; there is no server code here.
Path | What it is |
Entry for the official MCP Registry as | |
Claude Code plugin marketplace and plugin | |
Cursor plugin | |
Gemini CLI extension | |
ChatGPT and Codex plugin bundle; build the upload ZIP with | |
Icons (SVG, and PNG at 48, 128, 256, 400 and 512 px) |
Links
Documentation: https://docs.fictura.co/connections/outgoing/mcp-server
Website: https://fictura.co
Privacy policy: https://fictura.co/privacy
Terms: https://fictura.co/terms
Support: https://fictura.co/contact or info@fictura.co
License
MIT © Apex Byte Technologies
This server cannot be deployed
Maintenance
Related MCP Connectors
Set up and inspect app paywalls, subscriptions, offerings and analytics from your AI agent.
Analyze and manage Apple Ads from your AI assistant with RevenueCat insights and safety controls.
Live App Store and Google Play data for AI agents: revenue and download estimates for 3.6M+ apps, app search and filters, ASO keyword research, reviews and listing change history. Read-only tools; API key from GetAppNiche (https://getappniche.com/mcp).
AI-agent operations for App Store Connect and Google Play, with approval before live publishing.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access App Store Connect data including financial metrics, subscription analytics, app performance data, and revenue insights. Provides real-time iOS app metrics through secure API integration with rate limiting and comprehensive reporting capabilities.12 npm36MIT
- AlicenseAqualityDmaintenanceEnables AI agents to access website analytics, including visitor sessions, UX friction, conversion funnels, and anomaly alerts.637 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to research mobile apps, compare onboarding and paywall flows, explore App Store reviews, and find visual UI references, bringing real screens and market context into their research.3MIT

AppmanAi MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query live App Store and Google Play data — keyword demand, rank history, top charts, competitor sets, reviews and ratings — across 100+ countries, directly inside a chat instead of a dashboard. Exposes 35 read-only tools covering app search, ASO keyword profiling, ranking trajectories, and worldwide market comparisons through a remote OAuth-authenticated endpoint.2MIT