Run ClickTrail MCP for local attribution diagnostics
Build ClickTrail MCP from its GitHub source and connect the resulting stdio process to an MCP client. Its eleven tools inspect supplied records, generate integration sketches and construct conversion payloads. They do not contact advertising providers. Use synthetic data and distinguish declared pipeline completeness from an observed end-to-end journey.
By FunnelSheet · Technical guide
Build ClickTrail MCP from its GitHub source and connect the resulting stdio process to an MCP client. Its eleven tools inspect supplied records, generate integration sketches and construct conversion payloads. They do not contact advertising providers. Use synthetic data and distinguish declared pipeline completeness from an observed end-to-end journey.
How do I start the server?
After reviewing the repository, clone it and install its dependencies. Run npm run typecheck, npm test and npm run build, then node dist/index.mjs. Configure your MCP client with node as the command and the absolute build path as its argument. A process waiting silently can be normal: it expects newline-delimited JSON-RPC input.
Which checks should come first?
Begin with capture_click_id_schema and diagnose_missing_click_ids using a synthetic case. Use calculate_click_id_coverage only on a clearly defined sample; do not present that ratio as sitewide coverage. validate_attribution_pipeline checks stages you declare, so setting every stage to true is not evidence that a visitor completed them.
Are generated integrations production-ready?
No. Inspect the generated files before adopting them. The Next.js generator explicitly calls for consent gating before cookie storage. It also needs server-owned record identity and deterministic event IDs. These requirements are application work, not hidden capabilities automatically supplied by the tool.
Do the send tools actually send?
send_conversion, send_qualified_lead and send_sale build payloads and declare sideEffects false. check_conversion_status returns unknown because it does not query destination APIs. Keep provider credentials out of this local diagnostic exercise. Actual delivery requires an authorized destination integration and separate diagnostics.
Source and next step
Source reviewed on 2026-09-15: ClickTrail — clicktrail-mcp-local-attribution-diagnostics.
Continue with ClickTrail mcp.
Disclosure: FunnelSheet publishes ClickTrail guidance. These instructions describe source-level behavior, not an independent performance benchmark.