Filesystem MCP Server (@shtse8/filesystem-mcp)
About
📁 Secure, efficient MCP filesystem server - token-saving batch operations with project root confinement
Details
- Author
- shtse8
- GitHub stars
- 7
- Downloads
- 523
- Categories
- Other, AI
Jump to
- Batch operations – read, write, edit multiple files in one request
- Token‑optimized – reduces round trips and overhead (50‑70% less token usage)
- Project root confinement – prevents path traversal outside the working directory
- Zod validation – all tool arguments validated for safety
- Detailed per‑item error reporting for batch operations
- 11+ tools including read, write, edit, search, move, copy, delete, chmod, chown
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Filesystem MCP Server (@shtse8/filesystem-mcp)Command (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Configure the server in your MCP host (e.g., Cline, VSCode) using npx or bunx with the command @shtse8/filesystem-mcp. Alternatively, run the official Docker image, mounting your project directory to /app. The server uses its current working directory as the project root; ensure your host sets cwd appropriately.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"filesystem mcp server (@shtse8/filesystem-mcp)": {
"filesystem-mcp": {
"command": "npx",
"args": [
"@sylphx/filesystem-mcp"
],
"name": "Filesystem (npx)"
}
}
}
}McpServers
{
"filesystem-mcp": {
"command": "npx",
"args": [
"@sylphx/filesystem-mcp"
],
"name": "Filesystem (npx)"
}
}Filesystem MCP 📁
Secure filesystem operations for AI agents - Token-optimized with batch processing
Batch operations • Project root safety • Token optimized • Zod validation
Quick Start • Installation • Tools
<a href="https://glama.ai/mcp/servers/@sylphx/filesystem-mcp">
</a>
</div>
---
🚀 Overview
Empower your AI agents (like Claude/Cline) with secure, efficient, and token-saving access to your project files. This Node.js server implements the Model Context Protocol (MCP) to provide a robust set of filesystem tools.
The Problem:
Traditional AI filesystem access:
- Shell commands for each operation ❌
- No batch processing (high token cost) ❌
- Unsafe (no project root boundaries) ❌
- High latency (shell spawn overhead) ❌
The Solution:
Filesystem MCP Server:
- Batch operations (10+ files at once) ✅
- Token optimized (reduce round trips) ✅
- Secure (confined to project root) ✅
- Direct API (no shell overhead) ✅
Result: Safe, fast, and token-efficient filesystem operations for AI agents.
---
⚡ Performance Advantages
Token & Latency Optimization
| Metric | Individual Shell Commands | Filesystem MCP | Improvement |
|--------|---------------------------|----------------|-------------|
| Operations/Request | 1 file | 10+ files | 10x reduction |
| Round Trips | N operations | 1 request | N× fewer |
| Latency | Shell spawn per op | Direct API | 5-10× faster |
| Token Usage | High overhead | Batched context | 50-70% less |
| Error Reporting | stderr parsing | Per-item status | Detailed |
Real-World Benefits
- Batch file reads - Read 10 files in one request vs 10 requests
- Multi-file edits - Edit multiple files with single tool call
- Recursive operations - List entire directory trees efficiently
- Detailed status - Per-item success/failure reporting
---
🎯 Why Choose This Server?
Security & Safety
- 🛡️ Project Root Confinement - All operations restricted to cwd at launch
- 🔒 Permission Control - Built-in chmod/chown tools
- ✅ Validation - Zod schemas validate all arguments
- 🚫 Path Traversal Prevention - Cannot escape project directory
Efficiency & Performance
- ⚡ Batch Processing - Process multiple files/directories per request
- 🎯 Token Optimized - Reduce AI-server communication overhead
- 🚀 Direct API - No shell process spawning
- 📊 Detailed Results - Per-item status for batch operations
Developer Experience
- 🔧 Easy Setup - npx/bunx for instant use
- 🐳 Docker Ready - Official Docker image available
- 📦 Comprehensive Tools - 11+ filesystem operations
- 🔄 MCP Standard - Full protocol compliance
---
📦 Installation
Method 1: npx/bunx (Recommended)
The simplest way - always uses latest version from npm.
Using npx:
{
"mcpServers": {
"filesystem-mcp": {
"command": "npx",
"args": ["@sylphx/filesystem-mcp"],
"name": "Filesystem (npx)"
}
}
}
Using bunx:
{
"mcpServers": {
"filesystem-mcp": {
"command": "bunx",
"args": ["@sylphx/filesystem-mcp"],
"name": "Filesystem (bunx)"
}
}
}
Important: The server uses its own Current Working Directory (cwd) as the project root. Ensure your MCP host (e.g., Cline/VSCode) launches the command with cwd set to your project's root directory.
Method 2: Docker
Use the official Docker image for containerized environments.
{
"mcpServers": {
"filesystem-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-v",
"/path/to/your/project:/app",
"sylphx/filesystem-mcp:latest"
],
"name": "Filesystem (Docker)"
}
}
}
Remember to replace /path/to/your/project with your actual project path.
Method 3: Local Build (Development)
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
