cmdshellmcp
Related Servers
Alternatives to cmdshellmcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA secure MCP server that exposes local filesystem operations to AI clients with sandboxed access and runtime directory changes.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that equips AI agents with real-world tools including file operations, read-only MySQL queries, web summarization, safe calculations, and system info. It uses stdio transport and enforces safety guardrails like SELECT-only database access and AST-based math evaluation.MIT
- FlicenseAqualityDmaintenanceA minimal MCP server that lets AI hosts execute shell commands in a sandboxed workspace directory.1-
- AlicenseBqualityAmaintenanceA secure MCP server for shell operations, terminal management, and process control, enabling AI assistants to safely execute commands and manage interactive sessions.13150 npm6MIT
- AlicenseNot gradedqualityDmaintenanceA modular MCP server providing file operations, web search, URL scraping, and sandboxed command execution for LLM interactions.1MIT
- AlicenseNot gradedqualityDmaintenanceSecure MCP server for controlled terminal access, enabling AI assistants to run whitelisted commands with configurable working directory, timeout, and output limits.MIT
TDQS
Scored across 12 tools
Each dedicated file tool targets a specific operation (read/write/edit/patch/delete/copy/move/list/mkdir/rmdir), so they are mostly distinct. However, the general cmdshell tool overlaps with many of these (ls, cat, sed, mkdir, cp, mv), which can create ambiguity about whether to use a dedicated tool or a shell command. The detailed descriptions help but overlap remains.
Most file tools use camelCase verb_noun (writeFile, readFile, listFiles, copyFile, etc.), but fetch, cmdshell, mkdir, and rmdir break the pattern with lowercase or Unix-style names. The mix is still readable, but not fully consistent.
12 tools is a reasonable, well-scoped set for a sandboxed file/shell server. Each core operation (create, read, update, delete, directory management, shell, fetch) has a clear place, and the count is within the typical 3-15 range.
The server covers the main file lifecycle: create (writeFile), read (readFile), update (editFile/applyPatch), delete (deleteFile), plus copy, move, directory create/list/remove, and a general command runner. Minor gaps exist (e.g., append-specific operation, metadata/stat, recursive directory deletion), but agents can work around most via cmdshell or editing tools.