Super Shell MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_platform_infoB | Get information about the current platform and shell |
| execute_commandC | Execute a shell command on the current platform |
| get_whitelistB | Get the list of whitelisted commands |
| add_to_whitelistC | Add a command to the whitelist |
| update_security_levelC | Update the security level of a whitelisted command |
| remove_from_whitelistC | Remove a command from the whitelist |
| get_pending_commandsB | Get the list of commands pending approval |
| approve_commandC | Approve a pending command |
| deny_commandC | Deny a pending command |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each 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.