Filesystem MCP Server (@sylphlab/filesystem-mcp)

Created By
sylphlaba year ago
Node.js Model Context Protocol (MCP) server providing secure, relative filesystem access for AI agents like Cline/Claude.
Overview

What is Filesystem MCP?

Filesystem MCP is a Node.js server that implements the Model Context Protocol (MCP) to provide secure and efficient filesystem access for AI agents like Cline and Claude.

How to use Filesystem MCP?

To use Filesystem MCP, configure your MCP host settings to run the server using npx or Docker, ensuring the project root directory is correctly set.

Key features of Filesystem MCP?

  • Secure access confined to the project root directory.
  • Batch operations for reading, writing, and managing files.
  • Easy integration with minimal configuration.
  • Docker containerization for consistent deployment.
  • Comprehensive filesystem tools for various tasks.

Use cases of Filesystem MCP?

  1. Empowering AI agents with filesystem capabilities.
  2. Efficiently managing project files and directories.
  3. Performing batch operations to reduce latency and token usage.

FAQ from Filesystem MCP?

  • Can Filesystem MCP be used with any AI agent?

Yes! It is designed to work with AI agents like Cline and Claude.

  • Is there a Docker version available?

Yes! Filesystem MCP can be run as a Docker container.

  • How does it ensure security?

It restricts all operations to the defined project root directory, preventing unauthorized access.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sylphlab
Star
3
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)

a day ago