Executes whitelisted shell commands remotely with standard input support.
Most file and storage access work still happens through a UI a human drives. Shell Command Executor MCP server moves it into the conversation instead. Executes whitelisted shell commands remotely with standard input support.
A secure shell command execution server implementing the Model Context Protocol (MCP). This server allows remote execution of whitelisted shell commands with support for stdin input.
The server publishes 1 tool. What each one is for:
Configuration — The Configuration tool exposed by this serverConfiguration is passed through the environment: ALLOW_COMMANDS, SECRET_TOKEN, ACCESS_KEY, PRIVATE_KEY, MCP_SHELL_SAFE_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Shell Command Executor's toolset — Configuration — is a fair guide to whether it matches your workflow. It is maintained by tumf; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Configuration | The Configuration tool exposed by this server. |
```json
{
"mcpServers": {
"shell": {
"command": "uvx",
"args": [
"mcp-shell-server"
],
"env": {
"ALLOW_COMMANDS": "ls,cat,pwd,grep,wc,touch,find"
}
},
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ALLOW_COMMANDS | Configuration value read at startup. | Optional |
| SECRET_TOKEN | Credential the server authenticates with. | Yes |
| ACCESS_KEY | Credential the server authenticates with. | Yes |
| PRIVATE_KEY | Credential the server authenticates with. | Yes |
| MCP_SHELL_SAFE_PATH | Filesystem location the server is allowed to use. | Optional |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.