refactor(mcp): share instrumentation lifecycles - #888
Merged
Conversation
Contributor
posthog-python Compliance ReportDate: 2026-08-25 07:32:50 UTC ✅ All Tests Passed!111/111 tests passed Capture_V1 Tests✅ 94/94 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
# Conflicts: # posthog/mcp/_instrumentation.py
Member
Author
|
This PR is part of a trial using Slopo to identify high-value code duplication for targeted refactoring. |
Contributor
|
Reviews (1): Last reviewed commit: "merge: update MCP lifecycle refactor fro..." | Re-trigger Greptile |
turnipdabeets
approved these changes
Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💡 Motivation and Context
The MCP v1 and v2 adapters duplicated setup, teardown, error capture, and missing-capability reporting for tools, prompts, and resources. Keeping those lifecycle paths separate made it easy for telemetry behavior to drift.
This refactor introduces shared instrumentation lifecycle helpers while leaving adapter-specific SDK calls in each adapter. It preserves support for missing-capability requests that omit tool arguments and avoids reprocessing customer-owned
conversation_idschema fields.💚 How did you test it?
mainmerge: 221 passedmainmerge: 205 passed, 9 skippeduv run pytest --verbose --timeout=30 posthog/test/mcpafter mergingmainand addressing feedback: 231 passedmake public_api_checkorigin/main: clean📝 Checklist
If releasing new changes
sampo addto generate a changeset file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Pi and Slopo identified the repeated MCP instrumentation lifecycle. The implementation keeps version-specific SDK interactions in their adapters and shares telemetry lifecycle state and capture behavior. Autoreview found that missing-capability requests may omit tool arguments, so the shared helper remains null-safe. Reviewer feedback also restored the previous no-warning behavior for tools that own
conversation_id.