Overview
Features
Docker-based Lisply backend management
Automates starting and managing a Lisply-compliant Docker container for the Lisp backend.
MCP-Lisply request translation
Translates Lisp evaluation requests between MCP protocol and the backend Lisply API, handling errors and responses.
Dual communication modes: HTTP and STDIO
Supports HTTP mode with structured responses and STDIO mode for raw REPL interactions, including debugger support.
Per-server isolation and tool prefixing
Each MCP server runs independently; tools are prefixed with the server name to avoid conflicts.
SWANK Emacs integration
Includes a Lisply SWANK server bridge for Emacs connections.
Extensible configuration and image management
Offers docker image selection, Lisp implementation choice, mounting host directories, and environment variables for flexible setups.
Tool suite: Lisp evaluation, HTTP requests, and ping
Provides built-in MCP tools such as lisp_eval, http_request, and ping_lisp for interactive exploration.
Who Is This For?
- AI practitioners:Experiment with Lisp-enabled AI workflows; connect Claude Desktop to Lisp backends via MCP Lisply.
- Lisp practitioners:Leverage MCP Lisply to integrate Lisp environments with AI agents and tools.
- Neuro-Symbolic Programming researchers:Explore neuro-symbolic workflows by enabling AI agents to reason in Lisp.
- Engineers and CAD designers:Apply Lisp-based backends to automate CAD tasks with AI guidance.
- Tinkerers and hobbyists:Tinkerers and hobbyists exploring how Lisp backends can be controlled by AI agents.
- Claude Desktop users:Configure and test Lisply-MCP with Claude Desktop to drive Lisp environments.




