Lichess MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Required to use the Lichess tools; without it, tool calls return "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Lichess through Cotlet.dev. Call lichess_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lichess_guideA | How to work in Lichess (accept team join requests and message your team): its screens and the sign-in link. Call this first. |
| lichess_statusB | Check that your Cotlet.dev account and Lichess are ready: account, credits and Lichess connection. |
| lichess_openB | Open a Lichess page in your signed-in Cloud Browser (default https://lichess.org) to work with accept team join requests and message your team. |
| lichess_readB | Read the current Lichess page: its text and numbered buttons, links and fields. |
| lichess_clickB | Click a numbered element on the current Lichess page. |
| lichess_typeB | Type text into a numbered field on the current Lichess page. |
| lichess_closeA | Close the Lichess browser session when the work is done, so credits stop running. |
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 7 tools
Each tool maps to a distinct step in a browser automation loop: guide/status for setup, open for navigation, read for page inspection, click/type for interaction, and close for teardown. There is no meaningful overlap between any pair, so an agent can select the right tool unambiguously.
All tools share a consistent lichess_ prefix and snake_case style, which is predictable and readable. Two tools (guide, status) are nouns rather than verbs while the rest are action verbs, a minor deviation from a strict verb_noun pattern.
Seven tools is a tight, well-scoped set that covers the full browser automation lifecycle for the stated Lichess workflow without filler. Each tool clearly earns its place.
The core loop (open, read, click, type, close) plus setup (guide/status) fully covers the 'accept team join requests and message team' purpose. Minor gaps exist—no explicit scroll, back/navigate, or wait/screenshot—but the read+click+type combination lets agents work around most of these.