Use Lispex with an AI Assistant

Connect the Native server

Install Native from Downloads, confirm lispex --version, and add this local stdio server to the assistant.

JSON

{
  "mcpServers": {
    "lispex": {
      "command": "lispex",
      "args": ["mcp", "serve"]
    }
  }
}

The installed Native executable owns lispex mcp serve. After reconnecting, the assistant receives four tools.

Tool	Result
`lispex_reference`	forms, procedures, reader spellings, resource profiles, and runtime routes
`lispex_eval`	Rust tree reference observation for reviewed source
`lispex_diagnostic`	explanation of an exact diagnostic code such as `E302`
`lispex_compare_routes`	agreement or disagreement for one named runtime comparison

First request

Use the Lispex tools. Check that if is admitted, write a rule that returns approve when the input is at least 10 and review otherwise, run it with input 12, and repair any diagnostic before answering.

The assistant can check the form, evaluate the program, and resolve diagnostics against the installed catalog. Lispex requires an else arm on if; #f is the false value; the reader publishes its exact accepted comment forms.

Local data flow

The Lispex server communicates through local stdio. The guest program receives explicit datum input and the language's pure computation surface. The tool result contains the source hash, observations, and diagnostics, and source storage ends with the request. The surrounding assistant application applies its own data policy to text entered into that application.

Compare runtime routes

The built-in comparison is ready with the base server.

JSON

{
  "court": "tree-rust",
  "source": "(+ input 1)",
  "input": "41"
}

It compares the Rust tree reference and Rust VM over one source, input, Core IR, bytecode, and resource request. Add exact Topaz products at server startup for the rust-topaz and all-four comparisons.

JSON

{
  "command": "lispex",
  "args": [
    "mcp", "serve",
    "--topaz-vm", "/absolute/path/to/topaz-vm",
    "--topaz-compiler", "/absolute/path/to/topaz-compiler",
    "--rust-tools", "/absolute/path/to/rust-tools"
  ]
}

rust-topaz compares the two virtual machines. all-four adds the tree run and a product compiled ahead of time for the request. Each comparison retains its selected route set.

Authoring resource profile

Resource	Value
source per request	65,536 bytes
input per request	16,384 bytes
evaluation result	1 MiB
evaluation wall time	5 seconds
comparison result	4 MiB
`all-four` wall time	11 minutes

Timeout, cancellation, malformed input, unavailable product, build, cleanup, and process terminal states are returned explicitly. Use this surface with reviewed authoring source. The Resource-Controlled Evaluator Contract is the application runtime for untrusted rules.

Optional products are selected from absolute startup paths. Comparison output is an authoring observation. The Vouch workflow adds publisher authentication, request binding, current re-execution, and a local gate.

Close the MCP stdio connection when finished. The local process exits and releases request state.

MCP Tool Reference · Learning Path · Lispex Vouch