Lisply MCP

🚀 Model

This document provides solutions to common issues when using the model, including container startup failures, connection errors, and permission problems. It also details the license information for the software.

🚀 Quick Start

If you encounter issues during the use of the model, you can refer to the following solutions.

✨ Features

• Troubleshoot container startup failures, connection errors, and permission issues.
• Provide diagnostic commands for troubleshooting.
• Explain the impact of the license and provide solutions for applications that need to keep the source code closed.

📦 Installation

No installation steps are provided in the original document, so this section is skipped.

💻 Usage Examples

Basic Usage

When using the model, you may encounter the following issues and solutions:

Container Failed to Start

If the Lisply container fails to start:

1. Check if Docker is running:

docker info

2. Check if the ports are occupied:

sudo lsof -i :4201
sudo lsof -i :9081

3. Verify if the Docker image exists:

docker images | grep genworks

4. Try to manually pull the image:

docker pull genworks/gendl:master-ccl

Connection Error

If the LLM Agent / MCP client fails to connect to the configured Lisply backend:

1. Check if the Lisply server is running:

docker ps | grep lisply

2. Enable debug logging:

{
  "mcpServers": {
    "lisply": {
      "command": "wsl", 
      "args": [
        "node",
        "/path/to/cloned/lisply-mcp/scripts/mcp-wrapper.js"
      ]
    }
  }
}

3. Check the wrapper log file:

tail -f /tmp/lisply-mcp-wrapper.log

4. Check the Claude desktop log file on Windows, usually at the following paths:

WSL/Linux:

/mnt/c/Users/<user>/AppData/Roaming/Claude/logs/mcp-server-lisply.log

Windows:

c:\Users\<user>\AppData\Roaming\Claude\logs\mcp-server-lisply.log

5. Try to send a curl request to the Lisply HTTP server:

curl http://localhost:9081/lisply/ping-lisp

6. Try to connect to the Lisply SWANK server (default port 4201):

M-x slime-connect  ;; from emacs

Permission Issues

If you encounter permission errors:

1. Check the Docker socket permissions:

ls -l /var/run/docker.sock

2. Ensure that your user has permission to access Docker:

sudo usermod -aG docker $USER

3. Check the permissions of the mounted directory:

ls -l /path/to/mounted/directory

Note: The files generated by the Lisply backend may belong to different users. This can be fixed by certain docker exec commands. We hope to automate these commands, such as passing the -u parameter to the docker run command in the mcp/filesystem server example in the typical setup section.

Advanced Usage

Use the following commands for troubleshooting:

1. Check the wrapper log:

tail -f /tmp/lisply-mcp-wrapper.log

2. Check the Docker container log:

docker logs $(docker ps --filter "name=lisply-mcp" --format "{{.ID}}")

3. Check the Lisply service status:

curl http://localhost:9081/lisply/ping-lisp

4. Verify the Docker environment:

docker system info

📚 Documentation

The above usage examples provide detailed solutions to common issues. If you have other questions, please refer to the complete license text in the COPYING.txt file in this directory.

🔧 Technical Details

No technical implementation details are provided in the original document, so this section is skipped.

📄 License

This software is released under the GNU Affero General Public License, Version 3.0 (AGPL-3.0), the same license used by Gendl.

License Impact

⚠️ Important Note

Simply using this MCP server to interact with Gendl and obtain output does not trigger the requirements of the AGPL. You can use this wrapper to interact with Gendl without sharing your code.

However, if you modify this wrapper or the licensed backend (e.g., Gendl) and distribute and/or host services based on these modifications, you are required to share the modifications with the recipients under the AGPL. Of course, if you have any questions, please consult legal counsel.

For applications that need to keep the source code closed, Genworks offers a release that is free from AGPL restrictions, subject to a 5% self-reported quarterly revenue royalty. Detailed information and a payment gateway will be available at payments.genworks.com (coming soon).

The full license text can be found in the COPYING.txt file in this directory.