English Français العربية

io.github.dlsforge/aegov-mcp

Official registry Media and design

UAE Design System (AEGOV DLS) for AI assistants: components, tokens, validation. Not TDRA-official.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @dlsforge/aegov-mcp
Claude Code 
claude mcp add aegov-mcp -- npx -y @dlsforge/aegov-mcp@0.2.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "aegov-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@dlsforge/aegov-mcp@0.2.2"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. DLSForge — UAE Design System (AEGOV DLS) tooling
  2. The generate → verify loop
  3. Working in this repo
  4. License

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:

PackageWhat it isStatus
@dlsforge/aegov-rules-coreMachine-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-mcpMCP 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.

Frequently asked questions

What is io.github.dlsforge/aegov-mcp?

UAE Design System (AEGOV DLS) for AI assistants: components, tokens, validation. Not TDRA-official.

How do I install io.github.dlsforge/aegov-mcp?

It runs on your machine. In Claude Code: claude mcp add aegov-mcp -- npx -y @dlsforge/aegov-mcp@0.2.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.dlsforge/aegov-mcp need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.dlsforge/aegov-mcp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.dlsforge/aegov-mcp?

It is published by dlsforge. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.