Chess MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| createGameA | Initializes a new chess game session. Returns the Game ID and instructions. |
| waitForNextTurnA | Blocks until it is the Agent's turn (or User's turn via Agent proxy). Waits up to 30 seconds for the opponent to move. |
| finishTurnA | Submits a move and returns the updated state or a precise failure. |
| joinGameA | Joins an existing chess game. Returns the current board state and turn information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct role: createGame starts a game, joinGame enters an existing game, waitForNextTurn blocks until the agent's turn, and finishTurn submits a move. There is no meaningful boundary overlap between these operations.
All tool names use the same imperative camelCase style and mostly follow a verb + object pattern: createGame, joinGame, waitForNextTurn, finishTurn. The naming is predictable and consistent across the set.
Four tools is well-scoped for a turn-based chess workflow: create, join, wait, and move. Each tool earns its place and there are no redundant tools.
The core chess lifecycle is covered: start or join a game, wait for a turn, submit a move, and get updated state. Minor optional gaps remain, such as resigning, listing active games, or an explicit get-board/status tool, but agents can work around these using the returned board state.