Cursor supports MCP — register CleenUI in .cursor/mcp.json and the skills become available in Composer and Chat.
Cursor has first-class MCP support. The config file lives at .cursor/mcp.json (project-scope) or ~/.cursor/mcp.json (global). Once registered, the three CleenUI tools are available in Composer, Chat, and Cmd-K threads — no rules file needed.
Open your project folder in Cursor. The MCP config is project-scoped by default so it lives in the repo you're working on.
At the root of your project, create a folder called .cursor (if it doesn't exist), and add a file named mcp.json inside it. You can also use ~/.cursor/mcp.json for a global config available in every project.
Hit ⌘+Shift+J to open Cursor Settings, then go to Features → Model Context Protocol. Cursor will auto-discover the file you just created and list cleenui — toggle it on if it's off.
Cursor's Composer is where multi-file agent work happens. Hit ⌘+I, then just describe what you want. Cursor will call the cleenui setup tool automatically.
Click Apply in the Composer panel. Then run npm install in Cursor's integrated terminal — ⌃` (Ctrl+backtick) — to pull the new dependencies.
Open ⌘+Shift+J → Features → MCP. The cleenui server should show a green dot — and listing it from any Composer thread with /tools should show setup, builder, theme.
Restart Cursor — the mcp.json file is only re-scanned on startup. Confirm the file is named exactly .cursor/mcp.json, not cursor.mcp.json or .cursor/mcp.json.txt.
Click the failed entry — Cursor surfaces the npx error message. Most commonly it's a missing Node version or a corporate proxy blocking 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.