@clarvivo/mcp
Related Servers
Alternatives to @clarvivo/mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenancePrivacy friendly, cookieless web analytics built MCP-first. "Add analytics to my Next.js app" → an AI agent runs the setup_analytics_for_site tool, picks the right install snippet, edits your layout file, and verifies the script is loading. OAuth onboarding, no API keys to paste.2851 npm1MIT

Taliviaofficial
AlicenseNot gradedqualityDmaintenanceRevenue-first website analytics that your AI agent can install, connect, and verify for you. Talivia shows founders which referrers, campaigns, pages, search keywords, and customer journeys turn visits into revenue. @talivia/agent connects Codex, Claude Code, ChatGPT, OpenClaw, Hermes, and other MCP clients to Talivia so an agent can finish the analytics setup inside your project47 npm32MIT
mimofficial
AlicenseNot gradedqualityAmaintenanceGives AI coding agents a project's growth context, exposing site audits, prioritized findings, live analytics, ad, search, and lifecycle marketing data, and session-replay insights so they can answer growth questions and recommend next steps. Also provides action tools to provision measurement, provision ad resources, and turn findings into reviewable code-fix workflows such as pull requests, diffs, and previews.68 npmMIT- AlicenseBqualityAmaintenanceEnables AI agents to plan and, only when writes are explicitly enabled, apply a site's Google Analytics 4 and Search Console measurement setup — property and web stream creation, key events, custom dimensions, DNS verification, sitemap submission and a PageSpeed baseline — while remaining read-only by default.2439 PyPI1MIT
- AlicenseBqualityDmaintenanceProvisions Google Analytics 4 for local AI/web projects by creating properties and web data streams, injecting gtag snippets, and saving configuration.14MIT
- AlicenseAqualityCmaintenanceGives Claude read access to Google Analytics 4, Google Search Console, and Microsoft Clarity data, with connections stored once and reusable across projects.8MIT
TDQS
Scored across 11 tools
Each tool targets a distinct responsibility: snippet retrieval, installation verification, project listing, stats, setup, revenue connection, revenue verification, event registration, funnel creation, alert creation, and funnel listing. The slight overlap between setup_analytics and get_install_snippet is differentiated by their detection vs retrieval purposes.
All tools follow a consistent verb_noun naming pattern using clear verbs (get, verify, list, setup, connect, add, create) and snake_case. There is no mixing of conventions or ambiguous verbs.
11 tools is well within the ideal range for a domain covering analytics setup, events, funnels, and alerts. Each tool provides a unique capability without redundancy or bloat.
The tool surface covers the full analytics lifecycle from installation and verification through stats, revenue, events, funnels, and alerts. Minor gaps exist in update/delete operations for configured items, but these are not critical for the primary use case.