← MCP

模型与开放条件Model & openness

本身不调用模型，是被客户端调用的接口实现。

依赖 @modelcontextprotocol/sdk（npm 2026.8.31 实测 ^1.30.0）； 协议版本在 initialize 握手时由 SDK 与客户端协商，不绑定单一版本。

It calls no model itself; it is an interface implementation called by clients. It depends on @modelcontextprotocol/sdk (npm measured 2026.8.31: ^1.30.0); the protocol version is negotiated between SDK and client at the initialize handshake, not pinned to a single version.

运行位置Where it runs

本地 Node.js 子进程，通过 stdio 与客户端通信。 生命周期绑定客户端进程，客户端退出即停止。

A local Node.js child process communicating with the client over stdio. Its lifecycle is bound to the client process — it stops when the client exits.

本地文件Local files

核心能力。默认不支持无限制访问： 必须通过命令行参数指定允许目录，或客户端支持 Roots 协议动态下发。 若无参数启动且客户端不支持 roots，server 在初始化阶段直接报错。

The core capability. Unrestricted access is not the default: allowed directories must be given via command-line arguments, or delivered dynamically if the client supports the Roots protocol. If started with no arguments and the client does not support roots, the server errors out directly at initialization.

关机后的任务Tasks after shutdown

不支持。本地 stdio 进程随客户端生死， 无独立守护或云端执行形态。

Not supported. A local stdio process lives and dies with the client; there is no standalone daemon or cloud-execution form.

工具与扩展Tools & extensions

提供 11 个工具：read_text_file、read_media_file、read_multiple_files、

write_file、edit_file、create_directory、list_directory、

list_directory_with_sizes、move_file、search_files、directory_tree。

输出为结构化内容，可直接消费。

It provides 11 tools: read_text_file, read_media_file, read_multiple_files,

write_file, edit_file, create_directory, list_directory,

list_directory_with_sizes, move_file, search_files, directory_tree. Output is structured content, ready for direct consumption.

上下文与记忆Context & memory

无状态。每次调用独立，不保留会话记忆。 list_allowed_directories 可查询当前生效目录。

Stateless. Each call is independent; no session memory is kept. list_allowed_directories can query the currently effective directories.

权限与限制Permissions & limits

无独立审批机制，权限边界完全由允许目录决定。 全部文件操作限制在允许目录内，越界会被拒绝。

注意：提供 write_file / edit_file / move_file / create_directory， 属可写但无删除工具的组合。

No separate approval mechanism; the permission boundary is defined entirely by the allowed directories. All file operations are confined to the allowed directories; anything outside is rejected.

Note: it provides write_file / edit_file / move_file / create_directory — a combination that is writable but has no delete tool.

适合什么任务Best for

让 Agent 安全读写指定目录内的文本与媒体文件。 不适合需要删除操作或需要跨目录聚合的场景。

Lets an Agent safely read and write text and media files inside specified directories. Not a fit for scenarios needing delete operations or cross-directory aggregation.

传输方式Transport

仅 stdio。本地 Node.js 进程，通过标准输入输出通信。

官方 README（2026-10-08 全文核验）只给两种本地启动方式。 即 npx 与 Docker。它没有远程传输的官方配置。 目录控制走命令行参数或 MCP Roots（可动态更新）。

stdio only. A local Node.js process communicating over standard input/output. The official README (full-text verified 2026-10-08) gives only two local launch methods: npx and Docker. There is no official configuration for a remote transport. Directory control goes through command-line arguments or MCP Roots (dynamically updatable).

认证机制Authentication

无独立认证层。stdio 形态继承启动它的客户端用户的全部文件权限。 权限边界靠目录白名单实现，不靠认证机制。

No separate authentication layer. In stdio form it inherits all file permissions of the client user that launches it. The permission boundary is not an auth mechanism but a directory allowlist.

权限范围Permission scope

默认范围窄且强制显式：必须通过命令行参数指定允许目录， 或客户端支持 Roots 协议动态下发。 无参数且客户端不支持 roots 时，server 初始化即报错。

不提供删除工具；提供写入、编辑、移动、建目录。 可用 list_allowed_directories 查询当前生效目录。

The default scope is narrow and explicitly forced: allowed directories must be given via command-line arguments, or delivered dynamically if the client supports the Roots protocol. With no arguments and no client roots support, the server errors out at initialization.

No delete tool is provided; write, edit, move and create-directory are. list_allowed_directories can query the currently effective directories.

本页由This page is generated from the ai-handbook 数据层生成（CC BY 4.0）。data layer (CC BY 4.0). 方法论与坐标系定义见仓库内For the methodology and coordinate definitions, see METHODOLOGY.md.