Can My Agent Uselookup · compare · cite

Aug 28, 2026 · Catalog foundation is up

Specification feature · interfaces

MCP rootsMCP 2026-07-28

Provide filesystem or workspace roots to an MCP server.

Terminology basis: MCP 2026-07-28. MCP 2026-07-28

MCP roots: 3 supported, 0 partial, 3 unsupported, 25 unreviewed across 31 cataloged products.

Markdown · JSON

Explore this familyMore in Model Context Protocol23 capabilities

Current evidence by product

Can my agent use MCP roots?

Read across for the answer. 6 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.

Known issues (0)Report an issue
  • Supported3
  • Partial0
  • Unsupported3
  • Unknown25
  • Not applicable0

Web

9 products

Desktop

13 products
ClineCline
N4Unsupported
Docs checked 2026-08-28Current · 1 condition
?Unknown
No source reviewedPreview record
Report this result

CLI

9 products

Unknown means no public evidence has been reviewed for that product and capability. It does not mean unsupported.

How statuses are assigned

Definition and scope

What this capability means

Provide filesystem or workspace roots to an MCP server.

This row remains unknown for a product until exact, dated evidence covers this capability rather than MCP generally.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

Claude CLIcli · current
Supported
Target
current Claude Code MCP documentation · dated-documentation
Environment
local-default
Observed
2026-08-28
  • runtimethe documented root is the directory Claude Code was launched from
Evidence
Cursordesktop · current
Supported
Target
current Cursor MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • runtimethe documentation confirms the capability but does not enumerate Cursor's root selection or change-notification policy
Evidence
Gemini CLIcli · current
Supported
Target
Gemini CLI v0.57.0 · release
Environment
local-default
Observed
2026-08-28
  • runtimeroots are derived from the CLI workspace context and change notifications follow workspace-directory updates
  • protocol-revisionevidence covers the pre-2026 roots/list request flow implemented by Gemini CLI v0.57.0
Evidence
Clinedesktop · current
Unsupported
Target
Cline source commit 27350f243c2a observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • host-rolestatus is scoped to Cline's desktop extension MCP client
Evidence
Continuedesktop · current
Unsupported
Target
Continue source commit 5522c6f44ca0 observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • host-rolestatus is scoped to Continue's desktop extension MCP client
Evidence
Zed Agentdesktop · current
Unsupported
Target
Zed source commit e3adf43f37d7 observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • host-rolestatus is scoped to Zed Agent's direct MCP client initialization
Evidence
  1. 1. Evidence checked 2026-08-28: Claude Code documents the MCP `roots/list` request returning the directory from which Claude Code was launched.
  2. 2. Evidence checked 2026-08-28: Gemini CLI v0.57.0 advertises the roots capability, handles `roots/list` from its current workspace directories, and sends `roots/list_changed` when those directories change.
  3. 3. Evidence checked 2026-08-28: Cursor's protocol capability table explicitly lists MCP Roots as supported server-initiated inquiries into URI or filesystem boundaries.
  4. 4. Evidence checked 2026-08-28: Cline's pinned desktop MCP client initializes with an empty client-capabilities object, so it does not advertise or handle the Roots capability.
  5. 5. Evidence checked 2026-08-28: Continue's pinned desktop MCP client initializes with an empty client-capabilities object, so it does not advertise or handle the Roots capability.
  6. 6. Evidence checked 2026-08-28: Zed's pinned MCP initialization explicitly sets the client Roots capability to none.