Back to Directory/Developer Tools

io.github.dlsforge/aegov-mcp

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

Developer ToolsHTMLv0.2.2

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.

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y @dlsforge/aegov-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

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

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@dlsforge/aegov-mcpnpm

Compatible MCP Clients

io.github.dlsforge/aegov-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More