Hi, this ["Lisply MCP"](<a href="https://github.com/gornskew/lisply-mcp">https://github.com/gornskew/lisply-mcp</a>) project started out as a "quick hack" to get Claude Desktop driving my [Common Lisp based backend](<a href="https://gitlab.common-lisp.net/gendl/gendl" rel="nofollow">https://gitlab.common-lisp.net/gendl/gendl</a>), and ended up as a generic Node.js wrapper meant to work with pretty much [any language backend which can support "eval" and http](<a href="https://github.com/gornskew/lisply-mcp/blob/master/BACKEND-REQS.md">https://github.com/gornskew/lisply-mcp/blob/master/BACKEND-R...</a>) . By default, it comes configured to work with an existing reference-implementation backend [CL-based container image](<a href="https://gitlab.common-lisp.net/gendl/gendl/-/tree/master/gwl/lisply-backend" rel="nofollow">https://gitlab.common-lisp.net/gendl/gendl/-/tree/master/gwl...</a>) which it will pull and run on-demand. An [Emacs Lisp backend](<a href="https://github.com/gornskew/skewed-emacs/blob/master/dot-files/emacs.d/sideloaded/lisply-backend/README.md">https://github.com/gornskew/skewed-emacs/blob/master/dot-fil...</a>) is in progress.