BluKavantUI MCP

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-0.4.5.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.

npm install ./blukavantui-mcp-0.4.5.tgz

A real screen created in Service Studio

On October 13, 2026, Codex fetched the native Card, ChatWidget and FloatButton contracts and examples through BluKavantUI MCP 0.2.0, then used the connected OutSystems MCP to create McpExamples → McpAssistantDemo in the sample module.

The screen passed Service Studio validation, was published, and was tested for sending messages, receiving a local reply, expand/minimize, Escape focus return, draft preservation and reopening with a custom SVG FloatButton. Its layout was checked at desktop, 390 px and 320 px widths.

Open the MCP-created OutSystems screen ↗

This verifies the two-MCP editing workflow with installed producer dependencies. Replies are deterministic demo text; connecting an AI service or business API is application-owned setup.

A Grid and edit Drawer connected to OutSystems data

Codex read the native Grid, Drawer, Button and Card contracts through BluKavantUI MCP, then used OutSystems MCP to build McpExamples → McpCustomerDemo. It reuses the demo’s existing BluGridDemoCustomer entity, LoadGridCustomers and SaveGridCustomers Server Actions.

The Grid loads 250 database customers. The Drawer edits name, seats and revenue, displays validation and save errors, and keeps the draft after a rejected save. The existing server workflow enforces permissions, validates values and checks the original record version before committing.

Browser checks verified a successful save after a full reload, invalid-input handling, Cancel without a write, and a stale save rejected from a second tab with its draft preserved. The test customer’s values were restored through the same save workflow.

Open the MCP Grid + Drawer sample ↗

Find it under MCP Grid + Drawer in the OutSystems demo navigation. Demo editor access is required. The component Blocks supply the UI; the consumer module owns its entity, permissions and persistence.

Use the working form workflow in your own web app

MCP 0.4.5 includes complete TypeScript source for a shared FormBuilder/FormRenderer workspace and HTTP storage adapter: save RawJson, upload files, submit answers, reload and download. It documents the exact web inputs, callback arguments, request-ID acknowledgements and application-owned backend routes.

blukavantui_get_guide({"topic":"web-form-storage"})

Both web component examples return this recipe in recommendedIntegration. The same guide is available at blukavantui://guides/web-form-storage. Its sourceFiles contain the complete implementation; the website's temporary preview adapter is clearly separate from your production storage.

FormBuilder Code → · FormRenderer Code →

Update an older pinned MCP package URL to 0.4.5 and reconnect to load this guide.

Save forms as JSON. Keep one shared screen.

The MCP now includes the published save/reload and attachment setup: one RawJson attribute, a shared screen, and one upload endpoint. It provides exact FormBuilder/FormRenderer inputs, event-to-handler mappings, save acknowledgements, reload state and the Binary upload/download contract.

blukavantui_get_guide({"topic":"outsystems-form-storage"})

The same recipe is included in native FormBuilder and FormRenderer examples. Search for RawJson or save reload attachments. It identifies the library Blocks separately from the demo’s consumer-owned Entity, Server Action and REST API, and preserves the required access checks.

Read the complete setup and test workflow →

Enterprise OutSystems recipe. Update an older pinned MCP package URL to the version above and reconnect to load this guidance.

Tools, resources and prompts

blukavantui_search

Find components, API properties, templates and guides. Filter by platform and native edition.

blukavantui_get_component

Read an overview, API, types or accessibility evidence. An optional exact version check rejects mismatched references.

blukavantui_get_example

Get working TypeScript source or native binding examples and blueprints. Chat includes request/response wiring; Form Builder and Renderer include the complete native storage and attachment recipe.

blukavantui_get_template

Get components, CSS, assets and setup for either platform. Request each listed web source file by name.

blukavantui_get_guide

Read installation, web/OutSystems workflows, Community scope, native chat wiring, form storage and accessibility guidance. Use topic outsystems-form-storage for save/reload and attachments.

{
  "name": "ChatWidget",
  "platform": "outsystems",
  "edition": "enterprise",
  "section": "api"
}

Tools and prompts use the full blukavantui_ prefix. Version 0.1.0 used the older bluui_ shorthand; update your package URL and saved tool calls when moving to 0.2.0. The version 0.1.0 archive remains available for existing pinned configurations.

Resources

blukavantui://catalog lists available components and templates. blukavantui://guides/outsystems-workflow describes coordination with the editor. blukavantui://guides/outsystems-form-storage contains the native JSON persistence and attachment recipe. The resource template blukavantui://components/{platform}/{edition}/{name} exposes full contracts; use enterprise in the edition segment for web resources.

Reusable prompts

blukavantui_build_web_screen and blukavantui_build_outsystems_screen accept a task; the native prompt also accepts an edition. Clients that expose MCP prompts can use them to start a screen-building workflow.

Versions and scope

MCP 0.4.5 bundles web SDK 0.9.0, starter 0.9.4, Community 0.3.3 and the native API snapshot dated 2026-10-14.

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.

409d2369cca9797a9ce2e69480f7ac0b0c88add33300ffeacfa2461dee52d3b8