Expand MCP analytics - #20
Merged
Merged
Conversation
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
1 participant
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.
What changed
Why
The SDK's latest engagement analytics were not exposed through the MCP server. The MCP still returned only a single email-stat page and basic post/comment data, leaving post-management, Note, subscriber, and activity analytics inaccessible to MCP clients.
Impact
MCP clients can now analyze publication-wide performance, inspect complete post and Note engagement, discover the authenticated profile, and access bounded activity and subscriber analytics without exposing subscriber records by default.
Validation
bun run test:all— 50 tests passedbun run build— passedgit diff --check— passed