Minesweeper

An MCP server that lets clients play Minesweeper via Model Context Protocol.

typescript

0

GitHub Stars

typescript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mcp-mirror-tonypan2_minesweeper-mcp-server": {
      "command": "node",
      "args": [
        "C:\\\\path\\\\to\\\\repo\\\\minesweeper-mcp-server\\\\build\\\\index.js"
      ],
      "env": {
        "DEBUG": "*"
      }
    }
  }
}

You can run an MCP server that lets clients play Minesweeper by connecting through the Model Context Protocol. This server acts as a companion to the Minesweeper game server, enabling automated or agent-driven gameplay interactions and easy integration with MCP clients.

How to use

You will run the Minesweeper MCP Server locally and connect an MCP client to it. Start a game by initiating a new Minesweeper session from your client, then use the MCP prompts to place flags, reveal cells, and track mine locations. The server is designed for practical play sessions and supports common MCP client workflows. If you are using Claude Desktop, you can add the tool so it appears alongside your other MCP tools. Restart Claude Desktop after adding the tool so it registers correctly.

How to install

Prerequisites: ensure you have Node.js and npm installed on your machine.

Install dependencies and build the MCP server.

npm install
npm run build

MCP server configuration example

Configure your MCP client to load the Minesweeper MCP Server tool. The following is an example JSON configuration you can adapt to your environment.

{
  "mcpServers": {
    "mcp-server": {
      "command": "node",
      "args": ["C:\\path\\to\\repo\\minesweeper-mcp-server\\build\\index.js"],
      "env": {
        "DEBUG": "*"
      }
    }
  }
}

Notes and usage tips

Common operational steps include starting the Minesweeper MCP server locally using the runtime command shown above, then ensuring the client tool remains registered by restarting the client after configuration changes. The example demonstrates using a stdio-based runtime where you execute the server with Node.js and point to the built index file.