MCP ExplorerExplorer

Mcp Stockfish

@soniricoon 16 days ago
1 MIT
FreeCommunity
AI Systems
#ai#chess#go#golang#mcp#mcp-server#model-context-protocol#model-context-protocol-server#stockfish#mcp-server-golang
🐟 MCP server connecting AI systems to Stockfish chess engine

Overview

What is Mcp Stockfish

mcp-stockfish is a Model Context Protocol server that connects AI systems to the Stockfish chess engine, allowing for seamless communication and analysis of chess positions.

Use cases

Use cases include integrating Stockfish into AI-driven chess applications, developing chess training tools, and creating interactive chess analysis platforms.

How to use

To use mcp-stockfish, set up the server and connect your AI system to it via the MCP protocol. You can send commands to analyze chess positions and receive calculated moves from Stockfish.

Key features

Key features include support for concurrent sessions, full UCI command support, robust error handling, JSON output for easy integration, and Docker readiness for containerized deployment.

Where to use

mcp-stockfish can be used in various fields such as AI development, chess analysis, game development, and educational tools for teaching chess strategies.

Content

mcp-stockfish 🐟

A Model Context Protocol server that lets your AI talk to Stockfish. Because apparently we needed to make chess engines even more accessible to our silicon overlords.

Claude Desktop with mcp-stockfish

🧠⚡🖥️ Your LLM thinks, Stockfish calculates, you pretend you understand the resulting 15-move tactical sequence.

What is this?

This creates a bridge between AI systems and the Stockfish chess engine via the MCP protocol. It handles multiple concurrent sessions because your AI probably wants to analyze seventeen positions simultaneously while you’re still figuring out why your knight is hanging.

Built on mark3labs/mcp-go. Because reinventing wheels is for people with too much time.

Features

  • 🔄 Concurrent Sessions: Run multiple Stockfish instances without your CPU crying
  • ⚡ Full UCI Support: All the commands you need, none of the ones you don’t
  • 🎯 Actually Works: Unlike your last side project, this one has proper error handling
  • 📊 JSON Everything: Because apparently we can’t just use plain text anymore
  • 🐳 Docker Ready: Containerized for when you inevitably break your local setup

Supported UCI Commands ♟️

Command Description
uci Initializes the engine in UCI mode
isready Checks if the engine is ready. Returns readyok
position startpos Sets up the board to the starting position
position fen [FEN] Sets up a position using FEN notation
go Starts the engine to compute the best move
go depth [n] Searches n plies deep. Example: go depth 10
go movetime [ms] Thinks for a fixed amount of time in milliseconds. Example: go movetime 1000
stop Stops current search
quit Closes the session

Quick Start

Installation

git clone https://github.com/sonirico/mcp-stockfish
cd mcp-stockfish
make install

Usage

# Default mode (stdio, because we're old school)
mcp-stockfish

# With custom Stockfish path (for the special snowflakes)
MCP_STOCKFISH_PATH=/your/special/stockfish mcp-stockfish

# HTTP mode (for the web-scale crowd)
MCP_STOCKFISH_SERVER_MODE=http mcp-stockfish

Configuration ⚙️

Environment Variables

Server Configuration

  • MCP_STOCKFISH_SERVER_MODE: “stdio” or “http” (default: “stdio”)
  • MCP_STOCKFISH_HTTP_HOST: HTTP host (default: “localhost”)
  • MCP_STOCKFISH_HTTP_PORT: HTTP port (default: 8080)

Stockfish 🐟 Configuration

  • MCP_STOCKFISH_PATH: Path to Stockfish binary (default: “stockfish”)
  • MCP_STOCKFISH_MAX_SESSIONS: Max concurrent sessions (default: 10)
  • MCP_STOCKFISH_SESSION_TIMEOUT: Session timeout (default: “30m”)
  • MCP_STOCKFISH_COMMAND_TIMEOUT: Command timeout (default: “30s”)

Logging

  • MCP_STOCKFISH_LOG_LEVEL: debug, info, warn, error, fatal
  • MCP_STOCKFISH_LOG_FORMAT: json, console
  • MCP_STOCKFISH_LOG_OUTPUT: stdout, stderr

Tool Parameters

  • command: UCI command to execute
  • session_id: Session ID (optional, we’ll make one up if you don’t)

Response Format

{
  "status": "success|error",
  "session_id": "some-uuid",
  "command": "what you asked for",
  "response": [
    "what stockfish said"
  ],
  "error": "what went wrong (if anything)"
}

Session Management

Sessions do what you’d expect:

  • Spawn Stockfish processes on demand
  • Keep UCI state between commands
  • Clean up when you’re done (or when they timeout)
  • Enforce limits so you don’t fork-bomb yourself

Integration

Claude Desktop

{
  "mcpServers": {
    "chess": {
      "command": "mcp-stockfish",
      "env": {
        "MCP_STOCKFISH_LOG_LEVEL": "info"
      }
    }
  }
}

Development

make deps     # Get dependencies
make build    # Build the thing
make test     # Run tests (when they exist)
make fmt      # Make it pretty

Credits 🐟

Powered by Stockfish, the chess engine that’s stronger than both of us combined. Created by people who actually understand chess, unlike this wrapper.

Thanks to:

License

MIT - Do whatever you want, just don’t blame me when it breaks.

Tools

No tools

Comments