@clarvivo/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLARVIVO_BASE_URL | No | Base URL for a local or self-hosted Clarvivo server. Optional; for example http://127.0.0.1:5000 | |
| CLARVIVO_API_TOKEN | Yes | Your Clarvivo API token. Create one at https://app.clarvivo.com/dashboard/settings?tab=api-tokens. This is required for all tools. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setup_analyticsA | Detect this repository's framework, reuse or create the Clarvivo project for a domain, and return the exact file and code edit. Use this first when asked to add analytics. |
| get_install_snippetA | Return the exact tracking snippet, target file, placement, and framework-specific code for an existing Clarvivo API key or project. |
| verify_installationA | Check Clarvivo's proof-of-life receipt to confirm that traffic from the deployed site has arrived, without reading analytics or sending synthetic events. |
| list_projectsA | List accessible Clarvivo projects with their IDs, domains, and public tracking API keys. |
| get_statsA | Return a small pre-summarised traffic overview, active visitor count, and top five pages/referrers instead of raw daily analytics rows. |
| connect_revenueA | Detect a supported payment SDK (or use the named provider), connect its Clarvivo webhook, and return a three-step setup checklist with the exact attribution edit. Never accepts or transmits webhook secrets. |
| verify_revenueA | Check payment webhook proof-of-life and attribution coverage without returning revenue amounts or customer data. |
| add_eventC | Register a Clarvivo event and propose the exact window.clarvivo.trackEvent call and handler placement. This tool does not edit files. |
| create_funnelA | Create an ordered funnel, reusing a case-insensitive name match so retries never duplicate it, and flag steps without a known tracked page. |
| create_alertC | Create a traffic or conversion alert, reusing an existing alert of the same type. |
| list_funnelsA | List the project's funnels and ordered steps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.