MCP Filesystem Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Filesystem Server?

MCP Filesystem Server is an unofficial port of Claude's filesystem MCP server implementation, created as a Proof of Concept (POC) to demonstrate and explore MCP server functionality.

how to use MCP Filesystem Server?

To use the MCP Filesystem Server, install it using UVX, configure your claude_desktop_config.json to specify the directories you want to access, and restart Claude Desktop to apply the changes.

key features of MCP Filesystem Server?

  • Allows integration with Claude Desktop for file access.
  • Supports multiple directory configurations.
  • Enforces strict path validation for security.

use cases of MCP Filesystem Server?

  1. Accessing files from specified directories in Claude Desktop.
  2. Demonstrating MCP server functionality for educational purposes.
  3. Exploring filesystem interactions in a controlled environment.

FAQ from MCP Filesystem Server?

  • Is this project affiliated with Anthropic?

No, this is an unofficial port and is not affiliated with Anthropic.

  • Can I use this in production environments?

No, this project is intended for educational purposes only and should not be used in production.

  • What should I do if the server does not show in Claude Desktop?

Ensure your config file syntax is correct and restart Claude Desktop after making changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
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