chess-uci-mcp

Created By
AnglerfishChessa year ago
MCP server to connect to the chess engines using UCI protocol
Overview

what is chess-uci-mcp?

chess-uci-mcp is an MCP bridge that provides an interface to UCI chess engines, allowing users to connect and interact with chess engines like Stockfish.

how to use chess-uci-mcp?

To use chess-uci-mcp, you need to have a UCI-compatible chess engine installed, such as Stockfish. Configure your MCP setup with the path to the engine and the necessary commands to run the bridge.

key features of chess-uci-mcp?

  • Connects to UCI chess engines like Stockfish.
  • Provides commands to analyze positions, get best moves, and set positions.
  • Supports multiple operating systems with specific configuration paths.

use cases of chess-uci-mcp?

  1. Analyzing chess positions using FEN strings.
  2. Finding the best move in a given chess position.
  3. Integrating chess engine capabilities into applications or tools.

FAQ from chess-uci-mcp?

  • What is required to run chess-uci-mcp?

You need Python 3.10 or newer and a UCI-compatible chess engine like Stockfish.

  • How do I configure the MCP server?

You need to edit the configuration file for your MCP setup to include the path to the chess engine and the commands to run.

  • Is chess-uci-mcp free to use?

Yes! chess-uci-mcp is open-source and available under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AnglerfishChess
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

3 hours ago
Gpt Scrambler

2 days ago