experimental-ext-filesystems
AGENTS.md4 starsChanged 10 days agoApache-2.0View on GitHub
Nothing in this repository is a specification yet. The Filesystems Working Group charter defines the scope. The docs/ folder holds open questions, the decision log, related work, and the implementations list. Treat it as context, not as normative text. Do not describe a proposal in this repository as an accepted or official part of MCP. Until accepted text lands under specification/, everything here is experimental. Changes are proposed as pull requests. A change to the group's direction is a dated…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Do not describe a proposal in this repository as an accepted or official part of MCP.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
What to reference as a source
Nothing in this repository is a specification yet. The Filesystems Working Group charter defines the scope. The docs/ folder holds open questions, the decision log, related work, and the implementations list. Treat it as context, not as normative text.
Do not describe a proposal in this repository as an accepted or official part of MCP. Until accepted text lands under specification/, everything here is experimental.
Proposing changes
Changes are proposed as pull requests. A change to the group's direction is a dated entry in docs/decisions.md with **Status:** Proposed, in the ADR-lite format used in that file (Status / Context / Decision / Rationale / References). When a decision supersedes or amends an earlier one, add a forward pointer to the earlier entry's **Status:** line rather than rewriting it.
Code
The Python reference implementation lives in python/sdk/. Run ruff format --check ., ruff check ., mypy src/mcp_ext_filesystems, and pytest from that directory before opening a pull request.
AI disclosure
Pull requests and issues must disclose AI assistance, per the MCP AI contribution policy.
See CONTRIBUTING.md for participation, meetings, and decision-making.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.