feat(client): add timing information to request history and notifications#1052
Open
KyleKincer wants to merge 2 commits intomodelcontextprotocol:mainfrom
Open
feat(client): add timing information to request history and notifications#1052KyleKincer wants to merge 2 commits intomodelcontextprotocol:mainfrom
KyleKincer wants to merge 2 commits intomodelcontextprotocol:mainfrom
Conversation
…ions Add temporal context to help debug MCP server behavior: - Display request-to-response duration (e.g., "245ms", "2.4s") - Show timestamps for requests and notifications - Add expanded view with full timing details Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Member
|
@KyleKincer could you add a screenshot or two of what this looks like in the UI? Thanks! |
Author
Sure thing, sorry about that. PR description updated |
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
2 participants
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.
Summary
TimestampedNotificationwrapper for server notifications with receive timestampsRequestHistoryEntrytype with timing fields for request historyNote on V2
This feature aligns with V2's existing design - the
HistoryEntrytype inv2/corealready includes adurationfield, and the V2 UX spec shows timing display. However, V2's timing capture isn't wired up yet. This PR provides the functionality for V1 users in the interim.Test plan
npm run buildpassesnpm run lintpasses🤖 Generated with Claude Code