Nasaq UI

What Nasaq UI MCP server does

The Nasaq UI MCP server gives AI clients a query interface for the Nasaq design system. Nasaq contains 392 components, design tokens, 17 brand themes, and full-page templates, with Arabic and right-to-left layout treated as first-class requirements. The repository describes the component ecosystem as covering React, Vue, Blade, and HTML, while the published package also includes web, native, and Electron entry points.

The MCP layer focuses on documentation and design-system reference rather than directly editing an application. An agent can discover available components, search the catalogue, retrieve a component’s manual, inspect foundation guidance, and list tokens. This makes it relevant when an agent needs Nasaq-specific implementation information instead of generic UI advice.

How it works

Nasaq UI MCP server is available at https://mcp.nasaqui.com/mcp using streamable HTTP. The README also documents a local stdio invocation through npx -y @fadymondy/nasaq-mcp. MCP clients can then call the exposed tools and use their results while generating or reviewing interface code.

The documented tools are:

• get_setup for setup information.
• list_components for the component catalogue.
• search_components for finding components.
• get_component for retrieving a component’s documentation.
• get_foundation for foundation guidance.
• list_tokens for token information.

The repository points users to the Nasaq documentation site for client-specific setup guidance. The design system itself can be installed through a shadcn registry or the @fadymondy/nasaq npm package; those installation paths are separate from the MCP interface.

Setup and configuration

For a hosted connection, add the HTTP endpoint to an MCP client. The README shows this Claude command:

claude mcp add --transport http nasaq https://mcp.nasaqui.com/mcp

For a local stdio connection, the documented command is:

claude mcp add nasaq -- npx -y @fadymondy/nasaq-mcp

The provided material does not specify environment variables or other required configuration values. It names Claude and Cursor as supported examples and refers to the documentation site for setup instructions for other clients.

Tools and capabilities

Nasaq UI MCP server supports an agent workflow that starts with component discovery and continues through implementation reference. search_components can narrow the catalogue, while get_component supplies the selected component’s manual. get_setup can provide setup details, get_foundation exposes broader system guidance, and list_tokens makes token definitions available for design decisions.

The underlying Nasaq project uses Base UI and Tailwind CSS v4. It offers a shadcn registry with component JSON endpoints, a token system, themes, and Arabic and RTL support. Those project capabilities provide context for the MCP documentation, but the listed MCP tools are specifically the six discovery and reference operations above.

Limitations and notes

The README states that the stdio package is not on npm until it is released, despite documenting the npx command. Verify package availability before relying on that local route; the hosted endpoint is the explicitly published MCP service.

Component status varies: manuals mark components as stable, beta, or experimental. Stable APIs follow semver, while beta APIs may still receive new props. The repository’s MIT licence covers source code and documentation, but fonts, third-party provider marks, and other listed brand assets have separate licensing or usage considerations.