Filesystem MCP Server (v0.1)
A simple MCP server for filesystem operations with directory sandboxing and read-only mode support.
Early version (0.1) - not thoroughly tested/reviewed, use with caution
Quick Start
Install dependencies:
git clone <repo_url>
uv sync
Run the server:
# Normal mode - full filesystem access
uv run main.py /path/to/allowed/directory
# Read-only mode - no write operations
uv run main.py --read-only /path/to/allowed/directory
Features
- Directory sandboxing (operations restricted to allowed paths)
--read-onlyflag disables write operations- Gitignore support for searches
- Human-readable error messages
Usage Examples
Normal Mode
uv run main.py ~/projects
# Provides: create_file, delete_file, move_file, edit_file, create_directory + read tools
Read-Only Mode
uv run main.py --read-only ~/projects
# Provides only: read_text_file, list_directory, search_files, grep, directory_tree
Multiple Directories
uv run main.py /home/user/docs /tmp/workspace
uv run main.py --read-only /var/log /etc/config
Available Tools
Read Operations (always available):
read_text_file- Read file contentslist_directory- List directory contentsdirectory_tree- JSON directory structuresearch_files- Find files by patterngrep- Search text in filesread_multiple_files- Bulk file reading
Write Operations (disabled in --read-only):
create_file- Create new filesdelete_file- Delete filesmove_file- Move/rename filesedit_file- Edit file contentscreate_directory- Create directories
Dependencies
From pyproject.toml:
fastmcp>=2.11.2- MCP frameworkpathspec>=0.12.1- Gitignore patterns
Security Notes
- All paths resolved with
Path.resolve()to prevent traversal - Operations restricted to allowed directories only
- Binary files rejected for text operations
Metadata
Release files for iflow-mcp_fs-mcp-py 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_fs_mcp_py-0.1.1.tar.gz | 7.9 kB | Without provenance | Details for iflow_mcp_fs_mcp_py-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_fs_mcp_py-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_fs_mcp_py-0.1.1-py3-none-any.whl |
Total release size: 16.3 kB
Release files / iflow_mcp_fs_mcp_py-0.1.1.tar.gz
| Download URL | iflow_mcp_fs_mcp_py-0.1.1.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f5db615a32cadf613dc15e42eab9aedc4f93487747cf6b37d1ee788550671de
|
|
BLAKE2b-256 checksum How to use checksums |
9a1d760c5707a60500f6f0332ef1df0b652b3eccca26da41730521d0a4ec0db3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.17
|
Release files / iflow_mcp_fs_mcp_py-0.1.1-py3-none-any.whl
| Download URL | iflow_mcp_fs_mcp_py-0.1.1-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed5c171ed4e65240ca49edeeddea2082785a260a10ac5a376f98fcbc82a79141
|
|
BLAKE2b-256 checksum How to use checksums |
1b8b5982e9c4598588e6d8cb53d21d55604b1180f3c30072e2c99a96fba4ad91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.17
|
Security for iflow-mcp_fs-mcp-py 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.