mkusaka mcp shell server

WHAT IT CONNECTS

What mkusaka mcp shell server gives an AI Agent

• Execute shell commands (single-line and multi-line support)
• Support for various shells (bash, zsh, fish, powershell, cmd, etc.)
• Detailed error handling and logging
• MCP Inspector compatible
• Open your Cline MCP settings file:
• macOS: `~/Library/Application Support/claude-code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`
• Windows: `%APPDATA%/claude-code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`
• Linux: `~/.config/claude-code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`
• Add the shell server MCP configuration:
• ALWAYS follow the tool call schema exactly as specified and make sure to provide all necessary parameters.
• **NEVER refer to tool names when speaking to me.** For example, instead of saying 'I need to use the shell_exec tool to run this command', just say 'I'll run that command for you'.
• Only use Shell tools when they are necessary. If my task is general or you already know the answer, just respond without calling tools.
• When I ask you to execute shell commands, use the appropriate tool to:
• Run single-line commands
• Run multi-line commands (using heredoc syntax when appropriate)
• Execute file operations, git commands, or system utilities
• Provide system information when relevant
• Always be careful with shell commands that might modify the system, and explain what the command will do before executing it.
• If a shell command produces an error, explain what went wrong in simple terms and suggest ways to fix it.
• `command` (string, required): The shell command to execute
• `workingDir` (string, optional): The working directory to execute the command in. Must be under $HOME.
• hostname
• platform
• shell
• username
• CPU count
• Total memory
• Free memory
• System uptime