dos-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOS_MCP_ROOT | No | Starting directory for the child shell (optional) | |
| DOS_MCP_SHELL | No | Shell to use (e.g., /bin/bash) (optional) | |
| DOS_MCP_TARGET | No | UDP target address in ip:port format (optional) | |
| DOS_MCP_PASSWORD | No | Password or 128-bit hex key for authenticated UDP (optional) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dos.list_targetsA | List configured and locally discovered DOS systems and selectors. |
| dos.get_statusA | Report target identity, connection state, and current operating phase. |
| dos.get_capabilitiesA | Report exactly which target operations and screen formats are supported. |
| dos.capture_screenA | Capture the full fixed-width text screen, cell attributes, and cursor state. |
| dos.capture_graphicsB | Capture a standard CGA, Hercules, EGA, or VGA graphics framebuffer. |
| dos.send_keysB | Inject text and named keys into the target's input queue. |
| dos.download_fileA | Download one bounded binary file as base64 when file reads are enabled. |
| dos.upload_fileA | Upload one bounded binary file when writes are enabled at both peers. |
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 8 tools
Each tool targets a distinct operation: capabilities, file transfer, target discovery, status, screen capture (text vs graphics), and key injection. No overlapping purposes; the distinction between capture_screen and capture_graphics is clear.
All tool names follow a consistent verb_noun snake_case pattern (get_capabilities, upload_file, list_targets, get_status, capture_screen, capture_graphics, send_keys, download_file). No mixed styles or irregular verbs.
Eight tools is well-scoped for a DOS remote-control server, covering file transfer, input, output, discovery, and status without excess. Each tool earns its place in the set.
The tool surface covers core remote interaction: file up/download, screen capture, input, target discovery, and status. The only minor gap is a lack of explicit command execution beyond send_keys, but send_keys can handle that indirectly.