Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Make "resource" optional on earlier protocols #1017

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 1 commit into from
Jun 25, 2025

Conversation

dr3s
Copy link
Contributor

@dr3s dr3s commented Jun 24, 2025

Make "resource" optional on earlier protocols in order to remain backwards compatible with servers on earlier versions.

Motivation and Context

#991 introduced breaking changes for servers on earlier protocol versions that don't support the resource param. This change requires the param only if either is true: PRM is available or the protocol is 2025-06-18 or later.

How Has This Been Tested?

unit tests

Breaking Changes

None

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@dr3s
Copy link
Contributor Author

dr3s commented Jun 24, 2025

@pcarleton it seems like my implementation is more narrow than yours as I only exclude "resource" if it's also an older protocol

Copy link
Contributor

@pcarleton pcarleton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thanks!

@ihrpr ihrpr merged commit 41f3bc3 into modelcontextprotocol:main Jun 25, 2025
17 of 18 checks passed
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.

3 participants