mcpField
A
aegov-mcp

aegov-mcp

Local
github.comDeveloper Tools0Updated today
RepositoryVisit website

About aegov-mcp

aegov-mcp is a community MCP server that gives AI coding assistants access to UAE AEGOV Design System components, tokens, scaffolding, and snippet validation. It shares a rules core with the Mizan auditor; the project states it is not affiliated with or endorsed by TDRA.

Key features

  1. 01List and retrieve components
  2. 02Access design tokens
  3. 03Scaffold UAE Pass interfaces
  4. 04Scaffold Emirates ID interfaces
  5. 05Validate code snippets

Use cases

  1. 01Build interfaces following AEGOV DLS
  2. 02Look up components and design tokens
  3. 03Validate snippets against design rules

MCP support

The MCP server exposes the AEGOV rules core through tools for listing and retrieving components, reading tokens, scaffolding UAE Pass and Emirates ID, and validating snippets.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "dlsforge-aegov": {
      "command": "npx",
      "args": [
        "-y",
        "@dlsforge/aegov-mcp"
      ]
    }
  }
}
Run commandnpx -y @dlsforge/aegov-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@dlsforge/aegov-mcp0.2.2

Tools

7

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
messagestringNoOptional message to echo back

Details

From the project 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.