Aegov Mcp

io.github.dlsforgePublished by GitHub account dlsforgev0.2.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Lets an AI assistant look up UAE government design system components and tokens, scaffold UAE Pass and Emirates ID UI, and validate snippets.

What you can do
Exposes the AEGOV DLS core to coding assistants through tools such as listComponents, getComponent, getTokens, scaffoldUaePass, scaffoldEmiratesId and validate_snippet. It provides component schemas, resolved design tokens and a rule engine so generated government UI follows the same standard the companion auditor checks. It is a community project, not TDRA-official.
When to use it
Use it when building or reviewing UAE government-facing interfaces and you want an assistant to generate on-standard components, tokens and UAE Pass or Emirates ID scaffolding, and to check snippets against the DLS rules.
Requirements
Runs locally as a stdio process, installed from the npm package @dlsforge/aegov-mcp; Node.js and npm are needed. No authentication, environment variables or headers are declared. Desktop only.
Before you install
The README states the project is community-run and not affiliated with or endorsed by TDRA, so generated output should not be treated as official compliance. The validate_snippet tool checks snippets against the bundled rules; review generated UI before shipping.

Installation

In SourceWeft

  1. Open Aegov Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.3.0 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

bash
npm install          # once, at the root — links the workspacesnpm run build        # builds rules-core → mcp → audit (order matters)npm test             # all suites, every packagenpm 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.

Source: README.md at commit 4f51f7e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts