Skip to main content
Glama
Sign In

Lichess MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Import PGN to study in Lichess

lichess_import_pgn_to_study
Read-onlyIdempotent

Import PGN to study in the user's own Lichess account from ChatGPT, Claude or any AI agent. Returns how to do it in Lichess step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Lichess Cloud Browser. Lichess's official API: Lichess has a full, free REST API with personal and OAuth tokens, but no official MCP server (checked 17 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lichess_import_pgn_to_study"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With readOnlyHint=true already declared, the description adds real context beyond annotations: 'opens nothing by itself' confirms no navigation occurs, and it discloses the return content (step-by-step screens, buttons, fields). It does not mention failure/edge cases such as missing browser session or missing PGN.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operational sentence is front-loaded and useful, but the trailing paragraph about Lichess's official REST API, OAuth tokens, and 'checked 17 Oct 2026' adds no call-time value and dilutes the message.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only instruction tool with no output schema, the description covers what it returns and how it chains into browser tools, which is what an agent needs. Missing only edge-case behavior and prerequisites for the Lichess Cloud Browser session.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero parameters, so the baseline is 4 and the description need not explain inputs. One slight oddity: it claims to handle a PGN but exposes no parameter for PGN content, and the description does not explain where the PGN is expected to come from.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: it returns step-by-step UI instructions for importing a PGN into a study rather than performing the import. It distinguishes itself from the cotlet_browser_* tools by naming them as the actual execution path. Minor deduction because the tool name promises an 'import' that the tool explicitly does not do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage chain: call this first to get the screens/buttons/fields, then execute with cotlet_browser_* inside the user's Lichess Cloud Browser. It does not state prerequisites (e.g., the user must be logged in, or a PGN must be on hand) or when NOT to use it, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Lichess MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources