Skip to content
AdminKit

Roots (MCP)

What is Roots (MCP)?

Roots are a Model Context Protocol mechanism for a client to tell a server which filesystem directories it may operate within, advertised as one or more URIs the server is expected to honor voluntarily rather than an enforced sandbox. AdminKit's MCP & Agent Gateway applies the same idea to tools with an allowlist.

By AdminKit team, Netbase JSC · Updated

Roots are a Model Context Protocol mechanism — part of the protocol Anthropic introduced to standardize how applications connect context and tools to an LLM — for a client to tell a server which filesystem directories it’s permitted to operate within, exposed through a client capability the server can query at the start of a session. A client exposing roots — for example, a desktop AI application with a project folder open — advertises one or more URIs as its roots, and a well-behaved server is expected to confine any file operations its tools perform to those boundaries rather than reaching elsewhere on disk. In the current specification each root’s URI must be a file:// URI, the scheme RFC 8089 standardizes for naming files on a host’s filesystem. Roots are advisory in the specification, not an enforced sandbox: a server still has to honor them voluntarily, so they reduce the chance of a tool call touching an unrelated directory by mistake rather than guaranteeing it can’t happen against a server that ignores the signal.

Roots are one of several client-side capabilities MCP defines, alongside sampling and elicitation, each letting a server ask the client for something only it can provide — model access, user input, or a filesystem boundary.

Roots (MCP) is part of AdminKit’s AI agents & MCP cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Are MCP roots an enforced sandbox?

No -- roots are advisory in the specification; a server still has to honor them voluntarily, so they reduce accidental exposure rather than guaranteeing it can't happen.

How does a client expose roots to a server?

Through a client capability the server can query at the start of a session, with the client advertising one or more URIs as its roots.

What's an example of a client that would expose roots?

A desktop AI application with a project folder open, telling the server's tools to stay confined to that folder.