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

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

This project is a Model Context Protocol (MCP) middleware that enables Large Language Models (LLMs) to interact with Lisp-based development and runtime environments using a lightweight protocol called Lisply. It is intended for AI practitioners curious about Lisp, Lisp practitioners curious about AI, engineers interested in CAD automation and knowledge-based engineering, and general tinkerers.

How to use Model Context Protocol (MCP) Middleware for Lisp-based and Lisp-like Environments?

Install Node.js (18+), Docker (20+), clone the repository, then configure your MCP-capable AI agent (e.g., Claude Desktop) with a JSON configuration file pointing to the scripts/mcp-wrapper.js entry point. After restarting the agent, test by asking the LLM to evaluate a Lisp expression like (+ 1 2 3) using the gendl__lisp_eval tool.

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

• Connects MCP-capable AI agents to Lisp REPLs via the Lisply protocol.
• Allows LLMs to generate, evaluate, compile, and load Lisp code.
• Supports multiple Lisp environments simultaneously with separate server names.
• Manages Docker containers automatically for backend Lisply systems.
• Provides HTTP request, introspection, and file manipulation capabilities.
• Includes error handling, debugger interaction, and logging.

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

• AI-assisted symbolic programming (neuro-symbolic programming).
• CAD automation and knowledge-based engineering using Lisp.
• Experimenting with Common Lisp or Emacs Lisp from an AI agent.
• Managing, testing, and analyzing Lisp projects via LLM-driven evaluation.

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

What is the Lisply protocol?

Lisply is a lightweight protocol that specifies a minimal set of HTTP and standard input/output interfaces, environment variables, Docker container naming conventions, and optional capabilities for AI agents to control a running Lisp system.

What Lisp backends are supported?

The default backend is a Gendl (Common Lisp) Docker container. An Emacs Lisp backend is also available via the Skewed Emacs project.

Does it require Docker?

Yes, the default minimal configuration uses Docker (20+ recommended) to run a preconfigured containerized Lisply backend. The middleware manages container startup and connections.

Can I use multiple Lisp environments at once?

Yes, each server operates independently with its own HTTP port and server name. MCP tools are automatically prefixed with the server name to avoid conflicts.

What security considerations are there?

Allow the wrapper to connect only to containerized backends. Avoid mounting non-expendable host directories to the container. Consider limiting container RAM and CPU usage via Docker resource constraints.