File system MCP

Created By
iBz-04a year ago
This is a File system mcp server that could allow an LLM to read and list files from a specified safe directory on your local machine.
Overview

What is Filesys?

Filesys is a lightweight MCP server built with Python that allows an LLM to read and list files from a specified directory on your local machine securely.

How to use Filesys?

To use Filesys, clone the repository, install the dependencies, configure the directory in config/config.json, and start the server using python run.py. You can then interact with the server using the example client or any MCP-compatible client.

Key features of Filesys?

  • Securely exposes file contents and metadata from a preconfigured directory.
  • Provides endpoints for listing files and reading file contents.
  • Validates paths to prevent directory traversal attacks.

Use cases of Filesys?

  1. Listing files in a specific directory for LLM processing.
  2. Reading file contents and metadata for analysis or processing.
  3. Integrating with other applications that require file access through MCP protocol.

FAQ from Filesys?

  • Is Filesys secure?

Yes! Filesys implements basic security measures to restrict file access to the configured directory.

  • How do I customize the directory?

You can modify the config/config.json file to point to a different directory as needed.

  • Can I contribute to Filesys?

Yes! Contributions are welcome. Fork the repository and submit a pull request with your changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
iBz-04
Star
1
Language
Python
License
-
Category
file-systems

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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