Filesystem is a Developer Tools MCP server that lets Claude Code, Cursor, Windsurf and any MCP-compatible AI agent local filesystem operations — read, write, search. Install in 1 minute with mcpizy install filesystem.
Developer Tools
Local filesystem operations — read, write, search
mcpizy install filesystemnpx -y @modelcontextprotocol/server-filesystemIf Filesystem doesn't fit your stack, these Developer Tools MCP servers solve similar problems.
The Filesystem MCP server is an Developer Tools Model Context Protocol server that lets Claude Code, Cursor, Windsurf, VS Code with Copilot, and other MCP-compatible AI agents local filesystem operations — read, write, search. It exposes Filesystem's capabilities as tools the AI can call directly from your editor or CLI.
The fastest way is the MCPizy CLI: run `mcpizy install filesystem` and MCPizy will add the server to your `.claude.json` automatically. You can also install it manually by adding an entry under `mcpServers` in `.claude.json` with the command `npx -y @modelcontextprotocol/server-filesystem` and restarting Claude Code.
Yes. The Filesystem MCP server is free and open source (see the GitHub repository linked on this page). You may still need a Filesystem account or API key to connect the server to the underlying service, but the MCP layer itself has no MCPizy subscription cost.
Yes. Any MCP-compatible client works — including Claude Code, Claude Desktop, Cursor (via `.cursor/mcp.json`), Windsurf, VS Code with Copilot Chat, and custom agents built on the MCP SDK. The same install command targets all of them; only the config file path differs.
Once installed, your AI agent can local filesystem operations — read, write, search directly inside your conversation. Typical use cases include asking Claude Code or Cursor to run Filesystem operations, inspect results, chain Filesystem with other MCP servers (see our Workflow Recipes), and automate repetitive developer tools tasks without leaving your editor.