Clarvivo MCP · v0.3.1
Install Clarvivo from Cursor, Claude Code, or Codex—without leaving your editor
The Clarvivo MCP server detects your app framework, sets up analytics, verifies real traffic, connects payment revenue, and manages events, funnels, reports, and exports from your coding agent.
Quick start
The 60-second flow
- 1
Sign in
Sign in to Clarvivo. New users create an API token right on the dashboard page after signing in; paying users create one in Settings → API tokens.
- 2
Add the server
Add the Clarvivo MCP server to your coding client with CLARVIVO_API_TOKEN in its environment.
- 3
Ask the agent
Paste: “Set up Clarvivo analytics for example.com.”
- 4
Apply and verify
Let the agent make the returned edit through your normal workflow, visit the deployed site, then ask it to verify the installation.
Configuration
Install in your coding client
Replace clv_live_REPLACE_ME with your token. Keep personal configuration files out of source control. Node.js 20 or newer is required.
Claude Code
This user-scoped command works from every project:
claude mcp add clarvivo --scope user \
--env CLARVIVO_API_TOKEN=clv_live_REPLACE_ME \
-- npx -y @clarvivo/mcpCursor
Create .cursor/mcp.json in a project, or ~/.cursor/mcp.json globally:
{
"mcpServers": {
"clarvivo": {
"command": "npx",
"args": ["-y", "@clarvivo/mcp"],
"env": {
"CLARVIVO_API_TOKEN": "clv_live_REPLACE_ME"
}
}
}
}Codex CLI
Add this to ~/.codex/config.toml:
[mcp_servers.clarvivo]
command = "npx"
args = ["-y", "@clarvivo/mcp"]
[mcp_servers.clarvivo.env]
CLARVIVO_API_TOKEN = "clv_live_REPLACE_ME"Or use the equivalent command:
codex mcp add clarvivo \
--env CLARVIVO_API_TOKEN=clv_live_REPLACE_ME \
-- npx -y @clarvivo/mcpGeneric MCP client
For clients using the common mcpServers shape:
{
"mcpServers": {
"clarvivo": {
"command": "npx",
"args": ["-y", "@clarvivo/mcp"],
"env": {
"CLARVIVO_API_TOKEN": "clv_live_REPLACE_ME"
}
}
}
}Need Windsurf, Cline, VS Code, or Zed? See the complete npm README.
Capabilities
All 15 tools
Setup
setup_analytics- Detect the framework, reuse a matching-domain project or create one, and return the exact installation edit.
get_install_snippet- Get framework-specific instructions for an existing API key or project.
verify_installation- Prove the deployed snippet works from a proof-of-life event count, without reading analytics.
list_projects- List accessible projects and their public tracking API keys.
Payments
connect_revenue- Detect Stripe, Polar, Razorpay, Paddle, Lemon Squeezy, or Dodo; connect its webhook; and return the attribution edit.
verify_revenue- Summarise webhook proof-of-life and attribution coverage without dumping payment data.
Events & funnels
add_event- Register an event and propose the window.clarvivo.trackEvent(...) edit and handler placement.
create_funnel- Create an ordered funnel or reuse one with the same name, then flag unmatched steps.
create_alert- Create a traffic or conversion alert, or reuse an alert of the same type.
list_funnels- List funnels and their ordered steps.
Read your data
get_stats- Return a small traffic and top-line revenue summary for 1–90 days, capped to the top five pages and referrers.
get_traffic_sources- Aggregate up to 90 days into channel shares, the top ten referrers, and the top ten UTM source rows.
get_pages- Return the top ten pages with visitors, entries, exits, bounce rate, and average time.
get_audience- Summarise devices, browsers, operating systems, countries, visitor segments, screens, and languages.
Export
export_data- Write CSV or JSON locally, or create a self-contained printable HTML report for PDF; return metadata only.
Try it
Example prompts
Safe by design
- Clarvivo API tokens are scoped and revocable.
- Payment signing secrets stay in the Clarvivo dashboard and never pass through the agent.
- The SPA tracker observes history.pushState, history.replaceState, and popstate automatically, so it needs no router hooks.