feat: add MCP 2025-06-18 protocol support with _meta AdditionalFields - #91
Open
bytethm wants to merge 1 commit into
Open
feat: add MCP 2025-06-18 protocol support with _meta AdditionalFields#91bytethm wants to merge 1 commit into
bytethm wants to merge 1 commit into
Conversation
- Add Meta struct with ProgressToken and AdditionalFields support - Implement custom JSON marshaling/unmarshaling for Meta - Add Get/Set helper methods for convenient access - Update CallToolParams to use new Meta type - Add ProtocolVersion_2025_06_18 constant - Add comprehensive tests for Meta functionality - Update example to use new Meta structure This enables passing arbitrary custom metadata in _meta field, supporting use cases like A2A protocol auth metadata passthrough. Based on mcp-go implementation (mark3labs/mcp-go#293) Resolves requirement for custom _meta fields (faustli's use case)
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.
This enables passing arbitrary custom metadata in _meta field, supporting use cases like A2A protocol auth metadata passthrough.
Based on mcp-go implementation (mark3labs/mcp-go#293) Resolves requirement for custom _meta fields (faustli's use case)