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