
Talivia Revenue Analytics
io.github.talivia-group由 GitHub 账号 talivia-group 发布v0.1.0更新于 Nov 2, 2026
Revenue-first analytics installed and verified by AI agents through Talivia
概览
Talivia Revenue Analytics 让 AI 代理安装并验证以营收为核心的网站分析:接入追踪代码、确认实时事件、连接支付归因。
- 可以做什么
- 查看已连接的 Talivia 账户及其可用能力
- 列出已有网站,或在用户批准后新建网站
- 获取准确的追踪配置和针对所用框架的安装方案
- 验证真实分析事件是否已到达 Talivia
- 发起安全的支付服务商连接并检查营收归因是否就绪
- 获取针对具体支付服务商的结账指引,以保留访客与会话归因
- 适用场景
- 当你希望由编码代理在网页项目中安装并验证 Talivia 分析,并把流量数据与支付营收关联,从而看清哪些来源、活动、页面和用户旅程带来付费客户时使用。
- 运行要求
- 需要 Talivia 账户,并在浏览器中通过 OAuth 登录并批准权限。可使用托管的 HTTP 端点,或通过 npx 运行本地 npm 包(需 Node.js)。可选的 TALIVIA_API_KEY 密钥可通过 setup 与 checkin 命令保存在本地。
安装
在 SourceWeft 中
- 打开 控制台中的 Talivia Revenue Analytics,将其添加到工作区。
- 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.talivia-group%2Fagent/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。
{
"mcpServers": {
"talivia-revenue-analytics": {
"type": "http",
"url": "https://talivia.com/mcp"
}
}
}README
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:
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:
Codex:
Claude Code:
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:
Check the connection at any time:
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
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.
来源:README.md,提交 f4ed3fc
工具
0版本历史
1- v0.1.0最新Sep 16, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分