by kevinwatt
Automate system tasks securely with Shell Command Executor—perfect for knowledge database software and CRM relationship
Executes whitelisted shell commands safely with security controls like timeouts, output limits, and resource monitoring. Provides basic file system operations and system information commands for LLMs.
Shell Command Executor is a community-built MCP server published by kevinwatt that provides AI assistants with tools and capabilities via the Model Context Protocol. Automate system tasks securely with Shell Command Executor—perfect for knowledge database software and CRM relationship It is categorized under developer tools. This server exposes 20 tools that AI clients can invoke during conversations and coding sessions.
You can install Shell Command Executor in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Shell Command Executor is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Shell Command Executor reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Shell Command Executor is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
I recommend Shell Command Executor for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Shell Command Executor is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Shell Command Executor is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Strong directory entry: Shell Command Executor surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Useful MCP listing: Shell Command Executor is the kind of server we cite when onboarding engineers to host + tool permissions.
Strong directory entry: Shell Command Executor surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Useful MCP listing: Shell Command Executor is the kind of server we cite when onboarding engineers to host + tool permissions.
Shell Command Executor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 69
Shell command execution MCP server
An MCP server implementation that provides secure shell command execution capabilities for LLMs.
npm install @kevinwatt/shell-mcp
{
"mcpServers": {
"shell": {
"command": "npx",
"args": [
"-y",
"@kevinwatt/shell-mcp"
]
}
}
}
command (string, required): Command to executeargs (array, optional): Command argumentstimeout (number, optional): Execution timeout in msAsk your LLM to:
"Show current directory using shell_pwd"
"List files using shell_ls with -l argument"
"Check disk usage using shell_df with -h argument"
If needed, start the server manually:
npx @kevinwatt/shell-mcp
# Install dependencies
npm install
# Watch mode
npm run watch
# Run tests
npm test
# Lint
npm run lint
MIT © Dewei Yen
The following shell commands are available:
| Command | Description | Allowed Arguments |
|---|---|---|
| ls | List directory contents | -l, -a, -h, -R, --help, * |
| cat | Concatenate and display file contents | -n, -b, --help, * |
| pwd | Show current working directory | None |
| df | Show disk usage | -h, -T, --help |
| echo | Display text | Any text |
| ps | Show process status | -e, -f, -u, --help |
| free | Show memory usage | -h, -m, -g, --help |
| uptime | Show system uptime | None |
| date | Show system date and time | +%Y-%m-%d, +%H:%M:%S, --help |
| grep | Search text patterns in files | -i, -v, -n, -r, -l, --color, * |
| w | Show who is logged on and what they are doing | -h, -s, --no-header, --help |
| whois | Query WHOIS domain registration information | -H, * |
| find | Search for files in a directory hierarchy | -name, -type, -size, -mtime, * |
| netstat | Network connection information | -a, -n, -t, -u, -l, -p, --help |
| lspci | List PCI devices | -v, -k, -mm, -nn, --help |
| lsusb | List USB devices | -v, -t, -d, -s, --help |
| dig | DNS lookup utility | +short, +trace, +dnssec, @*, * |
| nslookup | Query DNS records | -type=, -query=, * |
| ip | Show network devices and interfaces | addr, link, route, neigh, -br, * |
| whereis | Locate binary, source and manual files | -b, -m, -s, * |
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.