Use component guidance alongside your connected editor to build and validate native screens.
Ask Codex, Claude Code or another MCP-enabled agent for a screen. It reads the component details from BluKavantUI MCP, then calls OutSystems MCP to create or edit that screen in Service Studio.
BluKavantUI MCP supplies the APIs, producer modules, types, CSS requirements and working examples.
The agent turns those references into calls to OutSystems MCP: add Blocks, create typed locals, bind inputs and wire actions.
The agent checks Service Studio validation, tests the resulting screen and publishes through OutSystems MCP when you authorize it and its publishing permission is enabled.
BluKavantUI MCP reads documentation. Your agent can still make native changes by calling the separately connected OutSystems MCP. The servers do not need to call each other directly—the agent carries the component guidance into the editing workflow.
Actual editor operations depend on the tools your OutSystems MCP exposes. If a dependency-selection step is unavailable, the agent should identify that specific manual step.
“Using both MCPs, add a full-edition ChatWidget to my open consumer module. Inspect its dependencies first, fetch the native contract and binding recipe, wire its events to screen state, and check validation messages.”
“Using both MCPs, build a customer Grid with an edit Drawer from my existing Customer entity. Inspect its attributes and server actions, reuse the existing permissions and save validation, wire loading and saving, and preserve drafts when a save fails. Test persistence by reloading.”
“Read the OutSystems setup for the Request template, then use OutSystems MCP to create a copy in my consumer module. Preserve the shared layout and typed lists, and connect submission to my Server Action.”
“My TreeSelect reports ‘Expecting a BluTreeNodeList Type’. Use BluKavantUI MCP to read the native contract, inspect the live input and local variable with OutSystems MCP, then correct the producer type and validate the module.”
“In my installed Community consumer, add a read-only Grid Basic and a detail Card. Use the Community contracts and producers, wire row selection to the detail view, and verify the compiled screen.”
platform: "outsystems" and edition: "pro" or "community".For “Expecting a BluTreeNodeList Type”, use the exact referenced producer’s list type for your consumer value. A locally recreated structure with the same name, or one from a different edition, is not interchangeable.
Community Web includes 67 components, including Basic Grid. The MCP includes 67 verified Community component contracts covering 85 native Blocks, plus the separate published Pro contracts. The MCP includes all nine Community and five Pro native templates with their separate demo modules, exact producer dependencies and shared layouts. Community libraries and demos are available on Forge; Pro uses the separate licensed delivery process.
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 →
Pro OutSystems recipe. Update an older pinned MCP package URL to the current version on the connection guide and reconnect to load this guidance.
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 MigratedShowcases → 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.
Codex read the native Grid, Drawer, Button and Card contracts through BluKavantUI MCP, then used OutSystems MCP to build ProShowcases → 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.