UAE Design System (AEGOV DLS) for AI assistants: components, tokens, validation. Not TDRA-official.
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.
@dlsforge/aegov-rules-core ← the standard, defined once (catalogue + rule engine)
│
├── @dlsforge/aegov-mcp → assistants GENERATE valid government UI
└── @dlsforge/aegov-audit → Mizan VERIFIES a finished/in-progress site
npm install # once, at the root — links the workspaces
npm run build # builds rules-core → mcp → audit (order matters)
npm test # all suites, every package
npm run evals # the 10 government-screen evals (mcp)
npm run evals:audit # Mizan's fixture-site evals (audit)
npm run smoke # stdio smoke test (mcp)
npm run validate # catalogue lint + invariants (rules-core)
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.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @dlsforge/aegov-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-dlsforge-aegov-mcp": {
"command": "npx",
"args": [
"-y",
"@dlsforge/aegov-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@dlsforge/aegov-mcpnpmio.github.dlsforge/aegov-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.