Analytics

vibesanalytics.com

Manages analytics projects, connects analytics/ad providers, and monitors their connection status.

1 endpoint27 known toolsFirst detected August 30, 2026Last detected August 30, 2026

ENDPOINT 1

https://vibesanalytics.com/api/mcp

No auth detected

MCP server metadata

Name: vibesanalytics
Version: 0.1.0

Capabilities

tools.listChangedprompts.listChanged

Server instructions

VibesAnalytics is a multi-source analytics control plane: it unifies your first-party (owned) events with GA4, Meta Ads, and Google Search Console, then produces metrics, insights, and digests. You (the agent) wire it up and read it back for the user. When the user wants analytics, tracking, conversions, traffic, SEO, or asks 'is anyone using my app' — LEAD with this setup sequence. If unsure what to do next, call vibetraker_get_setup_plan, which inspects project state and returns the ordered next steps + exact tool calls. Canonical first-run order: 1. Identity: if there's no API key, call vibes_register; then vibetraker_create_project for this app (set domain + app_type). 2. Instant win (no traffic needed): vibetraker_get_seo_scaffold for the domain — drop robots.txt + sitemap + llms.txt into the repo. You complete the sitemap from the app's real routes and fill llms.txt facts; the tool returns starters. 3. Tracking: vibetraker_get_integration_contract, then wire each canonical event at its call_site using the provided snippet (you read the codebase and place the calls). 4. Full multi-source setup — PROMPT the user to wire BOTH so they see real, full analytics, not just owned events: (a) GA4 via vibetraker_provision_ga4 (or connect_provider + list/attach_provider_asset); (b) Google Search Console via vibetraker_connect_provider, then vibetraker_submit_sitemap once verified. This is the standard setup, not optional enrichment — connecting Google covers both. Only skip a provider if the user explicitly declines (the OAuth grant is a user action you can't perform for them). 5. Verify: loop vibetraker_validate_tracking until required events report SEEN. 6. Report: vibetraker_refresh_project_metrics, then vibetraker_get_project_product_summary. Gotchas: the ingest event field is `event_name` (NOT name/event). The ingest_key (vt_ingest_*) is public/browser-safe — never send the secret vt_live_/vt_test_ key to ingest, and never put PII (emails/names) in event properties. Trends and trend-based insights compare to a prior period, so they fill over the first few days — empty on day one is normal, not broken.

Known tools 27

vibes_register

Create a workspace + API key.

Potential side effects

vibetraker_get_setup_plan

Inspect a project's real state (domain set?

Inferred read-only

vibetraker_create_project

Create a project (a site or app to track) and seed its canonical event schema.

Potential side effects

vibetraker_connect_provider

Connect an analytics/ad provider.

Inferred read-only

vibetraker_get_connection_status

List this workspace's provider connections and their status (pending_oauth, active, expired, error).

Inferred read-only

vibetraker_list_projects

List all projects in the workspace.

Inferred read-only

vibetraker_get_integration_contract

The install blueprint for a project: @vibetraker/js owned-events snippet, canonical events with call sites, and any connected provider (GA4) gtag install + mappings.

Inferred read-only

vibetraker_instrument_app

Return a ready-to-apply install kit so you can instrument this app in one pass: a dependency-free autocapture component (fires session_started + page_viewed automatically, ingest_key baked in, no npm install) plus the conversion track() calls to place at the app's REAL handlers (signup/purchase/etc).

Potential side effects

vibetraker_validate_tracking

Check which canonical events have fired recently.

Inferred read-only

vibetraker_get_workspace_overview

Headline metrics for every project in the workspace over a date range (default last 7 days).

Inferred read-only

vibetraker_get_workspace_insights

Recent insights across all projects in the workspace.

Inferred read-only

vibetraker_list_provider_assets

List discovered/attached provider assets (e.g.

Inferred read-only

vibetraker_attach_provider_asset

Attach a discovered asset (e.g.

Inferred read-only

vibetraker_provision_ga4

Create a NEW GA4 property + web data stream for a project's site and attach it.

Potential side effects

vibetraker_get_seo_scaffold

Generate robots.txt, sitemap.xml and llms.txt for the project's domain (classic SEO + AI-crawler/GEO).

Inferred read-only

vibetraker_get_project_insights

Recent insights for one project (tracking health, product, marketing).

Inferred read-only

vibetraker_provision_search_console

Start wiring Google Search Console for the project's domain.

Inferred read-only

vibetraker_verify_search_console

After the verification meta tag is live on the site, verify ownership, register the property in Search Console, and attach it.

Inferred read-only

vibetraker_get_project_metrics

Daily metric snapshots for a project over a date range (default last 7 days).

Inferred read-only

vibetraker_refresh_project_metrics

Roll up this project's owned events into daily metrics (and pull any connected GA4/Meta/Search Console/Stripe data) for a date range (default last 7 days), so the metrics and product/marketing summaries reflect what's happened.

Inferred read-only

vibetraker_generate_project_insights

Run the insight checks and build the daily summary for a project on a date (default today).

Inferred read-only

vibetraker_submit_sitemap

Submit (or re-submit) a sitemap to the project's verified Google Search Console property so Google discovers and crawls its pages.

Inferred read-only

vibetraker_get_project_product_summary

Product-focused metric summary (sessions, users, signups, trials, purchases, revenue) with period-over-period trends against the preceding equal-length period.

Inferred read-only

vibetraker_get_project_marketing_summary

Marketing-focused metric summary (spend, impressions, clicks, installs, CPI, CPC, CTR, CAC, ROAS) with period-over-period trends.

Inferred read-only

vibetraker_get_daily_summary

The pre-computed daily summary for a project: insight counts by severity plus product and marketing metrics with trends.

Inferred read-only

vibetraker_link_telegram

Mint a one-time deep link (t.me/<bot>?start=<code>) that links the user's Telegram chat to this workspace so they receive the morning analytics digest and alerts.

Inferred read-only

vibetraker_configure_telegram_alerts

Set the workspace's Telegram notification preferences: enable/disable the morning digest and per-source alerts (site-down, revenue, signup), set instant-alert thresholds (revenue floor, volume-rollup cutoff), digest hour/timezone, monitor URL, or mute for N minutes.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vibesanalytics]
url = "https://vibesanalytics.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "vibesanalytics": {
      "type": "http",
      "url": "https://vibesanalytics.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: vibesanalytics
Remote MCP URL: https://vibesanalytics.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "vibesanalytics": {
      "url": "https://vibesanalytics.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "vibesanalytics": {
      "type": "http",
      "url": "https://vibesanalytics.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "vibesanalytics",
  "transport": "streamable-http",
  "url": "https://vibesanalytics.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.