edict_explain
Explains AST nodes, errors, or compiler behavior
How to use it
Project documentation lists edict_explain for the Edict MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install Edict
npx edict-lang # start MCP server (stdio transport, no install needed)Other tools in Edict (21)
Full pipeline: validate → resolve names → type check → effect check → verify contracts
Compiles a checked AST to WASM (returns base64-encoded binary)
Combines composable program fragments into a module
Execution tracing and crash diagnostics
Compiles and deploys an Edict program to edge runtimes (Cloudflare Workers)
Returns machine-readable catalog of all error types
Returns 41 example programs as JSON ASTs (includes schema snippet)
Packages a program as a UASF portable skill
Generates tests from Z3-verified contracts
Imports and executes a UASF skill package
Invokes a deployed Edict WASM service via HTTP
Invokes a UASF skill package directly
Runs non-blocking quality analysis and returns warnings
Packages a compiled program as a deployable skill bundle
Applies targeted AST patches by nodeId and re-checks
Records and replays deterministic execution traces
Executes a compiled WASM binary, returns output and exit code
Returns the full AST JSON Schema — the spec for how to write programs
Returns diagnostics and environment info for troubleshooting
Validates AST structure (field names, types, node kinds)
Returns compiler version and capability info