Filesystem MCP server in Cline files beyond the workspace.
Cline edits your open project natively — mcp-server-filesystem extends its reach to other directories you choose, through one stdio entry in cline_mcp_settings.json.
Cline already reads and writes the workspace you have open in VS Code. What it can't do natively is reach files outside that workspace — and that's the niche mcp-server-filesystem (@agent-infra/mcp-server-filesystem, from ByteDance's ui-tars-desktop monorepo, 36.3k stars) fills, with an allowed-directories fence so "outside the workspace" never means "everywhere."
Typical uses: letting a Cline task pull reference docs from a folder you keep outside the repo, or writing generated output to a shared location.
Open the config the easy way
Cline's MCP config is cline_mcp_settings.json, buried in VS Code's globalStorage under saoudrizwan.claude-dev/settings/ — a path nobody should type. Instead, click the MCP Servers icon in the Cline panel and hit Configure: Cline opens the file in the editor for you.
The server is an npm package run over stdio, so the entry is a command, not a URL. Node 18+ needs to be on your PATH.
The server entry
Add a filesystem block under mcpServers. The directories after --allowed-directories define everything the server will agree to touch — make them absolute:
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@agent-infra/mcp-server-filesystem@latest",
"--allowed-directories",
"/Users/you/reference-docs"
],
"disabled": false,
"autoApprove": []
}
}
}autoApprove deserves thought here
Cline asks for confirmation before each MCP tool call unless the tool is in autoApprove. For a filesystem server, that prompt is a feature: it shows you each read and write before it happens. A sensible progression is to auto-approve read-style tools (listing, reading, searching) once you trust the setup, while leaving write and delete operations on manual confirmation permanently.
Combined with a narrow allowed-directories list, that gives you two independent layers between an autonomous agent and your disk.
Check the server row, then use it
After saving, the MCP Servers tab should show filesystem with a green indicator; expanding the row lists its tools. First real test: ask Cline to summarize the newest file in your allowed directory — that exercises listing and reading in one prompt.
Want to know the full tool surface before configuring? The server's probed tool list is on its Loomal listing at https://loomal.ai/marketplace/mcp-server-filesystem.
Troubleshooting in Cline
Red row with an error: expand it — Cline prints the server's stderr inline. An npx resolution error means Node isn't on the PATH VS Code inherited; launching VS Code from a terminal (code .) usually cures that. A typo in the scoped package name (@agent-infra/) is the other frequent spawn failure.
No row at all: the JSON didn't parse; check for trailing commas around the autoApprove array. Use the row's Restart button after fixes, or reload the VS Code window.
Tool calls failing with permission-style errors: the requested path is outside --allowed-directories. Remember the workspace itself isn't automatically allowed — if you want Cline using this server inside the repo too, add the repo path to the list.
FAQ
How do I add the filesystem MCP server to Cline?
Open the Cline panel > MCP Servers > Configure, then add an mcpServers entry with command npx and args running @agent-infra/mcp-server-filesystem@latest plus --allowed-directories and your absolute paths. Save, and the server appears with a status row.
Why use this when Cline already edits files?
Cline's native file tools cover the open workspace. This server grants explicit, fenced access to directories outside it — reference folders, shared output locations — without opening those folders as workspaces or widening what Cline can do by default.
Should I put filesystem tools in autoApprove?
Read-oriented tools, maybe, once the setup has earned trust. Keep write and delete tools on manual approval — the confirmation prompt is your last checkpoint before an autonomous agent modifies files, and it costs one click.
Cline says the server failed to start — what do I check?
Expand the server row to read the error. Most failures are PATH (VS Code can't find npx — launch it from a terminal) or the package name (the @agent-infra/ scope is required). Fix, then hit Restart on the row.
More MCP servers for Cline.
Compare live tool lists across servers on the Loomal marketplace.