e to be evaluated against a running Lisp-based backend, there are certain risks in case the LLM were to go "haywire." Therefore, best practices are: - Allow the wrapper to connect only to a containerized version of a Lisply backend. If overriding default host/port, the wrapper will happily connect to any live Lisply-compliant http port. Avoid allowing this to happen for any http ports being served by programs running directly on your host. - Make sure not to mount any non-expendable directories to that container (see directory mounting configuration instructions below) - Consider taking steps to [limit RAM and CPU usage](https://docs.docker.com/engine/containers/resource_constraints/) of the container. ### Code Modules/Files - **lib/config.js**: Configuration loading and environment handling - **lib/logger.js**: Logging functionality - **lib/docker.js**: Docker container management - **lib/server.js**: HTTP server and MCP wrapper implementation - **lib/utils.js**: Utility functions for response handling - **handlers/**: Tool-specific request handlers - **initialize.js**: Initialization handler - **toolsList.js**: Tools list handler - **toolCall.js**: Main tool call dispatcher - **httpRequest.js**: HTTP request handler - **ping.js**: Ping handler - **lispEval.js**: Lisp evaluation handler - **mcp-wrapper.js**: <--- Main entry point <--- ## Detailed Installation 1. Clone this repository: ```bash git clone https://github.com/gornskew/lisply-mcp.git ``` 2. Install the required dependencies (optional, as the wrapper auto-installs dependencies): ```bash cd lisply-mcp/scripts npm install # optional - the script will attempt to do this also if needed chmod +x mcp-wrapper.js # needed on some systems ``` 3. Ensure Docker is installed on your system. 4. Test the script: ```bash node mcp-wrapper.js --help ``` ## Advanced Configuration Optional settings for advanced users, with defaults suitable for most cases: ### Command-Line Arguments ```bash Options: -H, --backend-host Lisply server host (default: 127.0.0.1) --swank-host-port SWANK port on host system (external) (default: 4201) --http-host-port HTTP port on host system (external) (default: 9081) --https-host-port HTTPS port on host system (external) (default: 9444) --telnet-host-port TELNET port on host system (external) (default: 4024) --http-port HTTP port inside container (internal) (default: 9080) --https-port HTTPS port inside container (internal) (default: 9443) --swank-port SWANK port inside container (internal) (default: 4200) --telnet-port TELNET port inside container (internal) (default: 4023) --image-base-name Base name for Docker image (default: dcooper8/gendl) --image-branch Branch to use for Docker image (default: auto-detected) --docker-image Full Docker image for backend (overrides base name and branch) --lisp-impl Lisp implementation to use, ccl or sbcl (default: ccl) --no-auto-start Do not auto-start backend Docker container if not running --docker-socket Path to Docker socket (default: /var/run/docker.sock) --log-file Path to log file (default: /tmp/lisply-mcp-wrapper.log) --debug Enable debug logging --mount Mount volumes in format "src:dst" (can specify multiple times) --start-http Start HTTP service in backend container (default: true) --start-https Start HTTPS service in backend container (default: false) --start-swank Start SWANK service in backend container (default: true) --start-telnet Start TELNET service in backend container (default: false) --no-use-stdio

Model Context Protocol (MCP) Middleware for Lisp-based and Lisp-like Environments

Tools