MCP DOS - Classic DOS Gaming 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 |
|---|---|
| close-appA | Close an existing running mcp-dos server. You can use this tool if you are getting erros when starting a new server. |
| List DOS GamesB | List all available DOS games |
| open-dosA | Open and play a DOS game using js-dos. Use |
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 3 tools
Each tool has a clearly distinct purpose: close-app manages server lifecycle, List DOS Games provides a catalog, and open-dos launches a specific game. There is no overlap in functionality, and the descriptions clearly differentiate their roles.
The naming is inconsistent with mixed conventions: close-app uses kebab-case, List DOS Games uses title case with spaces, and open-dos uses kebab-case. There is no uniform verb_noun pattern, and the styles vary significantly across tools.
With only 3 tools, the count is borderline for a gaming server scope. It covers core operations (list, open, close), but feels thin compared to typical gaming servers that might include more features like save/load, settings, or game management. However, it is functional for basic play.
The tool set covers the essential lifecycle: list games, open a game, and close the server. Minor gaps exist, such as no tools for saving game progress, adjusting settings, or managing multiple sessions, but agents can perform basic gaming workflows without dead ends.