V
vizuh/clicktrail-mcp
ClickTrail MCP makes that handoff inspectable and completable by coding agents.
更新 2026-09-16
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 0 ★ · vizuh/clicktrail-mcp · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
vizuh/clicktrail-mcp;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# ClickTrail MCP
以下摘录自该仓库的 README(片段)
> ClickTrail is the open-source attribution handoff layer that keeps observed acquisition context attached to conversion records inside the stack you own.
ClickTrail MCP makes that handoff inspectable and completable by coding agents.
It supports a safe snapshot mode and a bounded Verify mode. Agents can inspect a
supplied project snapshot, run clicktrail-verify against an explicit local
repository and synthetic/staging URL, receive a canonical evidence report, and
optionally ask TypeSafe to route and prioritize the next remediation.
## Build and test
sh
npm run typecheck
npm test
npm run build
## Run
Use the published package when available:
sh
npx -y @vizuh/clicktrail-mcp
Or run the checked-out server:
sh
npm run build
node dist/index.mjs
Example Codex configuration:
sh
codex mcp add clicktrail -- npx -y @vizuh/clicktrail-mcp
Grok Build can use the same local stdio server after a checked-out build:
sh
grok mcp add --scope project clicktrail -- node /path/to/clicktrail-mcp/dist/index.mjs
grok inspect
This manual setup is intentional while @vizuh/clicktrail-mcp@0.3.0 is not
published on npm. Do not copy an npx command into a distributable plugin until
that exact package version is reachable from the public registry. xAI's
Responses API remote MCP surface is separate and accepts streaming HTTP or SSE,
not this stdio process.
The server reads newline-delimited JSON-RPC messages from stdin and writes responses to stdout. Snapshot tools do not read project files. The explicit verify_project tool invokes a local verifier against a caller-selected repository and URL; it does not submit forms, call ad platforms, transmit customer data, or claim live provider verification.
## Workflow tools
inspect_project → detect_attribution_gaps → plan_installation
generate_nextjs_integration / generate_shopify_integration
simulate_ad_click → verify_capture → verify_form_attachment → verify_crm_attachment
verify_conversion_delivery → attribution_health
verify_project → advise_report (optional TypeSafe routing and prioritization)
The server also provides capture_click_id_schema, validate_attribution_pipeline, diagnose_missing_click_ids, calculate_click_id_coverage, reconcile_conversions, send_conversion, send_qualified_lead, send_sale, and check_conversion_status. Delivery tools build payloads only. check_conversion_status always returns unknown; verify_conversion_delivery classifies a caller-supplied receipt without authenticating it.
## Choosing tools and interpreting results
Snapshot tools operate locally on supplied data, need no credentials, and perform
no external writes or provider calls. verify_project is an explicit local
subprocess boundary and may access the selected repository and URL. advise_report
uses TypeSafe only when configured and sends redacted summaries. Discovery
includes parameter descriptions and read-only annotations; initialization
includes workflow guidance.
| Question | Tool | Result boundary |
| What does this source snapshot contain? | inspect_project | Keyword signals, not executed tests |
ClickTrail MCP makes that handoff inspectable and completable by coding agents.
It supports a safe snapshot mode and a bounded Verify mode. Agents can inspect a
supplied project snapshot, run clicktrail-verify against an explicit local
repository and synthetic/staging URL, receive a canonical evidence report, and
optionally ask TypeSafe to route and prioritize the next remediation.
## Build and test
sh
npm run typecheck
npm test
npm run build
## Run
Use the published package when available:
sh
npx -y @vizuh/clicktrail-mcp
Or run the checked-out server:
sh
npm run build
node dist/index.mjs
Example Codex configuration:
sh
codex mcp add clicktrail -- npx -y @vizuh/clicktrail-mcp
Grok Build can use the same local stdio server after a checked-out build:
sh
grok mcp add --scope project clicktrail -- node /path/to/clicktrail-mcp/dist/index.mjs
grok inspect
This manual setup is intentional while @vizuh/clicktrail-mcp@0.3.0 is not
published on npm. Do not copy an npx command into a distributable plugin until
that exact package version is reachable from the public registry. xAI's
Responses API remote MCP surface is separate and accepts streaming HTTP or SSE,
not this stdio process.
The server reads newline-delimited JSON-RPC messages from stdin and writes responses to stdout. Snapshot tools do not read project files. The explicit verify_project tool invokes a local verifier against a caller-selected repository and URL; it does not submit forms, call ad platforms, transmit customer data, or claim live provider verification.
## Workflow tools
inspect_project → detect_attribution_gaps → plan_installation
generate_nextjs_integration / generate_shopify_integration
simulate_ad_click → verify_capture → verify_form_attachment → verify_crm_attachment
verify_conversion_delivery → attribution_health
verify_project → advise_report (optional TypeSafe routing and prioritization)
The server also provides capture_click_id_schema, validate_attribution_pipeline, diagnose_missing_click_ids, calculate_click_id_coverage, reconcile_conversions, send_conversion, send_qualified_lead, send_sale, and check_conversion_status. Delivery tools build payloads only. check_conversion_status always returns unknown; verify_conversion_delivery classifies a caller-supplied receipt without authenticating it.
## Choosing tools and interpreting results
Snapshot tools operate locally on supplied data, need no credentials, and perform
no external writes or provider calls. verify_project is an explicit local
subprocess boundary and may access the selected repository and URL. advise_report
uses TypeSafe only when configured and sends redacted summaries. Discovery
includes parameter descriptions and read-only annotations; initialization
includes workflow guidance.
| Question | Tool | Result boundary |
| What does this source snapshot contain? | inspect_project | Keyword signals, not executed tests |
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/vizuh-clicktrail-mcp/)
- 来源
- awesome · https://github.com/vizuh/clicktrail-mcp
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。