Skip to content

feat!: implement support for the MCP protocol version 2025-06-18 #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Jul 3, 2025

Conversation

hashemix
Copy link
Member

@hashemix hashemix commented Jul 3, 2025

📌 Summary

This PR adds support for the MCP protocol version 2025-06-18.

🔍 Related Issues

✨ Changes Made

  • Updated rust-mcp-sdk package to the latest version (0.7) with 2025-06-18 support
  • Extended the server handler trait to handle the newly introduced ElicitRequest
  • Updated rust-mcp-macros to align with changes in the Tool struct, including support for new attributes like meta and title
  • Adjusted CallToolResult::text_content invocations for compatibility with changes in rust-mcp-schema version 0.7
  • Aligned README, docs, and code examples with the 2025-06-18 update
  • Added a Cargo feature targeting 2025-06-18 and enabled it by default
  • Adjusted tests to cover updated logic and new MCP features.

🛠️ Testing Steps

in the root of the the rpo run:

cargo make check

💡 Additional Notes

In the rust-mcp-schema package, some constructor functions of CallToolResult within schema_utils have been modified. When updating your code to the latest version, please make sure to adjust your code accordingly.
For instance:

- CallToolResult::text_content( "Hello World!".to_string(), None,)
 
+ CallToolResult::text_content( vec![ TextContent::from("Hello World!".to_string()) ]  )

@hashemix hashemix merged commit 6a24f78 into main Jul 3, 2025
3 checks passed
@hashemix hashemix mentioned this pull request Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant