The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Aegov MCP listing page.
Community project. Not affiliated with or endorsed by TDRA.
The MCP server is listed on the official MCP Registry (io.github.dlsforge/aegov-mcp), Glama, and Smithery.
npm-workspaces monorepo holding the public, MIT-licensed DLSForge packages:
| Package | What it is | Status |
|---|---|---|
@dlsforge/aegov-rules-core | Machine-readable model of the AEGOV DLS: component schemas, resolved design tokens, catalogue loader, and the DLS rule engine shared by every DLSForge tool. | published: 0.2.1 on npm |
@dlsforge/aegov-mcp | MCP server exposing the core to AI coding assistants — listComponents, getComponent, getTokens, scaffoldUaePass, scaffoldEmiratesId, validate_snippet. | published: 0.2.2 on npm |
@dlsforge/aegov-audit (Mizan) | Compliance & accessibility auditor for UAE government sites (axe-core + Lighthouse + DLS rules over the rendered DOM), consuming the same core. Ships a CLI and a reusable GitHub Action. | published: 0.2.2 on npm |
The two tools mirror each other: the MCP server generates on-standard government UI, Mizan audits it — both enforcing the same rules from the shared core, so the standard is defined once.
Mizan's suites render pages, so npx playwright install chromium is needed once for npm test / npm run evals:audit.
See each package's own README for usage.
MIT — see LICENSE.