Runs on your machine from its package; the steps are below.
What it does
- Reads
- Writes
- High impact
At most: only reads or looks up information.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @dlsforge/aegov-mcp
MCP client config
{
"mcpServers": {
"aegov": {
"command": "npx",
"args": [
"-y",
"@dlsforge/aegov-mcp"
]
}
}
}DLSForge — UAE Design System (AEGOV DLS) tooling
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.
The generate → verify loop
@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
Working in this repo
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.
License
MIT — see LICENSE.
