ファイル削除機能を提供するモデルコンテキストプロトコル（MCP）サーバー。このサーバーにより、AIアシスタントは必要に応じて、相対パスと絶対パスの両方をサポートし、安全にファイルを削除できます。
相対パスまたは絶対パスを使用してファイルを削除する
複数の潜在的なパスを試すスマートなパス解決
詳細なパス解決情報を含む明確なエラーメッセージ
削除前に安全なファイルの存在をチェック
Claude やその他の MCP 対応 AI アシスタントと連携します
Related MCP server: File MCP Server
Smithery経由で Claude Desktop の File Deletion を自動的にインストールするには:
npx -y @smithery/cli install @qpd-v/mcp-delete --client claudenpx @qpd-v/mcp-deleteまたはグローバルにインストールします:
npm install -g @qpd-v/mcp-deleteClaude Desktop 構成ファイルにサーバー構成を追加します。
ウィンドウズ:
// %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp-delete": {
"command": "npx",
"args": ["@qpd-v/mcp-delete"]
}
}
}MacOSの場合:
// ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp-delete": {
"command": "npx",
"args": ["@qpd-v/mcp-delete"]
}
}
}
}Cline 設定にサーバー構成を追加します。
ウィンドウズ:
// %APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json
{
"mcpServers": {
"mcp-delete": {
"command": "npx",
"args": ["@qpd-v/mcp-delete"]
}
}
}MacOSの場合:
// ~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json
{
"mcpServers": {
"mcp-delete": {
"command": "npx",
"args": ["@qpd-v/mcp-delete"]
}
}
}
}指定されたパスにあるファイルを削除します。
パラメータ:
path （文字列、必須）: 削除するファイルへのパス（作業ディレクトリからの相対パスまたは絶対パス）
Claude での使用例:
You can ask me to delete a file like this:
"Please delete the file example.txt"
I will use the delete_file tool to safely remove the file.サーバーは、複数のアプローチを試して、パス解決をインテリジェントに処理します。
提供された正確なパス
現在の作業ディレクトリからの相対パス
指定されたベースディレクトリからの相対パス
これにより、ファイルを相対パスで参照できるようになり、サーバーがファイルを正しく見つけようとするため、ユーザーフレンドリーになります。
リポジトリをクローンします。
git clone https://github.com/qpd-v/mcp-delete.git
cd mcp-delete依存関係をインストールします:
npm installサーバーを構築します。
npm run build自動リビルドを使用した開発の場合:
npm run watchMCPサーバーはstdio経由で通信するため、デバッグが困難になる場合があります。デバッグにはMCPインスペクターを使用してください。
npm run inspectorこれにより、ブラウザでデバッグ ツールにアクセスするための URL が提供されます。
マサチューセッツ工科大学
qpd-v
Delete a file at the specified path (supports both relative and absolute paths)
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to the file to delete (relative to working directory or absolute) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose critical behavioral traits like whether deletion is permanent, irreversible, requires specific permissions, has confirmation prompts, or affects linked resources. 'Delete' implies destructive, but details are missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero waste—it states the action, resource, and a key parameter detail. It's appropriately sized and front-loaded with the core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral consequences (e.g., permanence, error handling), usage context, and expected outcomes. Given the complexity of file deletion, more guidance is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, so the parameter 'path' is fully documented in the schema. The description adds minimal value by reiterating path support (relative/absolute), which is already in the schema description. Baseline 3 is appropriate as the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Delete') and the resource ('a file at the specified path'), making the purpose unambiguous. It doesn't need to differentiate from siblings since none exist, but it could be more specific about what 'delete' entails (e.g., permanent removal vs. moving to trash).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives (e.g., move_file, archive_file) or any prerequisites (e.g., permissions needed). It mentions path types (relative/absolute) but this is parameter guidance, not usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0delete_fileScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is singular and clearly defined.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'delete_file' follows a clear verb_noun pattern.
One tool is too few for a server named 'MCP-Delete', which suggests a broader deletion domain. A single file deletion tool feels thin and incomplete for the implied scope.
The server name implies deletion operations, but only file deletion is covered. There are significant gaps, such as deleting directories, database entries, or other resources, which will likely cause agent failures.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
