# Talivia Revenue Analytics [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/talivia-group/agent  
**GitHub Stars:** 32  
**npm Downloads (last month):** 178  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/talivia-revenue-analytics

## Description
Revenue-first analytics installed and verified by AI agents through Talivia

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "talivia-revenue-analytics": {
    "command": "npx",
    "args": ["-y","@talivia/agent"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/talivia-revenue-analytics/readme_