Cline ships with native MCP support — configure cleenui via the MCP Servers panel in the Cline extension.
Cline runs as a VS Code extension and supports MCP servers out of the box. Configuration is managed through the UI (the stacked-server icon in the Cline panel's top toolbar), which writes to the extension's settings JSON behind the scenes.
Click the Cline icon in the activity bar to open the Cline panel. In the panel's top toolbar, click the stacked-server icon — this opens the MCP Servers view.
Cline opens its MCP settings as an editable JSON file. Add the cleenui entry under mcpServers. The autoApprove array lets you skip approval prompts for specific tools (leave it empty if you want approval each time).
Cline auto-reloads MCP configs on save. The MCP Servers panel will now show cleenui with a green status dot and its three tools.
Just type the request in the Cline panel. Cline will invoke the cleenui setup tool and ask for approval on each file change unless you've added them to autoApprove.
Open the MCP Servers panel in Cline and look for the green dot next to cleenui. Hover over it to see the three available tools.
Update the Cline extension to its latest version. MCP support requires v2.0 or later.
Replace 'npx' with the full path: %APPDATA%\npm\npx.cmd. Windows shells don't always resolve npx from PATH inside the extension host.
Click the failed entry — Cline surfaces the error message inline. Most often it's a Node version issue or a network block on npx.
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.