Log inSubmit server
Talivia Revenue Analytics logo

Talivia Revenue Analytics

Connects AI agents to Talivia to install, verify, and prepare revenue-focused website analytics.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Talivia Revenue Analytics

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "talivia-revenue-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@talivia/agent"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @talivia/agent

Run talivia setup --agent <name> and talivia checkin --agent <name> first.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 3d ago.

Overview

Talivia Revenue Analytics MCP server connects AI agents to Talivia for website analytics setup, event verification, and revenue attribution readiness. It can identify or create websites with approval, provide framework-specific tracker instructions, and help agents verify live events in a project. Use it when you want an agent to configure analytics for Next.js, React/Vite, Astro, or plain HTML and confirm that production data is arriving.

Use cases

  • Install revenue analytics in a web project
  • Verify that live tracking events reach Talivia
  • Identify which campaigns lead to purchases
  • Prepare payment attribution for a checkout
  • Check analytics readiness before launch

Key features

  • Framework-specific tracker installation plans
  • Website discovery and approval-based creation
  • Live analytics event verification
  • Revenue attribution readiness checks
  • Secure payment-provider handoff
  • Codex plugin manifest and setup workflow

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 50d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @talivia/agent (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars32Stargazers on the source repository.
npm downloads178Package downloads in the last 30 days.
Last commit27d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.

How Talivia Revenue Analytics works

What the Talivia Revenue Analytics MCP server does

Talivia Revenue Analytics MCP server gives coding agents an interface to Talivia’s website analytics workflows. It covers account access, website discovery, tracker setup, live event verification, and revenue attribution preparation. The service connects traffic sources, visitor journeys, events, and payment revenue so teams can investigate which campaigns, referrers, pages, and search terms lead to purchases.

An agent can find the appropriate website in a connected Talivia account. If the site is missing, it can request approval before creating one. It can then return the tracker configuration and an installation approach suited to Next.js, React/Vite, Astro, or plain HTML. After code changes are made with the agent’s native development tools, the agent can check whether real analytics events reach Talivia.

Revenue workflows include starting a secure payment-provider connection and checking whether attribution is ready. Talivia also provides provider-specific checkout guidance for preserving visitor and session attribution. Payment connections are completed through a browser flow rather than by passing provider secrets through chat or MCP arguments.

How it works

The hosted MCP endpoint is available at https://talivia.com/mcp for clients that support HTTP MCP and OAuth. Authentication and permission approval open in a browser. The same Talivia connection can be used across websites in the account, while website permissions are checked for website-specific operations.

A local alternative is supplied through the @talivia/agent npm package. Running its MCP command starts a local stdio server for clients that expect that transport. The package also includes a Codex plugin manifest and SKILL.md describing the supported setup workflow.

Talivia keeps the current setup rules and product logic on its hosted service. The agent operates in the project repository, while Talivia supplies configuration, account workflows, and live verification. Setup is treated as incomplete until Talivia receives real data, rather than stopping after tracker code is generated.

Setup and configuration

For an HTTP connection, add the hosted endpoint to the client and complete browser sign-in and consent. Codex can use its MCP add and login commands, while Claude Code can register the endpoint with HTTP transport.

For a local stdio connection, run the package’s setup command for the target agent, optionally run its check-in command, and register npx -y @talivia/agent mcp as the MCP process. The status command checks the package connection. No environment variables are documented as required.

After connecting an account, ask the agent to locate the project’s Talivia website, request approval before creating one if needed, install the appropriate tracker, build and test the project, verify incoming events, and begin the secure payment handoff when revenue attribution is required.

Limitations and notes

The material documents Talivia Cloud’s managed MCP connection and package, not the configuration details of the separate open-source self-hosted Talivia project. The hosted endpoint requires a client with HTTP MCP and OAuth support; the npm package is intended for clients that expect local stdio MCP servers.

Payment-provider credentials are not entered through chat or MCP tool arguments. Users approve access and connect providers in Talivia’s browser interface, and connections can be reviewed or revoked in Talivia Settings. Revenue attribution also depends on supported payment-provider connections or Talivia’s Manual Payment API for custom checkout flows.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Talivia Revenue Analytics

Talivia Revenue Analytics is an MCP server that connects AI agents to Talivia’s website analytics service. Its main tools cover account and website access, framework-specific tracker setup, live event verification, payment-provider connection, and revenue attribution readiness. It supports hosted HTTP MCP and a local stdio package for compatible clients.

Install it either through the hosted MCP endpoint or the `@talivia/agent` npm package. Use `https://talivia.com/mcp` with an HTTP MCP and OAuth-capable client, or run `npx -y @talivia/agent mcp` for a local stdio server. Browser sign-in and permission approval are required.

Yes, Talivia Revenue Analytics works with Codex. Add the hosted endpoint with Codex’s MCP commands and complete browser login, or run the npm package setup and register its local MCP command. The package also includes a Codex plugin manifest and setup skill.

Yes, it can verify whether real analytics events are reaching Talivia. After installing the tracker and building or testing the project, ask the agent to perform live verification. The workflow does not treat generated code alone as proof that analytics setup is complete.

Related MCP servers

All in Marketing All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTalivia Revenue Analytics AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/talivia-revenue-analytics?style=directory)](https://allmcps.com/mcp/talivia-revenue-analytics)
HTML Embed
<a href="https://allmcps.com/mcp/talivia-revenue-analytics"><img src="https://allmcps.com/api/badge/talivia-revenue-analytics?style=directory" alt="Talivia Revenue Analytics on AllMCPs" /></a>