VibesAnalytics is analytics built for the agent era. Instead of clicking through dashboards, your AI coding agent talks to VibesAnalytics over MCP, registers your site, connects providers, and gets back one structured contract describing exactly what to track. This guide gets you from zero to a connected project.
What you need
- A Next.js (or React) site — ideally one your agent helped build.
- An AI coding agent that speaks MCP (Claude Code, Codex, or any MCP client).
- A VibesAnalytics workspace (free for up to 2 projects, no credit card).
1. Connect the MCP server
VibesAnalytics 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 VibesAnalytics 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 site. Under the hood it calls create_project with the site name, platform_type (web), framework (e.g. nextjs), and app_type (the business model, e.g. subscription). Each site you ship is one project inside your workspace.
3. Connect providers
Connect the analytics and ad platforms you use — GA4, Meta Pixel, TikTok, LinkedIn. VibesAnalytics auto-discovers your properties and pixels so there's no manual ID hunting. See the Providers guides for each one.
4. Get the integration contract
Have your agent call get_integration_contract. It returns the full tracking blueprint: the canonical events to fire, how each maps to every connected provider, the SDK setup, the env vars to inject, and a validation checklist. Your agent reads it and wires up tracking — no copy-pasting from dashboards.
5. Verify
Call validate_tracking to confirm events are actually flowing and every provider is connected. Then run refresh_project_metrics and read get_project_product_summary — your numbers appear immediately.
One thing to expect: trends and trend-based insights compare each period against the one before it, so they're empty for the first few days until a baseline builds up. An empty trend (or an empty insights list) on day one is normal — not a broken setup. The product summary's data_maturity field tells you when comparisons will kick in.