VibesFlyer is mobile analytics for the agent era. Instead of wiring SDKs by hand and learning each attribution dashboard, your AI coding agent talks to VibesFlyer over MCP, registers your app, connects Firebase and your MMP, and gets back one contract describing exactly what to track. This guide gets you to a connected project.
What you need
- An Expo or React Native app — ideally one your agent helped build.
- An AI coding agent that speaks MCP (Claude Code, Codex, or any MCP client).
- A VibesFlyer workspace (free for up to 2 projects, no credit card).
1. Connect the MCP server
VibesFlyer is a hosted MCP server — nothing to install. Point your agent at https://vibesanalytics.com/api/mcp and authenticate with your workspace API key (vt_live_*):
claude mcp add --transport http vibesanalytics https://vibesanalytics.com/api/mcp \
--header "Authorization: Bearer vt_live_YOUR_KEY"
Your agent now has tools like vibetraker_create_project, vibetraker_connect_provider, and vibetraker_get_integration_contract (every tool is namespaced with the vibetraker_ prefix; the bootstrap tool is vibes_register). See Connect the VibesFlyer MCP for Cursor / Windsurf / Claude Desktop config and how to get a key.
2. Register a project
Ask your agent to create a project for your app. It calls create_project with the app name, platform_type (mobile), framework (e.g. expo), and app_type (the business model, e.g. subscription). Each app is one project in your workspace — built for founders juggling several at once.
3. Connect providers
Connect Firebase for product analytics and AppsFlyer for attribution, plus any ad platforms (Meta, TikTok). VibesFlyer auto-discovers your apps and accounts. See the Providers guides for each.
4. Get the integration contract
Have your agent call get_integration_contract. It returns the full mobile tracking blueprint: the canonical lifecycle events to log, how each maps to every provider, the SDK setup, the env vars (e.g. FIREBASE_APP_ID, APPSFLYER_DEV_KEY), and a validation checklist. Your agent reads it and wires up tracking across all providers.
5. Verify
Call validate_tracking to confirm events fire and every provider is connected. On a real device (DebugView can lag), confirm the lifecycle events show up, then your normalized metrics and daily summaries begin populating.