
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 分