MCP.so
ログイン

MCP Server Filesystem Service

@PimpMyNines

基本情報

カテゴリ

ファイルとストレージ

トランスポート

stdio

作者

PimpMyNines

MCP Server Filesystem Service について

MCP Filesystem Solution

MCP Server Filesystem Service の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "ai-mcp-server-filesystem": {
      "command": "node",
      "args": [
        "dist/index.js"
      ]
    }
  }
}

MCP Server Filesystem Service のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

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.

よくある質問

1

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.

2

Where does file data actually live?

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

3

What security limits does it enforce?

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

4

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.

5

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.

コメント

「ファイルとストレージ」の他のコンテンツ