#Lichess API docs MCP server
11 messages · Page 1 of 1 (latest)
I can just tell my agent to review the Lichess API on the Web and it does a great job looking up all the entry points, required arguments and expected results. I do this with copilot, but I expect all the coding agents can look up docs on the web these days, right? I also use it to look up the latest changes in any library dependency and it just works. What would MCP support add?
types info, exact api schema, running it in a sandbox, and less steps to call external tools to scrape the web while it can directly use mcp designed for it
and of course better context saving, I'm writing this for myself the question is if I can make it public given its based on Lichess api docs
under my name
The Lichess API is all in a single webpage and includes types and exact schema, which seem properly digested by my AI. It's a pretty small amount of text.
okay I will not open source thanks
I'm not a Lichess developer. Just a coder on the web. I'd love to use your tool, I'm just curious what the benefits are?