@wonderwhy-er
基本信息
This is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"desktop-commander": {
"command": "npx",
"args": [
"-y",
"@wonderwhy-er/desktop-commander"
]
}
}
}Get the complete server configuration as JSON. Config includes fields for: - blockedCommands (array of blocked shell commands) - defaultShell (shell to use for commands) - allowedDirectories (paths the server can access) - fileReadLineLimit (max lines for read_file, default 1000) - fileWriteLineLimit (max lines per write_file call, default 50) - telemetryEnabled (boolean for telemetry opt-in/out) - currentClient (information about the currently connected MCP client) - clientHistory (history of all clients that have connected) - version (version of the DesktopCommander) - systemInfo (operating system and environment details) This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Set a specific configuration value by key. WARNING: Should be used in a separate chat from file operations and command execution to prevent security issues. Config keys include: - blockedCommands (array) - defaultShell (string) - allowedDirectories (array of paths) - fileReadLineLimit (number, max lines for read_file) - fileWriteLineLimit (number, max lines per write_file call) - telemetryEnabled (boolean) IMPORTANT: Setting allowedDirectories to an empty array ([]) allows full access to the entire file system, regardless of the operating system. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Read contents from files and URLs. Read PDF files and extract content as markdown and images. Prefer this over 'execute_command' with cat/type for viewing files. Supports partial file reading with: - 'offset' (start line, default: 0) * Positive: Start from line N (0-based indexing) * Negative: Read last N lines from end (tail behavior) - 'length' (max lines to read, default: configurable via 'fileReadLineLimit' setting, initially 1000) * Used with positive offsets for range reading * Ignored when offset is negative (reads all requested tail lines) Examples: - offset: 0, length: 10 → First 10 lines - offset: 100, length: 5 → Lines 100-104 - offset: -20 → Last 20 lines - offset: -5, length: 10 → Last 5 lines (length ignored) Performance optimizations: - Large files with negative offsets use reverse reading for efficiency - Large files with deep positive offsets use byte estimation - Small files use fast readline streaming When reading from the file system, only works within allowed directories. Can fetch content from URLs when isUrl parameter is set to true (URLs are always read in full regardless of offset/length). FORMAT HANDLING (by extension): - Text: Uses offset/length for line-based pagination - Excel (.xlsx, .xls, .xlsm): Returns JSON 2D array * sheet: "Sheet1" (name) or "0" (index as string, 0-based) * range: ALWAYS use FROM:TO format (e.g., "A1:D100", "C1:C1", "B2:B50") * offset/length work as row pagination (optional fallback) - Images (PNG, JPEG, GIF, WebP): Base64 encoded viewable content - PDF: Extracts text content as markdown with page structure * offset/length work as page pagination (0-based) * Includes embedded images when available - DOCX (.docx): Two modes depending on parameters: * DEFAULT (no offset/length): Returns a text-bearing outline — shows paragraphs with text, tables with cell content, styles, image refs. Skips shapes/drawings/SVG noise. Each element shows its body index [0], [1], etc. * WITH offset/length: Returns raw pretty-printed XML with line pagination. Use this to drill into specific sections or see the actual XML for editing. * EDITING WORKFLOW: 1) read_file to get outline, 2) read_file with offset/length to see raw XML around what you want to edit, 3) edit_block with old_string/new_string using XML fragments copied from the read output. * IMPORTANT: offset MUST be non-zero to get raw XML (use offset=1 to start from line 1). offset=0 always returns the outline regardless of length. * For BULK changes (translation, mass replacements): use start_process with Python zipfile module to find/replace all <w:t> elements at once. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normal…
Read the contents of multiple files simultaneously. Each file's content is returned with its path as a reference. Handles text files normally and renders images as viewable content. Recognized image types: PNG, JPEG, GIF, WebP. Failed reads for individual files won't stop the entire operation. Only works within allowed directories. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. 🐳 KUBERNETES: Prefer paths within mounted directories: /home/appuser. When users ask about file locations, check these mounted paths first. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Write or append to file contents. IMPORTANT: DO NOT use this tool to create PDF files. Use 'write_pdf' for all PDF creation tasks. DO NOT use this tool to edit DOCX files. Use 'edit_block' with old_string/new_string instead. To CREATE a new DOCX, use write_file with .docx extension — text content with markdown headings (#, ##, ###) is converted to styled DOCX paragraphs. CHUNKING IS STANDARD PRACTICE: Always write files in chunks of 25-30 lines maximum. This is the normal, recommended way to write files - not an emergency measure. STANDARD PROCESS FOR ANY FILE: 1. FIRST → write_file(filePath, firstChunk, {mode: 'rewrite'}) [≤30 lines] 2. THEN → write_file(filePath, secondChunk, {mode: 'append'}) [≤30 lines] 3. CONTINUE → write_file(filePath, nextChunk, {mode: 'append'}) [≤30 lines] ALWAYS CHUNK PROACTIVELY - don't wait for performance warnings! WHEN TO CHUNK (always be proactive): 1. Any file expected to be longer than 25-30 lines 2. When writing multiple files in sequence 3. When creating documentation, code files, or configuration files HANDLING CONTINUATION ("Continue" prompts): If user asks to "Continue" after an incomplete operation: 1. Read the file to see what was successfully written 2. Continue writing ONLY the remaining content using {mode: 'append'} 3. Keep chunks to 25-30 lines each FORMAT HANDLING (by extension): - Text files: String content - Excel (.xlsx, .xls, .xlsm): JSON 2D array or {"SheetName": [[...]]} Example: '[["Name","Age"],["Alice",30]]' Files over 50 lines will generate performance notes but are still written successfully. Only works within allowed directories. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. 🐳 KUBERNETES: Prefer paths within mounted directories: /home/appuser. When users ask about file locations, check these mounted paths first. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Create a new PDF file or modify an existing one. THIS IS THE ONLY TOOL FOR CREATING AND MODIFYING PDF FILES. RULES ABOUT FILENAMES: - When creating a new PDF, 'outputPath' MUST be provided and MUST use a new unique filename (e.g., "result_01.pdf", "analysis_2025_01.pdf", etc.). MODES: 1. CREATE NEW PDF: - Pass a markdown string as 'content'. write_pdf(path="doc.pdf", content="# Title\n\nBody text...") 2. MODIFY EXISTING PDF: - Pass array of operations as 'content'. - NEVER overwrite the original file. - ALWAYS provide a new filename in 'outputPath'. - After modifying, show original file path and new file path to user. write_pdf(path="doc.pdf", content=[ { type: "delete", pageIndexes: [0, 2] }, { type: "insert", pageIndex: 1, markdown: "# New Page" } ]) OPERATIONS: - delete: Remove pages by 0-based index. { type: "delete", pageIndexes: [0, 1, 5] } - insert: Add pages at a specific 0-based index. { type: "insert", pageIndex: 0, markdown: "..." } { type: "insert", pageIndex: 5, sourcePdfPath: "/path/to/source.pdf" } PAGE BREAKS: To force a page break, use this HTML element: <div style="page-break-before: always;"></div> Example: "# Page 1\n\n<div style=\"page-break-before: always;\"></div>\n\n# Page 2" ADVANCED STYLING: HTML/CSS and inline SVG are supported for: - Text styling: colors, sizes, alignment, highlights - Boxes: borders, backgrounds, padding, rounded corners - SVG graphics: charts, diagrams, icons, shapes - Images: <img src="/absolute/path/image.jpg" width="300" /> or  Supports standard markdown features including headers, lists, code blocks, tables, and basic formatting. Only works within allowed directories. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. 🐳 KUBERNETES: Prefer paths within mounted directories: /home/appuser. When users ask about file locations, check these mounted paths first. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Create a new directory or ensure a directory exists. Can create multiple nested directories in one operation. Only works within allowed directories. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. 🐳 KUBERNETES: Prefer paths within mounted directories: /home/appuser. When users ask about file locations, check these mounted paths first. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Get a detailed listing of all files and directories in a specified path. Use this instead of 'execute_command' with ls/dir commands. Results distinguish between files and directories with [FILE] and [DIR] prefixes. Supports recursive listing with the 'depth' parameter (default: 2): - depth=1: Only direct contents of the directory - depth=2: Contents plus one level of subdirectories - depth=3+: Multiple levels deep CONTEXT OVERFLOW PROTECTION: - Top-level directory shows ALL items - Nested directories are limited to 100 items maximum per directory - When a nested directory has more than 100 items, you'll see a warning like: [WARNING] node_modules: 500 items hidden (showing first 100 of 600 total) - This prevents overwhelming the context with large directories like node_modules Results show full relative paths from the root directory being listed. Example output with depth=2: [DIR] src [FILE] src/index.ts [DIR] src/tools [FILE] src/tools/filesystem.ts If a directory cannot be accessed, it will show [DENIED] instead. If a path does not exist, it will show [NOT_FOUND] instead. Only works within allowed directories. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. 🐳 KUBERNETES: Prefer paths within mounted directories: /home/appuser. When users ask about file locations, check these mounted paths first. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Move or rename files and directories. Can move files between directories and rename them in a single operation. Both source and destination must be within allowed directories. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. 🐳 KUBERNETES: Prefer paths within mounted directories: /home/appuser. When users ask about file locations, check these mounted paths first. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Start a streaming search that can return results progressively. SEARCH STRATEGY GUIDE: Choose the right search type based on what the user is looking for: USE searchType="files" WHEN: - User asks for specific files: "find package.json", "locate config files" - Pattern looks like a filename: "*.js", "README.md", "test-*.tsx" - User wants to find files by name/extension: "all TypeScript files", "Python scripts" - Looking for configuration/setup files: ".env", "dockerfile", "tsconfig.json" USE searchType="content" WHEN: - User asks about code/logic: "authentication logic", "error handling", "API calls" - Looking for functions/variables: "getUserData function", "useState hook" - Searching for text/comments: "TODO items", "FIXME comments", "documentation" - Finding patterns in code: "console.log statements", "import statements" - User describes functionality: "components that handle login", "files with database queries" WHEN UNSURE OR USER REQUEST IS AMBIGUOUS: Run TWO searches in parallel - one for files and one for content: Example approach for ambiguous queries like "find authentication stuff": 1. Start file search: searchType="files", pattern="auth" 2. Simultaneously start content search: searchType="content", pattern="authentication" 3. Present combined results: "Found 3 auth-related files and 8 files containing authentication code" SEARCH TYPES: - searchType="files": Find files by name (pattern matches file names) - searchType="content": Search inside files for text patterns PATTERN MATCHING MODES: - Default (literalSearch=false): Patterns are treated as regular expressions - Literal (literalSearch=true): Patterns are treated as exact strings WHEN TO USE literalSearch=true: Use literal search when searching for code patterns with special characters: - Function calls with parentheses and quotes - Array access with brackets - Object methods with dots and parentheses - File paths with backslashes - Any pattern containing: . * + ? ^ $ { } [ ] | \ ( ) IMPORTANT PARAMETERS: - pattern: What to search for (file names OR content text) - literalSearch: Use exact string matching instead of regex (default: false) - filePattern: Optional filter to limit search to specific file types (e.g., "*.js", "package.json") - ignoreCase: Case-insensitive search (default: true). Works for both file names and content. - earlyTermination: Stop search early when exact filename match is found (optional: defaults to true for file searches, false for content searches) DECISION EXAMPLES: - "find package.json" → searchType="files", pattern="package.json" (specific file) - "find authentication components" → searchType="content", pattern="authentication" (looking for functionality) - "locate all React components" → searchTy…
Get more results from an active search with offset-based pagination. Supports partial result reading with: - 'offset' (start result index, default: 0) * Positive: Start from result N (0-based indexing) * Negative: Read last N results from end (tail behavior) - 'length' (max results to read, default: 100) * Used with positive offsets for range reading * Ignored when offset is negative (reads all requested tail results) Examples: - offset: 0, length: 100 → First 100 results - offset: 200, length: 50 → Results 200-249 - offset: -20 → Last 20 results - offset: -5, length: 10 → Last 5 results (length ignored) Returns only results in the specified range, along with search status. Works like read_process_output - call this repeatedly to get progressive results from a search started with start_search. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Stop an active search. Stops the background search process gracefully. Use this when you've found what you need or if a search is taking too long. Similar to force_terminate for terminal processes. The search will still be available for reading final results until it's automatically cleaned up after 5 minutes. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
List all active searches. Shows search IDs, search types, patterns, status, and runtime. Similar to list_sessions for terminal processes. Useful for managing multiple concurrent searches. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Retrieve detailed metadata about a file or directory including: - size - creation time - last modified time - permissions - type - lineCount (for text files) - lastLine (zero-indexed number of last line, for text files) - appendPosition (line number for appending, for text files) - sheets (for Excel files - array of {name, rowCount, colCount}) Only works within allowed directories. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. 🐳 KUBERNETES: Prefer paths within mounted directories: /home/appuser. When users ask about file locations, check these mounted paths first. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Apply surgical edits to files. BEST PRACTICE: Make multiple small, focused edits rather than one large edit. Each edit_block call should change only what needs to be changed - include just enough context to uniquely identify the text being modified. FORMAT HANDLING (by extension): EXCEL FILES (.xlsx, .xls, .xlsm) - Range Update mode: Takes: - file_path: Path to the Excel file - range: ALWAYS use FROM:TO format - "SheetName!A1:C10" or "SheetName!C1:C1" - content: 2D array, e.g., [["H1","H2"],["R1","R2"]] TEXT FILES - Find/Replace mode: Takes: - file_path: Path to the file to edit - old_string: Text to replace - new_string: Replacement text - expected_replacements: Optional number of replacements (default: 1) DOCX FILES (.docx) - XML Find/Replace mode: Takes same parameters as text files (old_string, new_string, expected_replacements). Operates on the pretty-printed XML inside the DOCX — the same XML you see from read_file with offset/length. Copy XML fragments from read output as old_string. After editing, the XML is repacked into a valid DOCX. Also searches headers/footers if not found in document body. Examples: - Replace text: old_string="<w:t>Old Text</w:t>" new_string="<w:t>New Text</w:t>" - Change style: old_string='<w:pStyle w:val="Normal"/>' new_string='<w:pStyle w:val="Heading1"/>' - Add content: include surrounding XML context in old_string, add new elements in new_string By default, replaces only ONE occurrence of the search text. To replace multiple occurrences, provide expected_replacements with the exact number of matches expected. UNIQUENESS REQUIREMENT: When expected_replacements=1 (default), include the minimal amount of context necessary (typically 1-3 lines) before and after the change point, with exact whitespace and indentation. When editing multiple sections, make separate edit_block calls for each distinct change rather than one large replacement. When a close but non-exact match is found, a character-level diff is shown in the format: common_prefix{-removed-}{+added+}common_suffix to help you identify what's different. Similar to write_file, there is a configurable line limit (fileWriteLineLimit) that warns if the edited file exceeds this limit. If this happens, consider breaking your edits into smaller, more focused changes. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. 🐳 KUBERNETES: Prefer paths within mounted directories: /home/appuser. When users ask about file locations, check these mounted paths first. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Start a new terminal process with intelligent state detection. PRIMARY TOOL FOR FILE ANALYSIS AND DATA PROCESSING This is the ONLY correct tool for analyzing local files (CSV, JSON, logs, etc.). The analysis tool CANNOT access local files and WILL FAIL - always use processes for file-based work. CRITICAL RULE: For ANY local file work, ALWAYS use this tool + interact_with_process, NEVER use analysis/REPL tool. Running on Linux (Kubernetes Pod). Default shell: bash. 🐳 KUBERNETES POD ENVIRONMENT DETECTED: This Desktop Commander instance is running inside a Kubernetes pod. Namespace: aigc AVAILABLE MOUNTED DIRECTORIES: - /home/appuser (read-write) - Host folder: appuser IMPORTANT: When users ask about files, FIRST check mounted directories above. Files outside these paths will be lost when the container stops. Always suggest using mounted directories for file operations. PATH TRANSLATION IN DOCKER: When users provide host paths, translate to container paths: Windows: "C:\projects\data\file.txt" → "/home/projects/data/file.txt" Linux/Mac: "/Users/john/projects/data/file.txt" → "/home/projects/data/file.txt" Rules: Remove drive letter/user prefix, keep full folder structure, mount to /home/ NOTE: Desktop Commander Docker installer mounts host folders to /home/[folder-name]. Container: mcpso-tanstack-59569ff95b-ht5gv LINUX-SPECIFIC NOTES: - Package managers vary by distro: apt, yum, dnf, pacman, zypper - Python 3 might be 'python3' command, not 'python' - Standard Unix shell tools available (grep, awk, sed, etc.) - File permissions and ownership important for many operations - Systemd services common on modern distributions REQUIRED WORKFLOW FOR LOCAL FILES: 1. start_process("python3 -i") - Start Python REPL for data analysis 2. interact_with_process(pid, "import pandas as pd, numpy as np") 3. interact_with_process(pid, "df = pd.read_csv('/absolute/path/file.csv')") 4. interact_with_process(pid, "print(df.describe())") 5. Continue analysis with pandas, matplotlib, seaborn, etc. COMMON FILE ANALYSIS PATTERNS: • start_process("python3 -i") → Python REPL for data analysis (RECOMMENDED) • start_process("node -i") → Node.js REPL for JSON processing • start_process("node:local") → Node.js on MCP server (stateless, ES imports, all code in one call) • start_process("cut -d',' -f1 file.csv | sort | uniq -c") → Quick CSV analysis • start_process("wc -l /path/file.csv") → Line counting • start_process("head -10 /path/file.csv") → File preview BINARY FILE SUPPORT: For PDF, Excel, Word, archives, databases, and other binary formats, use process tools with appropriate libraries or command-line utilities. INTERACTIVE PROCESSES FOR DATA ANALYSIS: For code/calculations, use in this priority order: 1. start_process("python3 -i") - Python REPL (preferred) 2. start_process("node -i") - Node.js REPL (when Python unavailable) 3. start_process("node:local") - Node.js fallback (when node -i fails) 4. Use interact_with_process() to send commands 5. Use read_process_output() to get responses When Python is unavailable, prefer Node.js over shell for calculations. Node.js: Always use ES imp…
Read output from a running process with file-like pagination support. Supports partial output reading with offset and length parameters (like read_file): - 'offset' (start line, default: 0) * offset=0: Read NEW output since last read (default, like old behavior) * Positive: Read from absolute line position * Negative: Read last N lines from end (tail behavior) - 'length' (max lines to read, default: configurable via 'fileReadLineLimit' setting) Examples: - offset: 0, length: 100 → First 100 NEW lines since last read - offset: 0 → All new lines (respects config limit) - offset: 500, length: 50 → Lines 500-549 (absolute position) - offset: -20 → Last 20 lines (tail) - offset: -50, length: 10 → Start 50 from end, read 10 lines OUTPUT PROTECTION: - Uses same fileReadLineLimit as read_file (default: 1000 lines) - Returns status like: [Reading 100 lines from line 0 (total: 5000 lines, 4900 remaining)] - Prevents context overflow from verbose processes SMART FEATURES: - For offset=0, waits up to timeout_ms for new output to arrive - Detects REPL prompts and process completion - Shows process state (waiting for input, finished, etc.) DETECTION STATES: Process waiting for input (ready for interact_with_process) Process finished execution Timeout reached (may still be running) This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Send input to a running process and automatically receive the response. CRITICAL: THIS IS THE PRIMARY TOOL FOR ALL LOCAL FILE ANALYSIS For ANY local file analysis (CSV, JSON, data processing), ALWAYS use this instead of the analysis tool. The analysis tool CANNOT access local files and WILL FAIL - use processes for ALL file-based work. FILE ANALYSIS PRIORITY ORDER (MANDATORY): 1. ALWAYS FIRST: Use this tool (start_process + interact_with_process) for local data analysis 2. ALTERNATIVE: Use command-line tools (cut, awk, grep) for quick processing 3. NEVER EVER: Use analysis tool for local file access (IT WILL FAIL) REQUIRED INTERACTIVE WORKFLOW FOR FILE ANALYSIS: 1. Start REPL: start_process("python3 -i") 2. Load libraries: interact_with_process(pid, "import pandas as pd, numpy as np") 3. Read file: interact_with_process(pid, "df = pd.read_csv('/absolute/path/file.csv')") 4. Analyze: interact_with_process(pid, "print(df.describe())") 5. Continue: interact_with_process(pid, "df.groupby('column').size()") BINARY FILE PROCESSING WORKFLOWS: Use appropriate Python libraries (PyPDF2, pandas, docx2txt, etc.) or command-line tools for binary file analysis. SMART DETECTION: - Automatically waits for REPL prompt (>>>, >, etc.) - Detects errors and completion states - Early exit prevents timeout delays - Clean output formatting (removes prompts) SUPPORTED REPLs: - Python: python3 -i (RECOMMENDED for data analysis) - Node.js: node -i - R: R - Julia: julia - Shell: bash, zsh - Database: mysql, postgres PARAMETERS: - pid: Process ID from start_process - input: Code/command to execute - timeout_ms: Max wait (default: 8000ms) - wait_for_prompt: Auto-wait for response (default: true) - verbose_timing: Enable detailed performance telemetry (default: false) Returns execution result with status indicators. PERFORMANCE DEBUGGING (verbose_timing parameter): Set verbose_timing: true to get detailed timing information including: - Exit reason (early_exit_quick_pattern, early_exit_periodic_check, process_finished, timeout, no_wait) - Total duration and time to first output - Complete timeline of all output events with timestamps - Which detection mechanism triggered early exit Use this to identify slow interactions and optimize detection patterns. ALWAYS USE FOR: CSV analysis, JSON processing, file statistics, data visualization prep, ANY local file work NEVER USE ANALYSIS TOOL FOR: Local file access (it cannot read files from disk and WILL FAIL) This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Force terminate a running terminal session. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
List all active terminal sessions. Shows session status including: - PID: Process identifier - Blocked: Whether session is waiting for input - Runtime: How long the session has been running DEBUGGING REPLs: - "Blocked: true" often means REPL is waiting for input - Use this to verify sessions are running before sending input - Long runtime with blocked status may indicate stuck process This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
List all running processes. Returns process information including PID, command name, CPU usage, and memory usage. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Terminate a running process by PID. Use with caution as this will forcefully terminate the specified process. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Get usage statistics for debugging and analysis. Returns summary of tool usage, success/failure rates, and performance metrics. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Get recent tool call history with their arguments and outputs. Returns chronological list of tool calls made during this session. Useful for: - Onboarding new chats about work already done - Recovering context after chat history loss - Debugging tool call sequences Note: Does not track its own calls or other meta/query tools. History kept in memory (last 1000 calls, lost on restart). This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Open feedback form in browser to provide feedback about Desktop Commander. IMPORTANT: This tool simply opens the feedback form - no pre-filling available. The user will fill out the form manually in their browser. WORKFLOW: 1. When user agrees to give feedback, just call this tool immediately 2. No need to ask questions or collect information 3. Tool opens form with only usage statistics pre-filled automatically: - tool_call_count: Number of commands they've made - days_using: How many days they've used Desktop Commander - platform: Their operating system (Mac/Windows/Linux) - client_id: Analytics identifier All survey questions will be answered directly in the form: - Job title and technical comfort level - Company URL for industry context - Other AI tools they use - Desktop Commander's biggest advantage - How they typically use it - Recommendation likelihood (0-10) - User study participation interest - Email and any additional feedback EXAMPLE INTERACTION: User: "sure, I'll give feedback" Claude: "Perfect! Let me open the feedback form for you." [calls tool immediately] No parameters are needed - just call the tool to open the form. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Retrieve a specific Desktop Commander onboarding prompt by ID and execute it. SIMPLIFIED ONBOARDING V2: This tool only supports direct prompt retrieval. The onboarding system presents 5 options as a simple numbered list: 1. Organize my Downloads folder (promptId: 'onb2_01') 2. Explain a codebase or repository (promptId: 'onb2_02') 3. Create organized knowledge base (promptId: 'onb2_03') 4. Analyze a data file (promptId: 'onb2_04') 5. Check system health and resources (promptId: 'onb2_05') USAGE: When user says "1", "2", "3", "4", or "5" from onboarding: - "1" → get_prompts(action='get_prompt', promptId='onb2_01') - "2" → get_prompts(action='get_prompt', promptId='onb2_02') - "3" → get_prompts(action='get_prompt', promptId='onb2_03') - "4" → get_prompts(action='get_prompt', promptId='onb2_04') - "5" → get_prompts(action='get_prompt', promptId='onb2_05') The prompt content will be injected and execution begins immediately. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
Desktop Commander MCP is a Model Context Protocol server that enables AI assistants to search, update, manage files, and run terminal commands on a user's computer. It extends the MCP Filesystem Server with additional search-and-replace editing, process management, and support for Excel, PDF, and DOCX file types. It is designed for developers and power users who want to integrate AI tools (like Claude Desktop) directly with their local development environment.
Install via one of six methods: npx @wonderwhy-er/desktop-commander@latest setup (auto‑updating, requires Node.js), a bash script installer for macOS, Smithery, manual addition to claude_desktop_config.json, a local git clone (manual updates), or a Docker container (no Node.js required). After installation, restart Claude Desktop or your MCP client. The server exposes tools for file operations, command execution, process management, and data analysis. The optional Desktop Commander App provides a dedicated UI with live file previews and support for multiple AI models.
You can install it using `npx @wonderwhy-er/desktop-commander@latest setup`, a bash script, via Smithery, manually adding to `claude_desktop_config.json`, cloning the repository, or using a Docker image. See the installation options in the README for details.
Yes, for installation Options 1, 2, 3, 4, and 6 (Docker) – the server updates automatically when you restart Claude. Option 5 (local clone) requires manual git pulls.
Yes. Option 6 provides a Docker‑based installation that runs in an isolated container. You must have Docker Desktop installed and running. The container can mount host folders for file access.
SOP software for small and medium businesses. Connect Claude, ChatGPT or any MCP-capable AI to search, draft, update and publish SOPs, policies and trainings in your systemHUB account. OAuth sign-in. Included on Accelera
Social media management for AI agents. PostPlanify MCP server lets Claude, ChatGPT, Cursor and other AI assistants schedule social media posts to Instagram, TikTok, LinkedIn, X, Facebook, YouTube, Threads, Pinterest, Bl
Genchi shows engineering leaders a prediction of which projects are heading for a missed deadline and which aren't, from the people doing the work. Giving every engineer a way to be heard, this prediction comes from thei
Human-in-the-loop decision-making by hybrid jury. Tribeunal is a decision platform where humans and AI agents open cases, weigh evidence and vote. 41 MCP tools + eight Agent Skills, incl. long-poll verdict awaiting, arbi
Incident reporting and claims management for multi-location businesses: incidents, claims, tasks, risk checks and inspections, with role and location limits on every call.
评论