Continue supports MCP servers — add cleenui to config.yaml or a standalone file in .continue/mcpServers/.
Continue is an open-source AI code assistant. It supports MCP servers but only in agent mode — the Setup, Builder, and Theme tools register cleanly. The config is YAML, and Continue accepts either an inline mcpServers array in config.yaml or a per-server standalone YAML file in .continue/mcpServers/.
Continue uses YAML config at ~/.continue/config.yaml (the old config.json is legacy and being phased out). Open the file in your editor.
Note: mcpServers in Continue is an array of entries (each with a name field), not the object-keyed shape Claude Code and Cursor use. Same fields otherwise.
Continue also discovers any YAML files dropped into .continue/mcpServers/. Useful if you want CleenUI scoped to a single project rather than your global config.
Open Continue's chat panel and switch from Chat / Edit mode to Agent mode (mode selector at the top of the chat). MCP tools are only available in agent mode.
Open Continue's chat and look at the tool inventory in agent mode. cleenui:setup, builder, and theme should be listed.
Switch Continue to Agent mode. Chat and Edit modes intentionally don't expose MCP tool calling.
Run 'Continue: Reload Configuration' from the command palette. Continue caches the YAML and doesn't always hot-reload on save.
Two paths to your first component. Pick the one that fits how your team builds.
One prompt to your AI tool. The Setup skill handles dependencies, design tokens, build config, and component registration — all without leaving your editor.
The classic flow. Install the package, import the styles, drop in your first component. No agents required — same end result.