Skip to content

Filesystem README recommends deprecated MCP Roots protocol for restricting directory access #4844

Closed as not planned

Description

@Denio1337

Summary

The README.md contains a section recommending the use of the MCP Roots protocol as the mechanism for restricting which directories the filesystem server can access. However, according to the current official MCP specification, Roots is deprecated as of protocol version 2026-07-28 and scheduled for removal.

Source: MCP Specification — Deprecated features

Why this matters

  • New users following the README will adopt a deprecated mechanism that is scheduled for removal from the protocol.
  • Roots-based access restriction may not work with newer MCP clients, so the documented guidance will break over time.
  • The project's documented access-control story should stay aligned with the current specification.

Suggested changes

  • Update the README section to stop recommending Roots as the primary way to restrict directory access
  • Document the alternatives recommended by the spec:
    • passing directories/files via tool parameters
    • resource URIs
    • server configuration (e.g., allowed directories passed via CLI arguments, which the server already supports)
  • If any Roots-related guidance or behavior is kept, mark it explicitly as legacy/deprecated with a pointer to the migration guidance
  • Check whether the server implementation itself relies on Roots (e.g., ListRootsRequest) and, if so, open a follow-up issue for migrating away from it

References

Activity

  1. changed the title [-]README recommends deprecated MCP Roots protocol for restricting directory access[/-] [+]filesystem README recommends deprecated MCP Roots protocol for restricting directory access[/+] on Sep 24, 2026
  2. changed the title [-]filesystem README recommends deprecated MCP Roots protocol for restricting directory access[/-] [+]Filesystem README recommends deprecated MCP Roots protocol for restricting directory access[/+] on Sep 24, 2026
  3. cliffhall commented on Oct 19, 2026

    @cliffhall
    Member

    Closing: this is available in the v2 release.

    Thank you for the suggestion, and apologies for the long wait for a response.

    The reference servers were rebuilt for the 2026-07-28 MCP specification (#4857) and released as v2 (2.0.0 on npm for the TypeScript servers, 2026.10.19 on PyPI for the Python servers), and what this asks for is covered there. The filesystem README now presents command-line directories as the access control and marks Roots as deprecated and 2025-era only, with a link to the deprecation notice. This is happening as part of the backlog triage in #4875.

    If the v2 behavior doesn't meet the need you had in mind, please open a fresh issue describing what's still missing; see CONTRIBUTING.md.

  4. added
    closed-superseded-v2Closed: fixed or made obsolete by the v2 / 2026-07-28 refactor (#4875)
    on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    closed-superseded-v2Closed: fixed or made obsolete by the v2 / 2026-07-28 refactor (#4875)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions