How to Add a Filesystem MCP Server to Claude Code

Give Claude Code structured read and write access to a specific folder through the official filesystem MCP server.

7 minBeginner

Visit Claude Code

Model Context Protocol (MCP) servers are small helper programs that expose tools and data to Claude Code over a standard protocol. The filesystem server is the easiest one to start with: it lets Claude list, read, and write files inside a folder you choose, with the path boundary enforced by the server itself. This guide walks through adding it with one command and confirming it works.

Claude Code installed and working in a terminal
Node.js 18 or newer (so npx can run the server package)
A project folder you want Claude to access

Step 1: Add the server with claude mcp add

The fastest path is the built-in CLI. Run the command below from inside your project. The double dash separates Claude Code flags from the command that launches the server, and the final argument is the directory the server is allowed to touch.

zsh - my-project

$claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem ./

Added stdio MCP server filesystem to local config

Step 2: Understand where the config is stored

By default the server is saved at local scope, which means it lives in your per-project user settings and is not shared with teammates. If you want everyone on the repo to get it, re-run the command with the project scope flag so it writes to a committed file instead.

terminal

claude mcp add filesystem --scope project -- npx -y @modelcontextprotocol/server-filesystem ./

.mcp.json - project root

Explorer

src

.mcp.json

package.json

README.md

.mcp.json

2 "mcpServers": {

3 "filesystem": {

4 "command": "npx",

5 "args": [

6 "-y",

7 "@modelcontextprotocol/server-filesystem",

8 "./"

9 ]

10 }

11 }

12}

Project-scope servers land in a committed .mcp.json file.

Step 3: Verify the connection

Start a session and list your servers. A healthy server shows a connected status. If it shows failed, check that Node is on your PATH and that the folder path actually exists.

zsh - my-project

$claude mcp list

filesystem: npx -y @modelcontextprotocol/server-filesystem ./ - connected

Step 4: Use it inside a session

Inside Claude Code, you can now ask it to use the filesystem tools directly. Because the server enforces the directory boundary, requests to read files outside your chosen folder are refused at the server level, not just by the model.

Claude Code

You

Use the filesystem server to list every .md file in the docs folder.

Agent

Found 3 markdown files: docs/intro.md, docs/setup.md, docs/faq.md. Want me to summarize any of them?

Scope a tight boundary

Point the server at the narrowest folder that still gets the job done. A server scoped to ./docs is much safer than one scoped to your home directory, and it keeps the tool list focused.

Result: Claude Code can now browse and edit files inside your chosen folder through a dedicated MCP server, with the access boundary enforced by the server rather than trusting the model to stay in bounds.