Back to Browse

Aegov Dls MCP Server

Developer ToolsLow Risk9.7MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

9.7
Low Risk9.7Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

9 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-dlsforge-aegov-mcp": {
      "args": [
        "-y",
        "@dlsforge/aegov-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

DLSForge — UAE Design System (AEGOV DLS) tooling

Community project. Not affiliated with or endorsed by TDRA.

smithery badge

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.

Reviews

No reviews yet

Be the first to review this server!