Status: Experimental. This work is for prototyping and feedback only, and is not an accepted or official MCP extension.
This repository holds the working documents and reference implementations for Resource operations: a common interface for operating on MCP Resources beyond a single read. That covers scoped listing, search and glob, bulk and partial reads, writes (create, update, delete) and a metadata read (stat), with optimistic concurrency control on writes and a defined interaction with change notification and caching. The problem statements define what a proposal must address. It is maintained by the Filesystems Working Group, which coordinates with the File Uploads Working Group on where an upload flow ends and a resource write begins.
Charter: Filesystems Working Group charter: mission, scope, leadership, and active work items.
Discord: #filesystem-wg on the MCP Discord.
Open work: pull requests and issues. Proposals, findings, and implementations are welcome.
| Document | Description |
|---|---|
| Problem Statements | What is missing from Resources today, as six problem statements with a running example |
| Use Cases | Concrete situations Resource operations should serve |
| Open Questions | Questions the group needs to settle, starting with the charter's |
| Resource operations strawman | Draft stat, create, update, delete with revision-based concurrency, for discussion |
| Decision Log | ADR-lite record of the group's decisions, and the vehicle for proposing changes |
| Related Work | SEPs, extensions, and discussions this work builds on |
| Implementations | Servers, SDKs, and hosts that implement Resource operations |
python/ |
Python reference implementation |
conformance/ |
Conformance scenarios for each new method and schema element |
Nothing under docs/ is part of a specification. A specification will live under specification/ once the group has accepted text to put there.
| Language | Directory | Package | Status |
|---|---|---|---|
| Python | python/sdk/ |
mcp-ext-filesystems |
Prototype |
The charter's success criteria call for reference implementations in at least two Tier 1 SDKs.
See CONTRIBUTING.md for how to participate.
Apache License 2.0. See LICENSE.