Design

nasaqui.com

Provides tools to browse, search, and retrieve details for Nasaq web components, design foundations, and CSS design tokens.

1 endpoint6 known toolsFirst detected October 6, 2026Last detected October 11, 2026

ENDPOINT 1

https://mcp.nasaqui.com/mcp

No auth detected

MCP server metadata

Name: nasaq
Version: 0.3.1

Capabilities

tools.listChangedresources.listChanged

Server instructions

Nasaq (نسق) is a bilingual (English/Arabic, LTR/RTL) React design system built on Base UI and Tailwind v4. Before writing UI with Nasaq: call get_setup once, then list_components or search_components to find the right component, then get_component for its manual (props, examples, accessibility, RTL rules). Use only props the manual documents. Colours come from tokens (bg-nq-*, text-nq-*); never hard-code hex. Never recolour, mirror or redraw a product logo. Docs: https://docs.nasaqui.com. Components can also be added with the shadcn CLI: npx shadcn@latest add @nasaq/<name>. Not on React? Pass `framework` (shadcn, inertia, inertia-vue, vue, nuxt, blade, livewire, filament, laravel, tomatophp, html, alpine) to get_setup, list_components and get_component: get_setup returns that stack's guide and get_component a component's code for it. Components are ported to Vue, Blade and HTML + Alpine one by one; an unported one says so, and React or shadcn cover it meanwhile.

Known tools 6

list_components

Lists every Nasaq web component with its category, status, one-line summary and exports.

Inferred read-only

search_components

Ranks components for a need described in words, e.

Inferred read-only

get_component

Returns one component's details and manual.

Inferred read-only

get_foundation

Design rules behind the components: colour roles, layout and density, architecture, brand/logo rules, README spec.

Inferred read-only

list_tokens

CSS custom properties (--nq-*) with their value in each context (light, dark, brand, density).

Inferred read-only

get_setup

Install command, CSS imports, provider and the usual app skeleton.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.nasaq]
url = "https://mcp.nasaqui.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "nasaq": {
      "type": "http",
      "url": "https://mcp.nasaqui.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: nasaq
Remote MCP URL: https://mcp.nasaqui.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "nasaq": {
      "url": "https://mcp.nasaqui.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "nasaq": {
      "type": "http",
      "url": "https://mcp.nasaqui.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "nasaq",
  "transport": "streamable-http",
  "url": "https://mcp.nasaqui.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.