Filesystem MCP Server

Created By
ai-yliua year ago
A Model Context Protocol (MCP) server that provides filesystem operations for Claude AI
Overview

what is Filesystem MCP Server?

Filesystem MCP Server is a Model Context Protocol (MCP) server that provides filesystem operations specifically designed for Claude AI.

how to use Filesystem MCP Server?

To use the Filesystem MCP Server, clone the repository, install the dependencies, build the project, and run the server with specified allowed directories.

key features of Filesystem MCP Server?

  • Read and write files with UTF-8 encoding.
  • Create directories and ensure they exist.
  • List directory contents with file and directory prefixes.
  • Move or rename files and directories.
  • Search for files and directories recursively with case-insensitive matching.
  • Get detailed metadata for files and directories.
  • List all directories the server is allowed to access.

use cases of Filesystem MCP Server?

  1. Integrating filesystem operations into AI applications.
  2. Managing file storage for AI models.
  3. Facilitating data access and manipulation for AI workflows.

FAQ from Filesystem MCP Server?

  • What operations can the Filesystem MCP Server perform?

It can read, write, create directories, list contents, move files, search for files, and get file information.

  • Is there a limit to the number of directories I can specify?

No, you can specify multiple allowed directories when running the server.

  • How does the server ensure security?

The server restricts operations to directories specified via command-line arguments.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ai-yliu
Star
1
Language
JavaScript
License
-
Category
file-systems

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago