Talivia Revenue Analytics

io.github.talivia-groupPublished by GitHub account talivia-groupv0.1.0Updated Nov 2, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Talivia Revenue Analytics lets an AI agent set up and verify revenue-first website analytics: install the tracker, check live events, and connect payment…

What you can do
  • Check the connected Talivia account and its available capabilities
  • List existing websites or create a new one after user approval
  • Get the exact tracker configuration and a framework-specific installation plan
  • Verify that real analytics events are reaching Talivia
  • Start a secure payment-provider connection and check revenue attribution readiness
  • Get provider-specific checkout guidance for preserving visitor and session attribution
When to use it
Use it when you want a coding agent to install and verify Talivia analytics in a web project, and to connect traffic data to payment revenue so you can see which referrers, campaigns, pages and journeys produce paying customers.
Requirements
A Talivia account and OAuth sign-in with permission approval in the browser. Either the hosted HTTP endpoint or the local npm package run through npx with Node.js. The optional TALIVIA_API_KEY secret can be stored locally via the setup and check-in commands.
Before you install
The agent can create websites and modify your repository by adding the tracker, so review changes before committing. Payment-provider secrets are handled in the browser rather than chat, and access is scoped to approved permissions and revocable in Talivia settings. Analytics data is sent to Talivia's hosted service.

Installation

In SourceWeft

  1. Open Talivia Revenue Analytics in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.talivia-group%2Fagent/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "talivia-revenue-analytics": {
      "type": "http",
      "url": "https://talivia.com/mcp"
    }
  }
}

README

[Talivia revenue-first analytics dashboard showing visitors, revenue, conversion rate, traffic sources, and customer geography]

Talivia Agent Kit

Revenue-first website analytics that your AI agent can install, connect, and verify for you.

Talivia shows founders which referrers, campaigns, pages, search keywords, and customer journeys turn visits into revenue. @talivia/agent connects Codex, Claude Code, ChatGPT, OpenClaw, Hermes, and other MCP clients to Talivia so an agent can finish the analytics setup inside your project - not just paste a tracking snippet and hope it works.

Ask your agent to set up Talivia. It can find or create the right website, generate a framework-specific installation plan, add the tracker with its native coding tools, verify that real events are arriving, open a secure payment-provider handoff, and check that revenue attribution is ready.

Start free | Agent Kit | Documentation | npm | GitHub

See which traffic becomes revenue

Most analytics products count visits. Payment dashboards count transactions. Talivia connects the two, so you can answer the questions that matter to a growing product:

  • Which referrers, campaigns, and search keywords bring paying customers?
  • Which landing pages and customer journeys lead to a purchase?
  • How do visitors, conversion rate, revenue per visitor, and revenue change together?
  • Which tracked session produced an individual payment?
  • Is analytics and checkout attribution actually working in production?

Talivia puts traffic, visitor journeys, events, payment revenue, and attribution in one workspace. Connect a supported payment provider or use the Manual Payment API for a custom checkout.

From one prompt to verified analytics

Give this to a coding agent after connecting Talivia:

text
Set up Talivia revenue analytics for this project.
1. Connect to my Talivia account and find the correct website.2. If it does not exist, ask before creating it.3. Install the Talivia tracker using the right plan for this framework.4. Build and test the project.5. Verify that Talivia is receiving real events.6. Help me connect revenue attribution through Talivia's secure browser flow.7. Tell me what is working and what still needs attention.

The agent works in your repository. Talivia supplies the exact tracking configuration, secure account workflows, and live verification. Setup is not considered complete merely because code was generated - it is complete when Talivia receives real data.

Why founders and developers use it

  • Revenue-first analytics: follow traffic all the way from source and session to payment.
  • Less integration work: let an agent navigate the tracker, framework, and checkout setup instead of jumping between documentation pages.
  • Real verification: check live ingestion and revenue readiness before declaring the task complete.
  • Framework-aware setup: get an installation plan for Next.js, React/Vite, Astro, or plain HTML.
  • One account connection: use the same Talivia MCP connection across every website in your account.
  • Secure handoffs: approve access and connect payment providers in Talivia's browser UI, not in chat.

Use it for a SaaS launch, indie product, marketing site, developer tool, or any web product where knowing which traffic creates revenue matters more than collecting another pageview count.

Connect Talivia to an AI agent

MCP endpoint

Use the hosted website analytics MCP server when your client supports HTTP MCP and OAuth:

text
https://talivia.com/mcp

Codex:

bash
codex mcp add talivia --url https://talivia.com/mcpcodex mcp login talivia

Claude Code:

bash
claude mcp add --transport http talivia https://talivia.com/mcp

Talivia opens in your browser for sign-in and permission approval. After that, ask the agent to install or verify Talivia in your project.

npm package

Use the package when an agent expects a local stdio MCP server:

bash
npx -y @talivia/agent setup --agent codexnpx -y @talivia/agent checkin --agent codexcodex mcp add talivia -- npx -y @talivia/agent mcp

Check the connection at any time:

bash
npx -y @talivia/agent status

The package also includes a Codex plugin manifest and SKILL.md, so compatible agents can discover both the Talivia MCP server and the safe setup workflow.

What the agent can do

AreaOutcome
AccountCheck the connected Talivia account and available capabilities
WebsitesList existing websites or create one after user approval
TrackingGet the exact tracker and a framework-specific installation plan
VerificationConfirm that real analytics events are reaching Talivia
RevenueStart a secure payment connection and check attribution readiness
CheckoutGet provider-specific guidance for preserving visitor and session attribution

Talivia keeps the product logic on the hosted MCP server, so agents receive the current setup rules without bundling a second analytics implementation into your codebase.

Safe by design

  • Talivia authentication and consent happen in your browser.
  • MCP access is scoped to the permissions you approve.
  • Website permissions are checked on every website-specific action.
  • Payment-provider secrets are never requested through chat or MCP tool arguments.
  • Connections can be reviewed and revoked in Talivia Settings.

Prefer to self-host? Talivia also has an open-source version for running revenue analytics on your own infrastructure. Talivia Cloud provides the managed service and agent connection described here.

Start with your own traffic

Create a Talivia account, connect an agent, and follow the next visit all the way to the payment.

Source: README.md at commit f4ed3fc

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts