Best for
- Developers who need an MCP client to access a specified Claude Code project directory.
F
35FMRS · D
The source identifies this as a stdio filesystem configuration example in an Anthropic-managed repository, but does not establish that this specific server is maintained by the upstream filesystem protocol owner; tool names and client compatibility are not evidenced.
A stdio MCP server configuration example for local filesystem access, using the project directory as its target. The source does not provide specific tool names, client compatibility, or more detailed capability information.
Setup
Add this configuration to a client that supports stdio MCP servers, and set ${CLAUDE_PROJECT_DIR} to the target project directory. Before running it, confirm that Node.js and npx are installed and that you trust the relevant plugin and server software.
claude_desktop_config.json
{"command":"npx","args":["-y","@modelcontextprotocol/server-filesystem","${CLAUDE_PROJECT_DIR}"],"env":{"LOG_LEVEL":"info"}}
Fit and risk
Not for
- Users who need database access or custom API tools.
- Users who need remote deployment, SSE, or streamable-http transport.
Required permissions
- Access to the local project directory specified by ${CLAUDE_PROJECT_DIR}.
- The exact read/write scope depends on the client, operating system, and server implementation; the source does not specify it.
Risks and side effects
- The MCP server may access local files; specify only a directory you are willing to authorize.
- The README warns that MCP servers, files, or other software included in plugins may not be controlled by Anthropic and are not guaranteed to work as intended or avoid making changes.
Troubleshooting
- Confirm that ${CLAUDE_PROJECT_DIR} resolves to a valid directory.
- Confirm that Node.js and npx are installed.
- Check that the client supports stdio MCP configuration.
- Inspect runtime logs with LOG_LEVEL set to info.
Use cases
Accessing local files within a project directory.