First Party Data CRO vs LiveVariant
First Party Data CRO is an MCP server published by atul0016. Marketplaces we read that list it: 1 (Official MCP Registry). LiveVariant is an MCP server published by livevariant. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  LiveVariant | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (PyPI): 52 Downloads/week (PyPI): 16 Not marked · First seen |
Listed Version: 0.1.5 Downloads/month (npm): 538 Downloads/week (npm): 62 Forks (GitHub): 2 Stars (GitHub): 2 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | First Party Data CRO | LiveVariant |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 2 |
| Forks (GitHub) (differs) | No figure on GitHub | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (first-party-data-cro-mcp) | Remote server (livevariant.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 3, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/livevariant/livevariant |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 47 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
First Party Data CRO
First-party funnel, rage-click, checkout, A/B test, and page-speed CRO intelligence.
LiveVariant
Build, inspect and read adaptive A/B tests. Config travels in the URL; no account or API key needed.
How to run each
First Party Data CRO As a local MCP server: PyPI package
claude mcp add --env "EARNALL_MCP_LICENSE_KEY=<YOUR_EARNALL_MCP_LICENSE_KEY>" --transport stdio first-party-data-cro -- uvx first-party-data-cro-mcpRequires: EARNALL_MCP_LICENSE_KEY (secret)
LiveVariant As a remote MCP server
claude mcp add --transport http livevariant https://livevariant.com/mcpRequires: LIVEVARIANT_API_TOKEN (secret), LIVEVARIANT_ASSET_UPLOAD_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only LiveVariant has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only First Party Data CRO asks for
EARNALL_MCP_ACTIVATION_IDEARNALL_MCP_LICENSE_APIEARNALL_MCP_LICENSE_KEY (secret)
Only LiveVariant asks for
LIVEVARIANT_API_TOKEN (secret)LIVEVARIANT_ASSET_UPLOAD_TOKEN (secret)LIVEVARIANT_SERVER_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: First Party Data CRO · What it can do: LiveVariant · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.