Skip to content

Unable to build client or server that would support the older 2024_11_05 rust-mcp-schema #48

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

Closed
pnehrer opened this issue May 29, 2025 · 2 comments

Comments

@pnehrer
Copy link

pnehrer commented May 29, 2025

I don't see a way to select the schema version at the rust-mcp-sdk crate. Would it be possible to expose the various version-selecting features from rust-mcp-schema in the sdk crate so that it'd be possible to build apps that support older protocol versions?

@hashemix
Copy link
Member

hashemix commented May 29, 2025

Yea absolutely.

For servers, that won't be necessary. it's backward compatible. If you build an MCP server using rust-mcp-sdk, it will work with clients using either the 2025-03-26 or 2024-11-05 protocols. for instance rust-mcp-filesystem works with both protocol versions with no issue.

For clients, though, that absolutely makes sense 👍 . I've already started working on implementing protocol version switching using Cargo features and it will be shipped soon.

@hashemix
Copy link
Member

Hey @pnehrer , I just published v0.4.2.

I plan to enhance rust-mcp-sdk support for multiple mcp protocole versions simultaneously, but for now v0.4.2 should unblock you , just use "2024_11_05" feature and disable the default-features:

rust-mcp-sdk = {version="0.4.2", default-features=false, features=["client","2024_11_05"]}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants