Thin Model Context Protocol middleware connecting AI agents to Lisply-compliant backends — the Gendl engines, the Readymacs Emacs, or any Lisp system implementing the small Lisply HTTP contract. The agent evaluates symbolic expressions in the running image: one tool, the whole language, instead of a hand-written schema per operation.
The wrapper is a pure HTTP client in Node.js: it never pulls, starts, or manages containers (Basalt owns lifecycle), and its defaults — the `lisply-mcp` server name, the `LISPLY_*` environment prefix, the endpoint names — are stable, versioned contracts.
Backends are exposed as TRUSTED SANDBOXES: the wrapper does not restrict Lisp operators, filesystem access, or subprocesses. Isolation is the operator's job, at the container boundary — which a Basalt deployment provides by construction.