File Operation Mcp

Created By
lxKylin10 months ago
一个基于MCP的文件操作服务器,提供pdf拆分、合并、转图片、文件统计、文件压缩、文件解压、图片压缩等功能。
Overview

What is File Operation MCP?

File Operation MCP is a file operation server based on the Model Context Protocol (MCP) that provides various functionalities such as PDF splitting, merging, image conversion, file statistics, compression, and decompression.

How to use File Operation MCP?

To use File Operation MCP, clone the project from GitHub, install the dependencies, and start the server. You can then interact with the server using commands to perform file operations.

Key features of File Operation MCP?

  • File statistics: Count the number of files in a specified folder.
  • File listing: Retrieve detailed information about all files in a folder.
  • Image compression: High-quality image compression supporting multiple formats.
  • File compression: Create ZIP, TAR, and TAR.GZ compressed files.
  • File extraction: Extract ZIP, TAR, and TAR.GZ files.
  • PDF merging and splitting: Merge multiple PDF files into one or split a PDF into multiple files.
  • PDF to image conversion: Convert PDF pages to JPEG or PNG images.

Use cases of File Operation MCP?

  1. Managing and organizing files on a server.
  2. Compressing images for web use.
  3. Merging reports into a single PDF document.
  4. Splitting large PDF files for easier sharing.
  5. Converting PDF documents into image formats for presentations.

FAQ from File Operation MCP?

  • Can File Operation MCP handle all file types?

Yes! It supports various file types including images, PDFs, and archives.

  • Is File Operation MCP free to use?

Yes! It is open-source and free for everyone.

  • How do I install File Operation MCP?

Clone the repository, install dependencies using pnpm or npm, and start the server.

Server Config

{
  "mcpServers": {
    "file-operation-mcp": {
      "url": "http://localhost:3000/sse"
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
lxKylin
Star
-
Language
-
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)

11 hours ago