Desktop Commander MCP Server | Docker MCP Catalog

Name	Description
`create_directory`	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. 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.
`edit_block`	Edit Text Block
`force_terminate`	Force Terminate Process
`get_config`	Get Configuration
`get_file_info`	Get File Information
`get_more_search_results`	Get Search Results
`get_prompts`	Browse and retrieve curated Desktop Commander prompts for various tasks and workflows. IMPORTANT: When displaying prompt lists to users, do NOT show the internal prompt IDs (like 'onb_001'). These IDs are for your reference only. Show users only the prompt titles and descriptions. The IDs will be provided in the response metadata for your use. DESKTOP COMMANDER INTRODUCTION: If a user asks "what is Desktop Commander?" or similar questions about what Desktop Commander can do, answer that there are example use cases and tutorials available, then call get_prompts with action='list_prompts' and category='onboarding' to show them. ACTIONS: - list_categories: Show all available prompt categories - list_prompts: List prompts (optionally filtered by category) - get_prompt: Retrieve and execute a specific prompt by ID WORKFLOW: 1. Use list_categories to see available categories 2. Use list_prompts to browse prompts in a category 3. Use get_prompt with promptId to retrieve and start using a prompt EXAMPLES: - get_prompts(action='list_categories') - See all categories - get_prompts(action='list_prompts', category='onboarding') - See onboarding prompts - get_prompts(action='get_prompt', promptId='onb_001') - Get a specific prompt The get_prompt action will automatically inject the prompt content and begin execution. Perfect for discovering proven workflows and getting started with Desktop Commander. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.
`get_recent_tool_calls`	Get Recent Tool Calls
`get_usage_stats`	Get Usage Statistics
`give_feedback_to_desktop_commander`	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.
`interact_with_process`	Send Input to Process
`kill_process`	Kill Process
`list_directory`	List Directory Contents
`list_processes`	List Running Processes
`list_searches`	List Active Searches
`list_sessions`	List Terminal Sessions
`move_file`	Move/Rename File
`read_file`	Read File or URL
`read_multiple_files`	Read Multiple Files
`read_process_output`	Read Process Output
`set_config_value`	Set Configuration Value
`start_process`	Start Terminal Process
`start_search`	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" → searchType="files", pattern=".tsx" or ".jsx" (file pattern) - "find TODO comments" → searchType="content", pattern="TODO" (text in files) - "show me login files" → AMBIGUOUS → run both: files with "login" AND content with "login" - "find config" → AMBIGUOUS → run both: config files AND files containing config code COMPREHENSIVE SEARCH EXAMPLES: - Find package.json files: searchType="files", pattern="package.json" - Find all JS files: searchType="files", pattern=".js" - Search for TODO in code: searchType="content", pattern="TODO", filePattern=".js\|.ts" - Search for exact code: searchType="content", pattern="toast.error('test')", literalSearch=true - Ambiguous request "find auth stuff": Run two searches: 1. searchType="files", pattern="auth" 2. searchType="content", pattern="authentication" PRO TIP: When user requests are ambiguous about whether they want files or content, run both searches concurrently and combine results for comprehensive coverage. Unlike regular search tools, this starts a background search process and returns immediately with a session ID. Use get_more_search_results to get results as they come in, and stop_search to stop the search early if needed. Perfect for large directories where you want to see results immediately and have the option to cancel if the search takes too long or you find what you need. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. 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.
`stop_search`	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.
`write_file`	Write File

create_directory

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. 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.

edit_block

Edit Text Block

force_terminate

Force Terminate Process

get_config

Get Configuration

get_file_info

Get File Information

get_more_search_results

Get Search Results

get_prompts

Browse and retrieve curated Desktop Commander prompts for various tasks and workflows. IMPORTANT: When displaying prompt lists to users, do NOT show the internal prompt IDs (like 'onb_001'). These IDs are for your reference only. Show users only the prompt titles and descriptions. The IDs will be provided in the response metadata for your use. DESKTOP COMMANDER INTRODUCTION: If a user asks "what is Desktop Commander?" or similar questions about what Desktop Commander can do, answer that there are example use cases and tutorials available, then call get_prompts with action='list_prompts' and category='onboarding' to show them. ACTIONS: - list_categories: Show all available prompt categories - list_prompts: List prompts (optionally filtered by category) - get_prompt: Retrieve and execute a specific prompt by ID WORKFLOW: 1. Use list_categories to see available categories 2. Use list_prompts to browse prompts in a category 3. Use get_prompt with promptId to retrieve and start using a prompt EXAMPLES: - get_prompts(action='list_categories') - See all categories - get_prompts(action='list_prompts', category='onboarding') - See onboarding prompts - get_prompts(action='get_prompt', promptId='onb_001') - Get a specific prompt The get_prompt action will automatically inject the prompt content and begin execution. Perfect for discovering proven workflows and getting started with Desktop Commander. This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.

get_recent_tool_calls

Get Recent Tool Calls

get_usage_stats

Get Usage Statistics

give_feedback_to_desktop_commander

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.

interact_with_process

Send Input to Process

kill_process

Kill Process

list_directory

List Directory Contents

list_processes

List Running Processes

list_searches

List Active Searches

list_sessions

List Terminal Sessions

move_file

Move/Rename File

read_file

Read File or URL

read_multiple_files

Read Multiple Files

read_process_output

Read Process Output

set_config_value

Set Configuration Value

start_process

Start Terminal Process

start_search

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" → searchType="files", pattern="*.tsx" or "*.jsx" (file pattern) - "find TODO comments" → searchType="content", pattern="TODO" (text in files) - "show me login files" → AMBIGUOUS → run both: files with "login" AND content with "login" - "find config" → AMBIGUOUS → run both: config files AND files containing config code COMPREHENSIVE SEARCH EXAMPLES: - Find package.json files: searchType="files", pattern="package.json" - Find all JS files: searchType="files", pattern="*.js" - Search for TODO in code: searchType="content", pattern="TODO", filePattern="*.js|*.ts" - Search for exact code: searchType="content", pattern="toast.error('test')", literalSearch=true - Ambiguous request "find auth stuff": Run two searches: 1. searchType="files", pattern="auth" 2. searchType="content", pattern="authentication" PRO TIP: When user requests are ambiguous about whether they want files or content, run both searches concurrently and combine results for comprehensive coverage. Unlike regular search tools, this starts a background search process and returns immediately with a session ID. Use get_more_search_results to get results as they come in, and stop_search to stop the search early if needed. Perfect for large directories where you want to see results immediately and have the option to cancel if the search takes too long or you find what you need. IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. 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.

stop_search

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.

write_file

Write File

Desktop Commander

Related servers

AWS Core MCP Server

Context7

Docker Hub

GitHub Official