Rust MCP Filesystem

Created By
rust-mcp-stacka year ago
Blazing-fast, asynchronous MCP server for seamless filesystem operations.
Overview

What is Rust MCP Filesystem?

Rust MCP Filesystem is a blazing-fast, asynchronous MCP (Model Context Protocol) server designed for efficient handling of various filesystem operations, rewritten in Rust for enhanced performance and capabilities.

How to use Rust MCP Filesystem?

To use Rust MCP Filesystem, refer to the project documentation for installation and configuration instructions.

Key features of Rust MCP Filesystem?

  • High Performance: Built in Rust for speed and efficiency, leveraging asynchronous I/O.
  • Read-Only by Default: Starts with no write access for safety.
  • Advanced Glob Search: Supports full glob pattern matching for precise file filtering.
  • Nested Directories: Improved directory creation for nested structures.
  • Lightweight: Standalone with no external dependencies, compiled to a single binary.

Use cases of Rust MCP Filesystem?

  1. Building tools for file exploration.
  2. Automating filesystem operations.
  3. Integrating with other systems for file management.

FAQ from Rust MCP Filesystem?

  • Is Rust MCP Filesystem suitable for production use?

Yes, it is designed for reliability and performance in production environments.

  • What programming language is used?

The project is built using Rust, ensuring type safety and performance.

  • How can I contribute to the project?

Contributions are welcome! Please check the GitHub repository for guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rust-mcp-stack
Star
1
Language
Rust
License
MIT license
Category
file-systems

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago