Proper UI

MCP integration

A Model Context Protocol server for Proper UI is planned but not yet built. This page describes the intent for anyone who wants to build it.

Planned, not built. There is no properui-mcp package and nothing to install today — packages/ in the Proper UI repo holds only cli, registry, and ui. This page describes the intent for an MCP server, for anyone who'd like to build it.

The idea

The properui CLI already exposes the whole registry through commands — list, search, add, diff (see the CLI docs). An MCP server would wrap that same registry so an MCP-aware assistant could search for and install components by description, without you leaving the chat.

What it would let you do

  • Search the registry by description instead of remembering an exact component name — the MCP equivalent of properui search.
  • Look up a component's props, examples, and dependencies before deciding to install it.
  • Have the assistant run the equivalent of properui add, including its dependency chain.
  • Ask for a full page example and get every component it composes in one pass, the way properui add example <name> does from the terminal.

How it would work

The intent is for the server to wrap the same registry JSON the CLI already reads (<registry>/<name>.json) rather than generating or guessing anything, and for its install operations to follow the same rules add already implements: resolving registryDependencies, rewriting @/ imports to the consuming project's configured alias, and reporting which files changed.

Building it

The pieces this would sit on top of already exist and are documented, if you want to take it on:

  • The registry format and build step — packages/registry (see packages/registry/src/build.ts) and the pnpm registry:build script.
  • The install logic to mirror — packages/cli/src/commands/add.ts, list.ts, search.ts, and diff.ts.
  • The CLI's own command surface — documented on the CLI page and in docs/cli.md.

Open an issue or a pull request on the GitHub repo if you'd like to build this — there's no packages/mcp yet, so there's no existing implementation to work around.

FAQs

The MCP server is tracked with the project's other planned work on the roadmap.