Stockfish MCP

io.github.stepbotPublished by GitHub account stepbotvv1.0.2Updated Oct 24, 2026

A Stockfish MCP server to allow an LLM to play chess against Stockfish

VerifiedSTDIODesktop only

Overview

AI-generated overview

A local MCP server that lets an AI assistant play chess against the Stockfish engine.

What you can do
Lets an assistant play chess against Stockfish, the open-source chess engine, through a local MCP connection. The assistant can take part in games against the engine rather than only discussing chess. No tool list is published, so the exact moves, position queries or engine settings available are not documented here.
When to use it
Worth adding when you want an assistant to actually play chess against a strong engine, for practice, testing or demonstration, rather than just talk about positions.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package stockfish-mcp over stdio. A desktop environment is required; it is not offered as a web-executable server. The Stockfish engine itself must be available locally, though the manifest declares no environment variables.
Before you install
The manifest declares no authentication, so anyone who can start the local process can use it. It is desktop-only and not web-executable. No tool list or README is published, so review the package before installing to confirm what it runs and whether it downloads or bundles the engine.

Installation

In SourceWeft

  1. Open Stockfish MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. vv1.0.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.