MDMA

Fenced mdma blocks with typed fields Authors write short YAML inside Markdown fences declaring components, fields, validation rules, and sensitive flags, keeping the format readable by people and small models.[1][2]

Ten schema-defined component types Form, button, task list, table, callout, approval gate, webhook, chart, thinking trace, and custom cover collection, sign-off, notification, and display tasks without per-use-case syntax.[1]

Deterministic validator with auto-fix Seventeen static lint rules plus an LLM fixer catch malformed blocks before render, and blocks render progressively with skeletons while streaming rather than failing on partial output.[1]

Headless runtime with audit log State, data bindings, policy checks, and an audit trail live outside the view layer, so approvals and submissions leave a trace the host can inspect.[1]

Three renderers from one document React, Vue 3, and React Native packages share the spec and theme token shape, so one MDMA document ships as web interface and native iOS and Android interface.[1]

AG-UI bridge with run interrupts Documents stream over the AG-UI protocol and user actions route back into the agent run, letting a run pause on an approval gate and resume from the answer.[1]

Model-agnostic prompt pack and MCP server Thirty-six tuned author prompts span five vendors plus a house fine-tune, and an MCP server hands the spec, prompts, and docs directly to a coding agent.[1]

Disclosed cross-format benchmark A published harness scored MDMA at 94.4 percent rendered on both a flagship model and an open-weights model with zero tier drop, against OpenUI Lang, json-render, and A2UI, with raw generations committed for re-scoring.[1]

Agent teams that need in-chat decisions: approval gates, forms, and checklists mounted where the conversation happens remove the detour to an external tool.[1]

Multi-platform product developers: one MDMA document feeding React, Vue, and React Native renderers suits teams shipping the same agent experience on web and mobile.[1]

Builders standardizing on agent protocols: the AG-UI bridge and MCP server give teams committed to those protocols a documented path for streaming interface and serving specs to models.[1]

Non-technical form publishers should look elsewhere: publishing a branded survey with no code remains HeyForm territory, since MDMA requires developers to install packages and host renderers.[1][2]

Teams that cannot operate LLM variance should be cautious: the validator and fixer narrow malformed output, but the interface still depends on a model emitting valid blocks within its context limits.[1]

Buyers needing compliance paperwork are blocked on public material: no SSO, data-location, or enterprise-support posture was documented on the observed official pages.[1]