BluKavantUI Design system

Connect your assistant

Install the documentation server, configure your MCP client and keep its references up to date.

Connect in a few steps

  1. Install Node.js 20.19 or newer on the machine running your MCP client.
  2. Add the blukavantui entry below to your client’s MCP configuration. Keep all existing server entries, including your OutSystems MCP.
  3. Enable or reconnect the new server in your client, then ask it to look up a component.
{
  "mcpServers": {
    "blukavantui": {
      "command": "npx",
      "args": [
        "--yes",
        "--package=https://blukavantui.blutekmedia.com/downloads/blukavantui-mcp-1.2.0.tgz",
        "blukavantui-mcp"
      ]
    }
  }
}

For clients with a setup form, choose stdio, command npx, and enter the three arguments shown above. Configuration file locations vary by client. On Windows, use npx.cmd if the client requires the executable suffix.

The first launch downloads the package from this website. Once installed, the server reads its bundled documentation locally. It needs no Service Studio credentials and does not fetch your application files.

Local installation and executable paths

Download the current MCP archive from the overview and install it in a local tools folder:

npm install ./blukavantui-mcp-1.2.0.tgz

Configure the absolute path to node as the command and the absolute path to node_modules/@blukavantui/mcp/dist/server.mjs as its argument. This also works when a desktop client cannot find npx on its PATH.

The package is distributed here, not on the npm registry. Use the full archive URL in the quick-start configuration. Running the executable with --version prints its version; normal execution uses stdin/stdout for the MCP protocol.

Versions and scope

MCP 1.2.0 bundles web SDK 1.2.0, starter 1.2.0, Community 1.2.0 and the native API snapshot dated 2026-11-04.

The archive stays on that snapshot. Update its package URL when a newer MCP release is available; it will not silently switch your reference version. For native work, compare the contract with the live producer before editing.

Accessibility references retain their original evidence dates and package versions. They cover reusable component and screen-template support, not full-page or application conformance. Your content, colors, data services and integration still need validation.

The MCP archive contains references and examples, not the native component libraries. Existing component licensing and distribution terms still apply.

Download integrity

SHA-256:

b483edb0c611ed6e0aad953312ce431e1a320778da992e8660abc08899c12566

Machine-readable release manifest · Documentation index for assistants

Search BluKavantUI