Un servidor MCP (Protocolo de Contexto de Modelo) para ejecutar comandos de shell en múltiples plataformas (Windows, macOS, Linux). Este servidor proporciona una forma segura de ejecutar comandos de shell con mecanismos integrados de lista blanca y aprobación.
Ejecutar comandos de shell a través de MCP en Windows, macOS y Linux
Detección automática de plataforma y selección de shell
Soporte para múltiples shells:
Ventanas : cmd.exe, PowerShell
macOS : zsh, bash, sh
Linux : bash, sh, zsh
Lista blanca de comandos con niveles de seguridad:
Seguro : Comandos que se pueden ejecutar sin aprobación
Requiere aprobación : comandos que necesitan aprobación explícita antes de su ejecución
Prohibido : Comandos que están bloqueados explícitamente
Listas blancas de comandos específicos de la plataforma
Flujo de trabajo de aprobación sin bloqueo para comandos potencialmente peligrosos
Sistema de registro integral con registros basados en archivos
Herramientas integrales de gestión de comandos
Herramienta de información de plataforma para diagnóstico
Related MCP server: Mac Shell MCP Server
Para instalar Super Shell MCP Server para Claude Desktop automáticamente a través de Smithery :
npx -y @smithery/cli install @cfdude/super-shell-mcp --client claude# Clone the repository
git clone https://github.com/cfdude/super-shell-mcp.git
cd super-shell-mcp
# Install dependencies
npm install
# Build the project
npm run buildnpm startO directamente:
node build/index.jsTanto Roo Code como Claude Desktop utilizan un formato de configuración similar para los servidores MCP. A continuación, se explica cómo configurar el servidor MCP de Super Shell:
La forma más sencilla de usar Super Shell MCP es con NPX, que instala y ejecuta automáticamente el paquete desde npm sin necesidad de configuración manual. El paquete está disponible en NPM en https://www.npmjs.com/package/super-shell-mcp .
"super-shell": {
"command": "npx",
"args": [
"-y",
"super-shell-mcp"
],
"alwaysAllow": [],
"disabled": false
}"super-shell": {
"command": "npx",
"args": [
"-y",
"super-shell-mcp"
],
"alwaysAllow": false,
"disabled": false
}Si prefiere utilizar una instalación local, agregue lo siguiente a su archivo de configuración de Roo Code MCP (ubicado en ~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json ):
"super-shell": {
"command": "node",
"args": [
"/path/to/super-shell-mcp/build/index.js"
],
"alwaysAllow": [],
"disabled": false
}Opcionalmente, puede especificar un shell personalizado agregando un parámetro de shell:
"super-shell": {
"command": "node",
"args": [
"/path/to/super-shell-mcp/build/index.js",
"--shell=/usr/bin/bash"
],
"alwaysAllow": [],
"disabled": false
}Ejemplo de Windows 11
"super-shell": {
"command": "C:\\Program Files\\nodejs\\node.exe",
"args": [
"C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npx-cli.js",
"-y",
"super-shell-mcp",
"C:\\Users\\username"
],
"alwaysAllow": [],
"disabled": false
}Agregue lo siguiente a su archivo de configuración de Claude Desktop (ubicado en ~/Library/Application Support/Claude/claude_desktop_config.json ):
"super-shell": {
"command": "node",
"args": [
"/path/to/super-shell-mcp/build/index.js"
],
"alwaysAllow": false,
"disabled": false
}Para los usuarios de Windows, el archivo de configuración normalmente se encuentra en %APPDATA%\Claude\claude_desktop_config.json .
Shell predeterminado: cmd.exe (o PowerShell si está disponible)
Rutas de configuración:
Código Roo: %APPDATA%\Code\User\globalStorage\rooveterinaryinc.roo-cline\settings\cline_mcp_settings.json
Escritorio de Claude: %APPDATA%\Claude\claude_desktop_config.json
Ejemplos de rutas de shell:
cmd.exe: C:\\Windows\\System32\\cmd.exe
PowerShell: C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe
Núcleo de PowerShell: C:\\Program Files\\PowerShell\\7\\pwsh.exe
Shell predeterminado: /bin/zsh
Rutas de configuración:
Código Roo: ~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json
Escritorio de Claude: ~/Library/Application Support/Claude/claude_desktop_config.json
Ejemplos de rutas de shell:
zsh: /bin/zsh
bash: /bin/bash
sh: /bin/sh
Shell predeterminado: /bin/bash (o variable de entorno $SHELL)
Rutas de configuración:
Código Roo: ~/.config/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json
Escritorio de Claude: ~/.config/Claude/claude_desktop_config.json
Ejemplos de rutas de shell:
bash: /bin/bash
sh: /bin/sh
zsh: /usr/bin/zsh
Opcionalmente, puede especificar un shell personalizado:
"super-shell": {
"command": "node",
"args": [
"/path/to/super-shell-mcp/build/index.js",
"--shell=C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
],
"alwaysAllow": false,
"disabled": false
}Reemplace /path/to/super-shell-mcp con la ruta real donde clonó el repositorio.
Nota :
Para Roo Code: Se recomienda configurar
alwaysAllowcon una matriz vacía[]por razones de seguridad, ya que solicitará aprobación antes de ejecutar cualquier comando. Si desea permitir comandos específicos sin solicitar aprobación, puede agregar sus nombres a la matriz, por ejemplo:"alwaysAllow": ["execute_command", "get_whitelist"].Para Claude Desktop: Se recomienda configurar
alwaysAllowcomofalsepor razones de seguridad. Claude Desktop utiliza un valor booleano en lugar de una matriz, dondefalsesignifica que todos los comandos requieren aprobación ytruesignifica que todos los comandos se permiten sin solicitud.Importante : El parámetro
alwaysAllowlo procesa el cliente MCP (Roo Code o Claude Desktop), no el propio servidor MCP de Super Shell. El servidor funcionará correctamente con ambos formatos, ya que el cliente gestiona el proceso de aprobación antes de enviar las solicitudes al servidor.
El servidor expone las siguientes herramientas MCP:
get_platform_infoObtenga información sobre la plataforma y shell actuales.
{}execute_commandEjecutar un comando de shell en la plataforma actual.
{
"command": "ls",
"args": ["-la"]
}get_whitelistObtenga la lista de comandos incluidos en la lista blanca.
{}add_to_whitelistAñade un comando a la lista blanca.
{
"command": "python3",
"securityLevel": "safe",
"description": "Run Python 3 scripts"
}update_security_levelActualizar el nivel de seguridad de un comando incluido en la lista blanca.
{
"command": "python3",
"securityLevel": "requires_approval"
}remove_from_whitelistEliminar un comando de la lista blanca.
{
"command": "python3"
}get_pending_commandsObtenga la lista de comandos pendientes de aprobación.
{}approve_commandAprobar un comando pendiente.
{
"commandId": "command-uuid-here"
}deny_commandDenegar un comando pendiente.
{
"commandId": "command-uuid-here",
"reason": "This command is potentially dangerous"
}El servidor incluye listas blancas de comandos específicas de la plataforma que se seleccionan automáticamente en función de la plataforma detectada.
echo - Imprimir texto en la salida estándar
ls - Listar el contenido del directorio
pwd - Imprimir directorio de trabajo
echo - Imprimir texto en la salida estándar
cat - Concatenar e imprimir archivos
grep - Buscar patrones en archivos
find - Buscar archivos en una jerarquía de directorios
cd - Cambiar directorio
head - Salida de la primera parte de los archivos
tail - Muestra la última parte de los archivos
wc - Imprimir recuentos de nuevas líneas, palabras y bytes
dir - Lista el contenido del directorio
type - Mostrar el contenido de un archivo de texto
findstr - Busca cadenas en archivos
where - Localizar programas
whoami - Mostrar el usuario actual
hostname - Nombre de la computadora para mostrar
ver - Mostrar la versión del sistema operativo
copy - Copiar archivos
move - Mover archivos
mkdir - Crear directorios
rmdir - Eliminar directorios
rename - Cambiar el nombre de los archivos
attrib - Cambiar atributos de archivo
mv - Mover (renombrar) archivos
cp - Copiar archivos y directorios
mkdir - Crear directorios
touch - Cambiar las marcas de tiempo de los archivos o crear archivos vacíos
chmod - Cambiar los bits del modo de archivo
chown - Cambiar el propietario y el grupo del archivo
del - Eliminar archivos
erase - Eliminar archivos
format - Formatear un disco
runas - Ejecutar un programa como otro usuario
rm - Eliminar archivos o directorios
sudo - Ejecutar un comando como otro usuario
Todos los comandos se ejecutan con los permisos del usuario que ejecuta el servidor MCP
Los comandos que requieren aprobación se mantienen en una cola hasta que se aprueban explícitamente.
Los comandos prohibidos nunca se ejecutan
El servidor utiliza execFile de Node.js en lugar de exec para evitar la inyección de shell
Los argumentos se validan contra patrones permitidos cuando se especifican
Puedes ampliar la lista blanca con la herramienta add_to_whitelist . Por ejemplo:
{
"command": "npm",
"securityLevel": "requires_approval",
"description": "Node.js package manager"
}Super Shell MCP está disponible como un paquete npm en https://www.npmjs.com/package/super-shell-mcp .
El uso del método NPX (como se muestra en la Opción 1 de la sección Configuración) ofrece varias ventajas:
Sin configuración manual : no es necesario clonar el repositorio, instalar dependencias ni compilar el proyecto
Actualizaciones automáticas : siempre utiliza la última versión publicada
Compatibilidad entre plataformas : funciona de la misma manera en Windows, macOS y Linux.
Configuración simplificada : configuración más corta sin rutas absolutas
Mantenimiento reducido : no hay archivos locales que administrar ni actualizar
Si prefieres utilizar la última versión de desarrollo directamente desde GitHub:
"super-shell": {
"command": "npx",
"args": [
"-y",
"github:cfdude/super-shell-mcp"
],
"alwaysAllow": [], // For Roo Code
"disabled": false
}Si desea publicar su propia versión modificada en npm:
Actualice el package.json con sus datos
Asegúrese de que el campo "bin" esté configurado correctamente:
"bin": {
"super-shell-mcp": "./build/index.js"
}Publicar en npm:
npm publishPara una integración óptima con los clientes MCP que utilizan NPX, este proyecto sigue estas prácticas recomendadas:
Punto de entrada ejecutable : el archivo principal incluye una línea shebang ( #!/usr/bin/env node ) y se hace ejecutable durante la compilación.
Configuración del paquete :
"type": "module" - Garantiza que se utilicen los módulos ES
Campo "bin" : asigna el nombre del comando al punto de entrada
Campo "files" : especifica qué archivos incluir al publicar
Script "prepare" : garantiza que la compilación se realice durante la instalación
Configuración de TypeScript :
"module": "NodeNext" - Compatibilidad adecuada con módulos ES
"moduleResolution": "NodeNext" - Consistente con los módulos ES
Instalación y ejecución automática :
La configuración del cliente MCP utiliza npx -y para instalar y ejecutar automáticamente el paquete
Ninguna ventana de terminal está bloqueada ya que el proceso se ejecuta en segundo plano
Proceso de publicación :
# Update version in package.json
npm version patch # or minor/major as appropriate
# Build and publish
npm publishEstas prácticas garantizan que el cliente MCP pueda iniciar automáticamente el servidor MCP sin necesidad de una ventana de terminal independiente, lo que mejora la experiencia del usuario y la eficiencia operativa.
Política de ejecución de scripts de PowerShell
Problema : PowerShell puede bloquear la ejecución del script con el error "La ejecución de scripts está deshabilitada en este sistema".
Solución : ejecute PowerShell como administrador y ejecute Set-ExecutionPolicy RemoteSigned o utilice el parámetro -ExecutionPolicy Bypass al configurar el shell.
Separadores de ruta
Problema : Windows usa barras invertidas ( \ ) en las rutas, que deben escaparse en JSON
Solución : utilice barras invertidas dobles ( \\ ) en los archivos de configuración JSON, por ejemplo, C:\\Windows\\System32\\cmd.exe
Comando no encontrado
Problema : Windows no tiene comandos Unix como ls , grep , etc.
Solución : utilice equivalentes de Windows ( dir en lugar de ls , findstr en lugar de grep )
Permisos de Shell
Problema : Permiso denegado al ejecutar comandos
Solución : asegúrese de que el shell tenga los permisos adecuados con chmod +x /path/to/shell
Variables de entorno
Problema : Las variables de entorno no están disponibles en el servidor MCP
Solución : establezca variables de entorno en el archivo de perfil del shell ( .zshrc , .bashrc , etc.)
Problemas de detección de shell
Problema : el servidor no detecta el shell correcto
Solución : especifique explícitamente la ruta del shell en la configuración
Tiempo de espera de ejecución del comando
Problema : los comandos tardan demasiado y se agota el tiempo de espera
Solución : Aumente el valor de tiempo de espera en el constructor del servicio de comandos
El servidor incluye un sistema de registro integral que escribe registros en un archivo para facilitar la depuración y la supervisión:
Ubicación del archivo de registro
Predeterminado: logs/super-shell-mcp.log en el directorio del servidor
El directorio de registros se crea automáticamente y Git lo rastrea (con un archivo .gitkeep)
Los archivos de registro en sí se excluyen de Git a través de .gitignore
Contiene información detallada sobre las operaciones del servidor, la ejecución de comandos y el flujo de trabajo de aprobación.
Niveles de registro
INFO : Información operativa general
DEBUG : Información de depuración detallada
ERROR : Condiciones de error y excepciones
Visualización de registros
Utilice los comandos de visualización de archivos estándar para comprobar los registros:
# View the entire log
cat logs/super-shell-mcp.log
# Follow log updates in real-time
tail -f logs/super-shell-mcp.logContenido del registro
Inicio y configuración del servidor
Solicitudes y resultados de ejecución de comandos
Eventos de flujo de trabajo de aprobación (pendiente, aprobado, denegado)
Condiciones de error e información de solución de problemas
Gestión de listas blancas
Problema : Es necesario agregar comandos personalizados a la lista blanca
Solución : utilice la herramienta add_to_whitelist para agregar comandos específicos para su entorno
Este servidor MCP cuenta con la licencia MIT. Esto significa que puede usar, modificar y distribuir el software libremente, sujeto a los términos y condiciones de la licencia MIT. Para más detalles, consulte el archivo de LICENCIA en el repositorio del proyecto.
Add a command to the whitelist
| Name | Required | Description | Default |
|---|---|---|---|
| command | Yes | The command to whitelist | |
| securityLevel | Yes | Security level for the command | |
| description | No | Description of the command |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool adds to a whitelist, implying a write operation, but doesn't cover critical aspects like permissions required, whether it overwrites existing entries, error conditions, or side effects. This leaves significant gaps for an agent to understand the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, direct sentence that efficiently conveys the core action without any wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (a write operation with security implications), lack of annotations, and no output schema, the description is insufficient. It doesn't explain what happens after adding (e.g., success response, error handling), how it integrates with the security system, or prerequisites, leaving the agent with incomplete context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with clear documentation for all three parameters, including an enum for 'securityLevel'. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline score of 3 where the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Add') and resource ('command to the whitelist'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'update_security_level' or 'approve_command', which might have overlapping functionality in a security context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. For example, it doesn't clarify if this is for initial whitelisting versus updating existing entries, or how it relates to siblings like 'update_security_level' or 'remove_from_whitelist'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Approve a pending command
| Name | Required | Description | Default |
|---|---|---|---|
| commandId | Yes | ID of the command to approve |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation ('Approve') but doesn't specify permissions required, whether the action is reversible, or what happens after approval (e.g., does it trigger execution?). This leaves critical behavioral traits unclear for a tool that likely changes system state.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral outcomes, error conditions, or integration with sibling tools (e.g., how approval relates to 'execute_command'), leaving gaps in understanding the tool's role in the broader context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with the single parameter 'commandId' well-documented in the schema. The description adds no additional meaning about the parameter beyond what the schema provides, such as format examples or sourcing guidance, so it meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Approve') and the target resource ('a pending command'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'deny_command' beyond the opposite action, missing explicit differentiation that would warrant a score of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'deny_command' or 'execute_command', nor does it mention prerequisites such as needing a pending command from 'get_pending_commands'. This lack of contextual direction leaves the agent without usage instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Deny a pending command
| Name | Required | Description | Default |
|---|---|---|---|
| commandId | Yes | ID of the command to deny | |
| reason | No | Reason for denial |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. 'Deny' implies a mutation that changes command status, but the description doesn't disclose behavioral traits like required permissions, whether denial is reversible, what happens to the denied command, or any side effects. This is a significant gap for a mutation tool with zero annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of a command denial operation (a mutation with potential security implications), no annotations, no output schema, and sibling tools like 'approve_command', the description is incomplete. It lacks context on prerequisites, consequences, alternatives, or return values, leaving significant gaps for an AI agent to use it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both parameters (commandId and reason) adequately. The description doesn't add any meaning beyond what the schema provides, such as explaining what constitutes a valid reason or how the commandId is obtained. Baseline 3 is appropriate when schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Deny a pending command' clearly states the action (deny) and target resource (pending command). It's specific and unambiguous, though it doesn't explicitly differentiate from sibling tools like 'approve_command' or 'execute_command' beyond the verb choice.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a pending command ID), when denial is appropriate, or how it differs from 'approve_command' or other command-handling tools in the sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Execute a shell command on the current platform
| Name | Required | Description | Default |
|---|---|---|---|
| command | Yes | The command to execute | |
| args | No | Command arguments |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but lacks critical details such as security implications, permission requirements, whether it's destructive, rate limits, or output format. This is a significant gap for a tool that executes shell commands, which can have high-risk behaviors.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded and appropriately sized for its purpose, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of executing shell commands (potentially high-risk with no annotations) and lack of output schema, the description is incomplete. It fails to address security, permissions, or return values, leaving the agent with insufficient context for safe and effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with clear documentation for 'command' and 'args'. The description doesn't add any parameter-specific details beyond what the schema provides, such as examples or constraints, so it meets the baseline for high schema coverage without extra value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Execute') and resource ('a shell command on the current platform'), making the purpose understandable. However, it doesn't distinguish this tool from its siblings like 'approve_command' or 'deny_command', which appear to be related to command management but have different functions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. Given siblings like 'approve_command' and 'deny_command', it's unclear if 'execute_command' requires approval, operates independently, or has specific prerequisites, leaving the agent without usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the list of commands pending approval
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool retrieves pending commands but doesn't mention whether this requires special permissions, how results are formatted, if there are rate limits, or what happens if no commands are pending. For a security/approval-related tool, this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with no output schema, the description provides the minimum viable information about what it does. However, given the security/approval context and sibling tools that suggest this is part of a command management system, more information about permissions, return format, or typical usage patterns would be helpful.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't mention parameters since none exist, which is correct. Baseline for zero parameters is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and resource ('list of commands pending approval'), making the purpose immediately understandable. It doesn't specifically differentiate from siblings like 'execute_command' or 'approve_command', but the verb+resource combination is unambiguous in context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives like 'execute_command' or 'approve_command'. The description only states what it does, not when it should be used in relation to the sibling tools that manage command approval workflows.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get information about the current platform and shell
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but doesn't specify what information is returned (e.g., OS version, shell type, environment details), whether it requires permissions, or if there are rate limits. This leaves significant gaps for a tool with zero annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action ('Get information'), making it easy to parse, and every part of the sentence contributes to understanding the tool's function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is incomplete for a tool that retrieves system information. It doesn't explain what specific data is returned (e.g., platform details, shell version) or the format of the output, which is critical for an agent to use the tool effectively. This leaves too much ambiguity for practical use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. A baseline of 4 is applied as per the rules for tools with no parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Get') and resource ('information about the current platform and shell'), making it immediately understandable. However, it doesn't explicitly differentiate this tool from its siblings (like 'execute_command' or 'get_pending_commands'), which focus on command execution and management rather than platform metadata.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., use for system diagnostics or compatibility checks), or exclusions, leaving the agent to infer usage based on the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the list of whitelisted commands
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose whether this is a read-only operation, if it requires authentication, rate limits, or what format the returned list has. This is inadequate for a tool with zero annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose with no wasted words. It's perfectly front-loaded and appropriately sized for a simple retrieval tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations and no output schema, the description is incomplete for a tool that likely returns structured data. It doesn't explain what 'whitelisted commands' entails, the return format, or any behavioral context, leaving significant gaps for an agent to use it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's appropriate here, warranting a baseline score above minimum viable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Get') and resource ('list of whitelisted commands'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_pending_commands' or 'get_platform_info' beyond the resource name, which prevents a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'get_pending_commands' or 'add_to_whitelist'. There's no mention of prerequisites, context, or exclusions, leaving usage entirely implicit from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Remove a command from the whitelist
| Name | Required | Description | Default |
|---|---|---|---|
| command | Yes | The command to remove from whitelist |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool removes a command from a whitelist, implying a mutation operation, but doesn't describe side effects (e.g., whether this affects pending commands or security levels), permissions required, or error conditions. This leaves significant gaps in understanding how the tool behaves beyond its basic function.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's mutation nature (removing from a whitelist), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like what happens after removal, error handling, or integration with sibling tools (e.g., 'get_whitelist'), leaving the agent with insufficient context for safe and effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the single parameter 'command' documented as 'The command to remove from whitelist'. The description doesn't add any meaning beyond this, such as format examples or constraints, but the schema provides adequate baseline information, justifying a score of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('remove') and target resource ('a command from the whitelist'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'deny_command' or 'update_security_level', which might have overlapping security functions, but the verb+resource combination is specific enough for basic understanding.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'deny_command' or 'update_security_level', nor does it mention prerequisites (e.g., whether the command must already be in the whitelist). It simply states what the tool does without contextual usage information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Update the security level of a whitelisted command
| Name | Required | Description | Default |
|---|---|---|---|
| command | Yes | The command to update | |
| securityLevel | Yes | New security level for the command |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is an update operation but doesn't clarify whether this requires admin permissions, if changes are reversible, what happens to existing security settings, or potential side effects. For a security-related mutation tool, this lack of transparency is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of a security-level update tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like permissions, side effects, or return values, nor does it help differentiate from sibling tools. The agent would lack sufficient context to use this tool effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, with both parameters clearly documented in the schema. The description doesn't add any meaningful parameter semantics beyond what the schema already provides (e.g., it doesn't explain what 'whitelisted command' means or provide examples). The baseline score of 3 reflects adequate but unenhanced parameter documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Update') and the target resource ('security level of a whitelisted command'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'approve_command' or 'deny_command', which might have overlapping functionality in a security context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'add_to_whitelist' or 'remove_from_whitelist'. It doesn't mention prerequisites (e.g., whether the command must already be whitelisted) or contextual constraints, leaving the agent with insufficient usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
add_to_whitelistapprove_commanddeny_commandexecute_commandget_pending_commandsget_platform_infoget_whitelistremove_from_whitelistupdate_security_levelEach tool has a clearly distinct purpose with no ambiguity. For example, add_to_whitelist and remove_from_whitelist handle whitelist modifications, while approve_command and deny_command manage pending commands, and execute_command performs command execution. The descriptions reinforce these distinct roles, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case, such as add_to_whitelist, get_pending_commands, and update_security_level. This predictability aids agent understanding and navigation without any deviations or mixed conventions.
With 9 tools, the count is well-scoped for a shell security management server. Each tool serves a clear purpose in the workflow, from command execution and approval to whitelist and platform management, avoiding bloat or thin coverage.
The tool set provides complete coverage for shell command security management, including CRUD operations for the whitelist (add, get, remove, update), a full lifecycle for pending commands (get, approve, deny), and core utilities like execute_command and get_platform_info. No obvious gaps exist for the domain.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cfdude/super-shell-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server