MCP.so
ログイン

Rust MCP Filesystem

@rust-mcp-stack

Rust MCP Filesystem について

Blazing-fast, asynchronous MCP server for seamless filesystem operations.

基本情報

カテゴリ

ファイルとストレージ

ライセンス

MIT

ランタイム

rust

トランスポート

stdio

公開者

rust-mcp-stack

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

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

概要

What is Rust MCP Filesystem?

Rust MCP Filesystem is a blazingly fast, asynchronous, and lightweight MCP (Model Context Protocol) server for handling filesystem operations. It is a pure Rust rewrite of the JavaScript-based @modelcontextprotocol/server-filesystem, offering enhanced performance, security, and a robust feature set for modern filesystem interactions.

How to use Rust MCP Filesystem?

Install via shell script, PowerShell, Homebrew, Cargo, npm, Docker, or download a pre-built binary. No external runtime (e.g., Node.js) is required. Detailed configuration instructions are available in the project documentation. The server runs as a standalone binary; clients connect per the MCP protocol.

Key features of Rust MCP Filesystem

  • Blazingly fast async I/O built in Rust.
  • Read-only by default for safety; write access must be explicitly enabled.
  • Full glob pattern search (e.g., *.rs, src/**/*.txt).
  • MCP Roots support for dynamic directory whitelisting (disabled by default).
  • ZIP archive creation and extraction tools.
  • Ability to disable specific tools to save tokens.

Use cases of Rust MCP Filesystem

  • AI‑powered file exploration and management with MCP clients.
  • Automating filesystem operations (search, read, write, archive) in a secure sandbox.
  • Integrating with CI/CD pipelines for artifact packaging or log analysis.

FAQ from Rust MCP Filesystem

How does this differ from the JavaScript version?

It is a complete rewrite in Rust, providing higher performance, asynchronous I/O, and no dependency on Node.js. The feature set is enhanced with glob search, MCP Roots, ZIP support, and tool disabling.

Is the server read‑only by default?

Yes. It starts with no write access, ensuring safety. Write operations must be explicitly enabled through configuration.

What installation methods are supported?

Shell script, PowerShell, Homebrew, Cargo (Rust package manager), npm (convenience wrapper), Docker, and direct binary downloads from GitHub Releases.

What are the licensing terms?

The project is licensed under the MIT License.

コメント

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