Repository navigation
feat(mcp): declare posthog.mcp stable - #1200
Conversation
posthog-python Compliance ReportDate: 2026-11-06T21:45:21.140336+00:00 ✅ All Tests Passed!121/121 tests passed Capture_V1 Tests✅ 95/95 tests passed View Details
Capture_Ai Tests✅ 5/5 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
Feature_Flags_Local_Evaluation Tests✅ 4/4 tests passed View Details
|
SDK performance: posthog-pythonBenchmarks completed. No changes flagged for review. Flags require at least a 5% change in the median and all six pairs agreeing on direction. This is a noise filter, not proof of a performance change or a CI gate. View all results
Values are medians of paired measurements. Not flagged does not mean unchanged. Unavailable means a measurement could not be provided, not zero. Estimated allocation measurements retain their instrumentation uncertainty. RSS measures the whole process, not just SDK allocations; observed peaks are sampled checkpoints. Paired ranges in the diagnostics describe variability, not confidence intervals. Each shard uses its own runner; compare Before PR against With PR within a row, not across shards. Compared 102 metric rows; 102 rows shown in all results. Omitted or shortened data remain in |
1d484ba to
d49400a
Compare
d49400a to
03c6298
Compare
03c6298 to
2ce9df8
Compare
A new stamphog review started for this PR — the fresh verdict replaces this approval.
2ce9df8 to
ed151aa
Compare
A new stamphog review started for this PR — the fresh verdict replaces this approval.
ed151aa to
85e99bf
Compare
A new stamphog review started for this PR — the fresh verdict replaces this approval.
The PR was retargeted to a different base branch, so the approved diff is no longer what was reviewed. Stamphog re-reviews automatically.
85e99bf to
678a75f
Compare
What: a Versioning section in the posthog.mcp README and a release note saying the API and the $mcp_* event schema are stable from this release. Why: posthog.mcp now counts calls the same way as the spec and the other SDKs (posthog-python#1199), so it can make the stability promise sdk-specs#189 defines. It ships inside posthog 7.x, so there's no separate version bump. Tested: docs and release note only; no code change.
678a75f to
6a29b3c
Compare
There was a problem hiding this comment.
Approved.
Documentation and a release note only; no runtime API, event behavior, or build tooling changes. There are no outstanding review concerns, and independent assurance is not required for this contained documentation change.
- Author wrote 0% of the modified lines and has 7 merged PRs in these paths (familiarity MODERATE).
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✓ | no deny categories matched |
| size | ✓ | 0L, 0F substantive, 9L/2F incl. docs/generated/snapshots — within ceiling |
| tier | ✓ | T1-agent / T1b-small (9L, 2F, two-areas, feat) |
| stamphog 2.7.0 | .stamphog/policy.yml @ 6a29b3c · reviewed head 6a29b3c |
Problem
posthog.mcpmakes no stability promise, and the docs warn that its API and events may change in a minor release. After posthog-python#1199, it counts tool calls the same way as the spec and the other SDKs, so its API and event schema are ready to promise stability.Changes
posthog.mcpships insideposthog, so it follows that package's version rather than its own. A minor or patch release doesn't break theposthog.mcpAPI, rename or remove a$mcp_*event or property, change its type, or change which requests send an event. It can add events and properties and redact more of a captured value. This mirrors "Event schema stability" in sdk-specs#189..sampo/changesets/mcp-python-stable.md, minor) stating the promise.Stacked on posthog-python#1199, so the promise ships with the spec alignment and not before it. The TypeScript counterpart is the
@posthog/mcp1.0.0 release, posthog-js#5584.For reviewers: merge after sdk-specs#189. After this ships, posthog.com#21880 drops the "Beta" wording from the Python install page.
How I tested
README and release note only. No code change.