Skip to main content
Glama
nuwax-ai

nuwax-openui-mcp

Official
by nuwax-ai
README.md
# Nuwax OpenUI MCP

pnpm workspace containing the Nuwax OpenUI MCP server and its frozen renderer
runtime.

## Packages

| Package                                        | Path               | Description                                                                                                                               |
| ---------------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| [`@nuwax-ai/openui-mcp`](packages/server)      | `packages/server`  | Lean stdio MCP server: OpenUI authoring guidance, validation, and durable artifact generation. Does **not** load the renderer at runtime. |
| [`@nuwax-ai/openui-runtime`](packages/runtime) | `packages/runtime` | Frozen, self-contained OpenUI renderer bundle (`runtime.js` + `runtime.css`) for sidecar / file preview.                                  |

See [`packages/server/README.md`](packages/server/README.md) for the MCP server
contract, installation, and artifact format.

## Development

```bash
pnpm install
pnpm verify          # format + lint + typecheck + test + build (both packages)
```

The server keeps its runtime lean: the component JSON Schema and authoring
reference are precomputed at build time (`pnpm gen:openui` →
`packages/server/src/generated/`) and read as static files, so the stdio process
never imports `@openuidev/react-ui` or `react-dom`.

## Publishing

```bash
pnpm publish --filter @nuwax-ai/openui-mcp
pnpm publish --filter @nuwax-ai/openui-runtime
```

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves reference documentation for OpenUI syntax, the other creates or updates OpenUI artifacts. No overlap in functionality.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with the 'nuwax_get_' and 'nuwax_render_' prefixes, making them predictable and easy to understand.

Tool Count3/5

With only 2 tools, the server feels minimally scoped. While it covers the core operations of getting guidance and rendering artifacts, it lacks additional utilities like listing or deleting, which may be needed.

Completeness2/5

The tool set covers documentation retrieval and artifact creation/update, but is missing essential operations like listing existing artifacts, deleting them, or validating schemas, leaving notable gaps in the lifecycle.

Maintenance

ActivitySlowing
ResponsivenessNo issues