Edict MCP Server

Edict MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. AI-agent programming language. JSON AST in, WASM out. Typed, effect-tracked, Z3-verified.

What you get

Edict is a statically-typed, effect-tracked programming language where the canonical program format is a JSON AST. It's purpose-built so AI agents can write, verify, and execute programs through a structured pipeline — no text parsing, no human-readable syntax, no ambiguity.

• JSON AST — — Programs are JSON objects, not text files. No lexer, no parser
• Structured errors — — Every error is a typed JSON object with enough context for an agent to self-repair
• Type system — — Int, Float, String, Bool, Array, Option, Result<T,E>, records, enums, refinement types
• Effect tracking — — Functions declare pure, reads, writes, io, fails. The compiler verifies consistency
• Contract verification — — Pre/post conditions verified at compile time by Z3 (via SMT). Failing contracts return concrete counterexamples
• WASM compilation — — Verified programs compile to WebAssembly via a pure-JS encoder and run in Node.js

Setting it up

The server ships on npm as edict-lang, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Edict is connected, these are the calls the assistant has available:

• edict_schema — Returns the full AST JSON Schema — the spec for how to write programs
• edict_version — Returns compiler version and capability info
• edict_examples — Returns 41 example programs as JSON ASTs (includes schema snippet)
• edict_validate — Validates AST structure (field names, types, node kinds)
• edict_check — Full pipeline: validate → resolve names → type check → effect check → verify contracts
• edict_compile — Compiles a checked AST to WASM (returns base64-encoded binary)
• edict_run — Executes a compiled WASM binary, returns output and exit code
• edict_patch — Applies targeted AST patches by nodeId and re-checks
• edict_errors — Returns machine-readable catalog of all error types
• edict_lint — Runs non-blocking quality analysis and returns warnings
• edict_debug — Execution tracing and crash diagnostics
• edict_compose — Combines composable program fragments into a module

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Edict.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the edict mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Edict's toolset — edict_schema, edict_version, edict_examples and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Sowiedu; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.