Talivia Revenue Analytics — Claude Code MCP server
Connects your AI agent to Talivia to track web traffic directly to payments. The agent integrates the script, runs builds, and verifies real telemetry intake.
claude mcp add --transport http agent https://talivia.com/mcpWhat Talivia Revenue Analytics does
The server links an agent to the Talivia platform through a hosted HTTP endpoint at https://talivia.com/mcp or via the @talivia/agent npm package. Instead of pasting code blindly, the assistant reads your repository structure, selects instructions for Next.js, Astro, or React, and injects the tracker into the project.
Verification happens on live data. The agent triggers a build, executes checks, and queries the Talivia backend to confirm that incoming events actually arrive. It also checks visitor journeys and session links leading to transactions.
Sensitive payment credentials stay protected. Authentication and payment provider handoffs run entirely inside your browser rather than traversing LLM prompts or tool arguments.
What it helps with
- connect incoming campaign traffic and visitor sessions to checkout payments
- integrate the tracking snippet based on your frontend framework
- verify live analytics ingestion on production builds
- configure payment attribution without revealing provider secrets to the LLM
Example prompts for the agent
- Connect Talivia revenue analytics to this repository and inspect the project framework
- Build the app, fire test events, and confirm that Talivia receives the telemetry
- Check revenue attribution readiness and launch the secure browser payment flow
How to install Talivia Revenue Analytics
1Platform CLI: remote server
claude mcp add --transport http agent https://talivia.com/mcp2Platform CLI
claude mcp add --env TALIVIA_API_KEY=<TALIVIA_API_KEY> --transport stdio talivia-revenue-analytics -- npx -y @talivia/agentReplace <…> with your own values
1Platform CLI: remote server
codex mcp add talivia-revenue-analytics --url https://talivia.com/mcp2Platform CLI
codex mcp add talivia-revenue-analytics --env TALIVIA_API_KEY=<TALIVIA_API_KEY> -- npx -y @talivia/agentReplace <…> with your own values
Config file
{
"mcpServers": {
"talivia-revenue-analytics": {
"url": "https://talivia.com/mcp"
}
}
}{
"mcpServers": {
"talivia-revenue-analytics": {
"command": "npx",
"args": [
"-y",
"@talivia/agent"
],
"env": {
"TALIVIA_API_KEY": "<TALIVIA_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"talivia-revenue-analytics": {
"type": "http",
"url": "https://talivia.com/mcp"
}
}
}{
"servers": {
"talivia-revenue-analytics": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@talivia/agent"
],
"env": {
"TALIVIA_API_KEY": "<TALIVIA_API_KEY>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http talivia-revenue-analytics https://talivia.com/mcp2Platform CLI
gemini mcp add -e TALIVIA_API_KEY=<TALIVIA_API_KEY> talivia-revenue-analytics npx -y @talivia/agentReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Talivia Revenue Analytics
How do I install Talivia Revenue Analytics in Claude Code?
Run claude mcp add --transport http talivia-revenue-analytics https://talivia.com/mcp. Your browser will open automatically to authenticate your Talivia profile and confirm permissions.
What does Talivia Revenue Analytics do?
It allows your coding assistant to locate your site profile, insert analytics tracking code, and test that telemetry reaches the platform. It links web sessions to completed customer checkouts.
Are payment provider keys exposed to the AI model?
No secrets are sent through chat prompts or MCP tool arguments. Payment connections and account logins occur strictly within Talivia's web interface in your browser.
