File Operations MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is File Operations MCP Server?

File Operations MCP Server is a Model Context Protocol (MCP) server designed to enhance file operation capabilities, including streaming, patching, and change tracking support.

how to use File Operations MCP Server?

To use the server, install it via Smithery or manually, then start the server and utilize the available tools for file and directory operations.

key features of File Operations MCP Server?

  • Basic file operations: copy, read, write, move, delete files
  • Directory operations: create, remove, copy directories
  • File watching: monitor files and directories for changes
  • Change tracking: track and query file operation history
  • Streaming support for large files
  • Real-time progress reporting
  • Enhanced security with path validation

use cases of File Operations MCP Server?

  1. Automating file management tasks in applications.
  2. Monitoring file changes in real-time for backup solutions.
  3. Implementing version control systems for file operations.

FAQ from File Operations MCP Server?

  • Can I use this server for large files?

Yes! The server supports streaming for efficient handling of large files.

  • Is there a limit on the number of requests?

Yes, the server implements rate limiting to prevent abuse, with specific limits for tools and resources.

  • How can I track file changes?

You can use the change tracking feature to query the history of file operations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

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