Skip to content

[CI] (624abe2) typescript-sdk/stdio-server - #4473

Closed
wizard-ci-bot[bot] wants to merge 1 commit into
mainfrom
wizard-ci-624abe2-typescript-sdk-stdio-server
Closed

wizard-ci-bot[bot] wants to merge 1 commit into
mainfrom
wizard-ci-624abe2-typescript-sdk-stdio-server

Conversation

@wizard-ci-bot

@wizard-ci-bot wizard-ci-bot Bot commented Oct 8, 2026

Copy link
Copy Markdown

Automated wizard CI run

Source: wizard-pr
Trigger ID: 624abe2
App: typescript-sdk/stdio-server
App directory: apps/typescript-sdk/stdio-server
Workbench branch: wizard-ci-624abe2-typescript-sdk-stdio-server
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-10-08T09:30:35.301Z
Duration: 113.1s

YARA Scanner

✓ 29 tool calls scanned, 0 violations detected

No violations: ✓ 29 clean scans

@wizard-ci-bot

wizard-ci-bot Bot commented Oct 8, 2026

Copy link
Copy Markdown
Author

Now I have all the context needed. Let me produce the evaluation.


PR Evaluation Report

Summary

This PR adds PostHog MCP analytics instrumentation to a TypeScript STDIO MCP server. It installs @posthog/mcp and posthog-node, wraps the existing McpServer with instrument(), configures the PostHog client from environment variables, and adds graceful shutdown on SIGTERM.

Files changed Lines added Lines removed
4 +48 -0

Confidence score: 5/5 🧙

  • .env file containing a full API key (phc_nmum...) is committed to the repo — it should be in .gitignore only, not tracked. [CRITICAL]
  • The stale comment on line 17–18 still says "PostHog-less MCP server" and suggests the wizard should wrap it, even though it already has been. Minor but misleading. [LOW]

File changes

Filename Score Description
src/index.ts 4/5 Adds PostHog client initialization, instrument() call, and SIGTERM shutdown handler. Clean and minimal.
package.json 5/5 Adds @posthog/mcp and posthog-node as dependencies.
.gitignore 5/5 Adds .env to gitignore.
posthog-mcp-analytics-report.md 4/5 Documents changes and manual next steps clearly.

App sanity check ⚠️

Criteria Result Description
App builds and runs Yes TypeScript compilation passes per the report; code is syntactically valid.
Preserves existing env vars & configs Yes Existing tools (echo, add) and transport setup are untouched.
No syntax or type errors Yes All imports, types, and function signatures are correct.
Correct imports/exports Yes instrument from @posthog/mcp and PostHog from posthog-node are correct.
Minimal, focused changes Yes Only PostHog instrumentation code was added.
Pre-existing issues None —

Issues

  • Committed .env with full API key: The .env file containing phc_nmum54dVqUBEAmNrWgHdnRF8HRSCVQhxL6kRhy4GCV6a is committed to the repository. While .gitignore was updated to exclude .env, the file itself was committed in a prior step and is tracked. The key should be rotated and the file removed from tracking. [CRITICAL]

Other completed criteria

  • Build configuration is valid — package.json scripts and dependencies are correct
  • Changes are all relevant to PostHog integration
  • Code follows existing codebase patterns (4-space indentation, TypeScript idioms)

PostHog implementation ✅

Criteria Result Description
PostHog SDKs installed Yes posthog-node ^5.55.0 and @posthog/mcp 0.22.2 added to package.json
PostHog client initialized Yes new PostHog() with token and host from env vars, then instrument(server, posthog, { captureModel: true })
capture() Yes instrument() auto-captures , , , and events
identify() N/A Server-only MCP server — no user identification applicable
Error tracking Yes instrument() captures `` for failed tool calls automatically
Reverse proxy N/A Server-only app using posthog-node — reverse proxy not applicable

Issues

  • No critical or medium issues with the PostHog implementation itself.

Other completed criteria

  • API key loaded from POSTHOG_PROJECT_TOKEN environment variable, not hardcoded in source
  • Host correctly configured to https://us.i.posthog.com via POSTHOG_HOST env var
  • Graceful shutdown via posthog.shutdown() on SIGTERM ensures events are flushed
  • requireEnv() helper provides clear error messages if env vars are missing

PostHog insights and events ✅

Filename PostHog events Description
src/index.ts , , , instrument() auto-captures MCP protocol events: tool invocations, server initialization, tool listing, and exceptions from failed calls. captureModel: true adds model context.

Issues

  • No issues with event quality — events are auto-generated by the @posthog/mcp instrumentation library and represent real MCP protocol actions.

Other completed criteria

  • Events represent real protocol actions (tool calls, initialization) — not synthetic
  • Events enable product insights (can build funnels on tool usage, error rates)
  • Events are enriched with properties via captureModel: true option
  • No PII in event properties — MCP protocol data only
  • Event names follow PostHog's * convention — consistent and descriptive

Reviewed by wizard workbench PR evaluator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants