Python (MCP) Filesystem Server

Created By
hypercata year ago
This is a robust Python-based MCP Filesystem Server. It enables AI models and applications to securely interact with the host system's file directories through a defined set of tools, allowing for operations like reading, writing, moving, and listing files and directories.
Overview

what is PyMCP-FS?

PyMCP-FS is a robust Python-based Model Context Protocol (MCP) Filesystem Server that allows AI models and applications to securely interact with the host system's file directories.

how to use PyMCP-FS?

To use PyMCP-FS, clone the repository, install the required dependencies, and run the server with specified allowed directories as command-line arguments.

key features of PyMCP-FS?

  • Secure directory access with predefined allowed directories.
  • Comprehensive file operations including reading, writing, moving, and listing files.
  • Dynamic allowed directories configurable via command-line arguments.
  • Robust logging and error handling.

use cases of PyMCP-FS?

  1. Enabling AI applications to manage files securely.
  2. Providing a controlled environment for file operations in AI models.
  3. Facilitating file access for various applications while maintaining security.

FAQ from PyMCP-FS?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that standardizes how AI tools manage and access files within specified boundaries.

  • Is PyMCP-FS free to use?

Yes! PyMCP-FS is open-source and free to use for everyone.

  • What are the prerequisites for running PyMCP-FS?

You need Python 3.8+ and the fastmcp library installed.

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