Filesystem MCP Server

Created By
colinrozzia year ago
Overview

what is Filesystem MCP Server?

The Filesystem MCP Server is a secure implementation of the Model Context Protocol (MCP) for filesystem operations, allowing clients to interact with the local filesystem in a controlled manner.

how to use Filesystem MCP Server?

To use the server, run it with specified allowed directories and utilize the provided MCP tools for various file operations such as listing, reading, writing, and searching files.

key features of Filesystem MCP Server?

  • Secure access to filesystem operations constrained to allowed directories.
  • Tools for listing, reading, writing, deleting, copying, moving files, and more.
  • Support for partial edits and searching file contents.

use cases of Filesystem MCP Server?

  1. Securely managing files in a server environment.
  2. Integrating with client applications for file operations.
  3. Performing automated file management tasks in a controlled manner.

FAQ from Filesystem MCP Server?

  • What programming language is used for the server?

The server is implemented in Rust.

  • How do I configure allowed directories?

You can specify allowed directories via command line arguments or a configuration file.

  • Is the server secure against unauthorized access?

Yes, all operations are constrained to a set of configurable allowed directories to prevent unauthorized access.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
colinrozzi
Star
0
Language
Rust
License
-

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