MCP Server Filesystem Service

What is MCP Server Filesystem Service?

MCP Server Filesystem Service is a TypeScript and Node.js implementation of a scalable filesystem service for the MCP (Model Context Protocol) server. It provides secure file operations—including path validation, reading, writing, editing with caching, pattern-based searching, directory management, and configurable security limits—following 12-factor app and AWS well-architected principles.

How to use MCP Server Filesystem Service?

Clone the repository, run make install, then build locally with make build-local and start with npm start or node dist/index.js. For Docker, build with make build and run with make run (mounting a workspace volume); use make dev for development mode or make prod for production mode via Docker Compose.

Key features of MCP Server Filesystem Service

• Validates and normalizes file paths against allowed directories.
• Reads, writes, and edits files with built-in content caching.
• Searches files by glob or regex patterns.
• Creates directory trees and lists directory contents.
• Enforces configurable security limits (max file size, allowed directories).

Use cases of MCP Server Filesystem Service

• Securely manage file content for MCP-based AI agents and tools.
• Cache frequently accessed files for efficient read/write operations.
• Restrict file access to approved directories for multi-tenant environments.
• Perform diff-based file editing with flexible matching logic.
• Automate directory creation and listing in CI/CD pipelines.

FAQ from MCP Server Filesystem Service

What runtime and dependencies are required?

Node.js (version specified in the project) and TypeScript, with dependencies installed via make install. Docker is optional for containerized deployment.

Where does file data actually live?

Data lives on the local filesystem of the host or within a mounted workspace volume when using Docker.

What security limits does it enforce?

It enforces a maximum file size and restricts operations to a configurable set of allowed directories.

Does it support any CI/CD integration?

Yes, it includes both GitLab CI (.gitlab-ci.yml) and GitHub Actions (.github/workflows/ci.yml) pipelines for linting, building, testing, security scanning (Snyk), and versioning.

How can I run tests?

Use make test for unit tests, make test-watch for watch mode, or make test-coverage for coverage reports. Tests use Jest and fixtures in the tests/ directory.