SEP: Allow non-file URI schemes for Roots #997
Draft
+45
−3
Conversation
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
Implements SEP-1573 to enable Roots with any URI scheme (https://, s3://, git://, etc.) instead of only file:// URIs. This allows servers to work with remote resources while maintaining full backward compatibility. Changes: - Update RootSchema to accept any URI scheme - Add tests validating both file:// and https:// URIs 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
chughtapan
changed the title
|
Saw your SEP at modelcontextprotocol/modelcontextprotocol#1573 If it gets accepted, then the zod validation should be further extended, and not fully removed (as currently on the PR). |
olaservo
reviewed
Oct 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reference implementation for SEP-1573 to enable Roots with any URI scheme (https://, s3://, git://, etc.) instead of only file:// URIs.
Motivation and Context
This allows servers to work with remote resources while maintaining full backward compatibility.
How Has This Been Tested?
All new and existing tests pass
Breaking Changes
No
Types of changes
Checklist
Additional context