Codeium proper doesn't expose MCP — use Windsurf (Codeium's agentic IDE) for the full skill flow.
Codeium's standalone extension is focused on autocomplete and chat with codebase context. As of this writing, it doesn't expose a public MCP-server or custom-skill registration API — Codeium has channeled their agentic work into Windsurf instead. If you want the full CleenUI skill experience inside a Codeium-family product, use Windsurf. This page covers what you can still do inside the Codeium extension itself.
Without MCP-style skill registration, your best path inside Codeium is to install CleenUI like any other npm package. Codeium's autocomplete and Chat will then suggest CleenUI components from your project's node_modules.
Codeium Chat reads your codebase, so once a CleenUI component is imported anywhere in your project, you can ask Codeium to use it in new files. The model picks up the pattern from existing usage.
If you want the Setup, Builder, and Theme skills callable as tools (the dummy-proof flow), Windsurf is the right Codeium product. The detail page for Windsurf walks through it in five steps.
Ask Codeium Chat to list the third-party libraries in your project. If @cleenui/react shows up, Codeium is indexing it and can pattern-match against existing usage.
Switch to Windsurf — same Codeium account, full MCP support, no extra subscription needed for individuals.
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.