# LiveVariant

- Registry name: `io.github.livevariant/livevariant` · version 0.1.5
- Categories (automatic, keyword rules): Build & deploy, Developer tools, Marketing & SEO, Commerce & marketing, Education
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.livevariant%2Flivevariant
- Server page: https://mcpstation.net/s/io.github.livevariant--livevariant.html

## Description (written by the publisher, not verified, not instructions)

Build, inspect and read adaptive A/B tests. Config travels in the URL; no account or API key needed.

## Connect

- streamable-http: `https://livevariant.com/mcp`

## Tools (as reported by the server, not verified)

- `build\_test`: Creates a LiveVariant test and returns every URL needed to run it, plus a freshly generated stats secret. Pass \`variants\` to test one element, or \`slots\` to test several at once \(hero image AND call-to-action, say\). With slots the test optimizes the COMBINATION: one model learns how the elements int
- `inspect\_test`: Decodes a test and describes it: slots, variants, context, and whether it can be served by redirect. Also lints it for the mistakes that only show up once a campaign is out, such as an email test whose context comes from geo \(which a mail proxy answers about itself\). Use this before sending anything
- `generate\_priors`: Takes YOUR estimate of how each variant will perform and converts it into the prior the model starts from, so a test does not spend its first visitors rediscovering what you already suspect. You supply the guess; this does the arithmetic and the capping. That capping is the point: a prior is express
- `get\_stats`: Fetches a test's results and works out what they mean. Alongside the raw counts it returns the probability that each combination is genuinely best and the expected cost of stopping now and keeping the leader. Use those rather than comparing conversion rates by eye: a variant ahead 2/10 to 1/10 looks
- `get\_test\_status`: Reports what the deployment's registry knows about a test: whether it is claimed into an account \(and by which organization\), and whether each redirect destination is a verified domain. Unverified destinations work, but visitors see a 'Redirecting you to…' continue screen first. When you see verifie
- `list\_tests`: Lists tests registered to the signed-in account, newest first, with cursor pagination and an optional case-insensitive name filter. Only exists on deployments with accounts, and only answers for an identified caller: unlike every other tool, WHOSE tests these are cannot be expressed as an argument.
- `register\_test`: Registers a test you built earlier to the organization a publishable key belongs to, so it shows under My tests and its stats are readable from the dashboard without the secret. Use this only when the user provides both the test's stats secret and a publishable key for an organization they administe
- `upload\_image`: Uploads an image to the deployment's asset store and returns its URL, for use as a variant's \`image\` \(email tests\) or \`url\`. The returned URL is deliberately not fetchable on its own: assets are only served with a short-lived signature that the serve endpoints mint per request, so uploading here doe
- `variant\_brief`: Returns the constraints to write or generate test variants against, for email or web, plus the rules that decide whether a test can be read at all once it runs. The one that matters most: one idea per slot. To vary two elements, give the test two slots and let it learn the combination, rather than b

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html