mcp -dunnet

This MCP server provides a Rust-based wrapper around the classic M-x dunnet game. The server runs the Dunnet game and exposes an interface that lets you send commands and receive responses, enabling you to automate and experiment with the game play. The wrapper handles the interaction loop, feeding commands to the game and returning the resulting text and any prompts. You can use the MCP protocol to issue inputs such as LOOK, GO, TAKE, USE, or custom actions, and you’ll receive the game's descriptive text and any state updates in return. The goal is to let you control the game remotely and creatively, without needing to manually interact with the Dunnet interpreter. When using this server, you’ll typically provide a sequence of in-game commands over MCP and process the textual responses to guide subsequent actions.

To get started, connect to the Dunnet MCP server with your MCP client, issue a sequence of commands to explore the world, and read the responses to determine the next steps. The server is designed to handle a stream of inputs and return corresponding outputs, so you can script longer adventures or integrate the game into larger automation workflows. If you’re building complex scenarios, you can batch commands and parse the resulting narration to extract items, locations, and game state to drive future actions.

Prerequisites:\n- Docker (recommended) or an alternative container runtime.\n- Optional: If you prefer not to use Docker, you can try to run a prebuilt binary if available or build from source according to the project’s guidelines.\n\nUsing Docker (recommended):\n1. Install Docker on your system.\n2. Pull and run the Dunnet MCP server image:\n docker pull lambdageek/mcp-server-dunnet\n docker run -i lambdageek/mcp-server-dunnet\n3. Connect your MCP client to the server endpoint provided by the running container.\n\nIf you prefer to build locally (Rust):\n1. Ensure Rust is installed (https://www.rust-lang.org/tools/install).\n2. Clone the repository containing the Dunnet MCP server.\n3. Build the project:\n cargo build --release\n4. Run the binary directly (adjust path as needed):\n ./target/release/mcp-dunnet-server\n5. Connect your MCP client to the local server.\n\nNote: The exact build/run commands may vary depending on how the project exposes the binary. Refer to the repository’s README for any project-specific steps.

Environment variables and configuration options (if supported by this build):\n- DUNNET_VERBOSE: Set to true to enable verbose logging of game prompts and responses.\n- DUNNET_TURNS: Limit the number of turns per session; useful for structured explorations.\n- MCP_LOG_LEVEL: Control MCP client/server log verbosity (e.g., info, debug).\n- Any standard Docker environment variables (e.g., -e VAR=value) can be used when running via Docker.\nCommon issues: ensure the container image has access to any required resources for the Dunnet game, and verify that the MCP client is correctly connected to the server endpoint. If commands appear to hang, check for prompts or initialization messages from the Dunnet interpreter and adjust your input timing accordingly.\nDocumentation and compatibility: This variant is a Rust wrapper; if you encounter build or runtime issues, confirm you’re using the intended image or binary and that the MCP protocol version matches the server’s implementation.