[wizard-ci-bot]

Automated wizard CI run

Source: scheduled
Trigger ID: cc5471b
App: typescript-sdk/stdio-server
App directory: apps/typescript-sdk/stdio-server
Workbench branch: wizard-ci-cc5471b-typescript-sdk-stdio-server
Wizard branch: main
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-10-28T17:08:59.674Z
Duration: 113.8s

YARA Scanner

✓ 24 tool calls scanned, 0 violations detected

No violations: ✓ 24 clean scans

[wizard-ci-bot]

Now I have all the context I need from the diff and the files. Let me produce the evaluation.

---

PR Evaluation Report

Summary

This PR adds PostHog MCP analytics to a TypeScript STDIO MCP server by installing @posthog/mcp and posthog-node, initializing a PostHog client from environment variables, and wrapping the server with instrument(). It also adds graceful shutdown, a .gitignore for .env, and a setup report.

Files changed	Lines added	Lines removed
4	+55	-2

Confidence score: 5/5 🧙

• No critical or medium issues found. The integration is clean, minimal, and correct for the MCP analytics use case.

---

File changes

Filename	Score	Description
src/index.ts	5/5	Added PostHog client initialization from env vars, instrument() call with captureModel, and SIGTERM shutdown handler
package.json	5/5	Added pinned @posthog/mcp@0.25.0 and posthog-node@5.59.0 dependencies
.gitignore	5/5	Excludes .env from version control
posthog-mcp-analytics-report.md	5/5	Clear documentation of changes, verification steps, and manual next steps

---

App sanity check ✅

Criteria	Result	Description
App builds and runs	Yes	Report confirms npm run build (tsc --noEmit) passes
Preserves existing env vars & configs	Yes	Existing echo and add tool handlers unchanged; no config modifications beyond PostHog additions
No syntax or type errors	Yes	Valid TypeScript throughout
Correct imports/exports	Yes	PostHog from posthog-node, instrument from @posthog/mcp — both correct
Minimal, focused changes	Yes	Only PostHog-related additions, no scope creep
Pre-existing issues	None	Base app is clean

Issues

No issues found.

Other completed criteria

• Environment variables documented in the report with clear manual deployment instructions
• Build configuration valid with pinned dependency versions
• .gitignore properly excludes .env to prevent credential leaks

---

PostHog implementation ✅

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-node@5.59.0 and @posthog/mcp@0.25.0 added to package.json with pinned versions
PostHog client initialized	Yes	new PostHog(token, { host }) initialized at module scope before instrument() call
capture()	Yes	instrument(server, posthog, { captureModel: true }) automatically captures , , and `` events
identify()	N/A	Server-only MCP app — no browser sessions to identify
Error tracking	Yes	@posthog/mcp instrument captures `` events automatically per the report
Reverse proxy	N/A	Server-only app — posthog-node does not benefit from a reverse proxy

Issues

No issues found.

Other completed criteria

• API key loaded from POSTHOG_PROJECT_TOKEN environment variable with explicit validation that throws on missing values
• Host loaded from POSTHOG_HOST environment variable
• Graceful shutdown via SIGTERM handler calls posthog.shutdown() to drain queued events
• captureModel: true option enables LLM model tracking on tool calls

---

PostHog insights and events ✅

Filename	PostHog events	Description
src/index.ts	, , ``	instrument() automatically captures tool invocations, tool listings, and exceptions. captureModel: true adds `` property when the client self-reports a model.

Issues

No issues found.

Other completed criteria

• Events represent real MCP tool invocations (echo, add) — actual product actions
• Tool call events enable funnel analysis (tools listed → tool called → success/failure)
• captureModel enriches events with LLM model metadata when available
• No PII in event properties — only tool names and parameters
• Event naming follows PostHog's standard * convention

---

Reviewed by wizard workbench PR evaluator