Mcp Filesystem

Created By
gabrielmaialva33a year ago
A secure Model Context Protocol (MCP) server providing filesystem access within predefined directories
Overview

what is Mcp Filesystem?

Mcp Filesystem is a secure Model Context Protocol (MCP) server that provides filesystem access within predefined directories, ensuring strict path validation for security.

how to use Mcp Filesystem?

To use Mcp Filesystem, clone the repository from GitHub, install the necessary dependencies, and run the server specifying the directory you want to allow access to.

key features of Mcp Filesystem?

  • Secure access with strict path validation
  • File operations including read, write, edit, and move
  • Directory operations such as create, list, and search
  • Metadata access for file and directory information
  • Docker support for easy deployment

use cases of Mcp Filesystem?

  1. Providing secure file access for AI models
  2. Managing files in a controlled environment
  3. Facilitating file operations in cloud applications

FAQ from Mcp Filesystem?

  • Is Mcp Filesystem secure?

Yes! It enforces strict path validation to prevent unauthorized access.

  • Can I use Mcp Filesystem with Docker?

Yes! Mcp Filesystem supports Docker for easy deployment.

  • What programming languages are used in Mcp Filesystem?

The project is primarily built with TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gabrielmaialva33
Star
6
Language
TypeScript
License
MIT 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
Voyei

4 hours ago