Skip to content

Add filesystems problem statements - #3

Merged
sambhav merged 2 commits into
modelcontextprotocol:mainfrom
DanielTemesgen:add-problem-statements
Oct 20, 2026
Merged

sambhav merged 2 commits into
modelcontextprotocol:mainfrom
DanielTemesgen:add-problem-statements

Conversation

@DanielTemesgen

@DanielTemesgen DanielTemesgen commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Problem statements for the Filesystems WG: scoped listing, search and glob, bulk and partial reads, writes and typed errors, optimistic concurrency, and change notification and caching.

Seeing as the combined Files WG has been put on hold for now, I've removed reference to it here.

Motivation and Context

How Has This Been Tested?

Breaking Changes

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

Problem statements for the Filesystems WG: scoped listing, search and
glob, bulk and partial reads, writes and typed errors, optimistic
concurrency, and change notification and caching.
@DanielTemesgen
DanielTemesgen marked this pull request as ready for review October 14, 2026 12:39
@jayzuccarelli

Copy link
Copy Markdown
Contributor

The running example makes each gap easy to follow.

For what it's worth, #2 (my resource-operations strawman) sketches answers to parts of PS4 and PS5: stat, create/update/delete, and conditional writes with a precondition-failed error. It uses "version" where this uses "revision". I'm happy to switch #2 to "revision" so the two docs line up, or to whatever the group prefers.

@kziemski kziemski self-assigned this Oct 20, 2026
@kziemski
kziemski self-requested a review October 20, 2026 13:32
@kziemski
kziemski dismissed their stale review October 20, 2026 13:37

testing permissions and ran an automated review

@DanielTemesgen
DanielTemesgen requested a review from a team as a code owner October 20, 2026 21:18
@kziemski kziemski removed their assignment Oct 20, 2026
@kziemski
kziemski requested review from kziemski and removed request for kziemski October 20, 2026 21:23
@sambhav
sambhav merged commit 6a61117 into modelcontextprotocol:main Oct 20, 2026
@DanielTemesgen
DanielTemesgen deleted the add-problem-statements branch October 20, 2026 21:27
olaservo added a commit that referenced this pull request Nov 4, 2026
Fast follow to #1. Docs only.

`docs/problem-statements.md` (#3) is now the source of truth for scope,
open questions, and SEP status, so the skeleton docs link to it instead
of restating it:

- **README**: scope covers listing, search/glob, bulk/partial reads,
writes, and `stat` (per PS1–6), and links the problem statements.
- **open-questions.md**: keeps only cross-cutting questions
(SEP-2571/2532 disposition, uploads vs. writes, Skills
`resources/directory/read`) and links the PS items; per-statement
questions live in the problem statements.
- **related-work.md**: drops the SEP table, which had already drifted
(SEP-2631 listed as Draft; it closed 2026-10-14), and points to PS
"Related proposals". Adds the File Uploads extension.
- **use-cases.md**: links the running example and PS1–3 for the two
cases they already cover; memory-server and base64 cases unchanged.

AI disclosure: drafted with Claude Code; reviewed by me.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.

4 participants