Cody supports MCP via the cody.mcpServers setting — enable the feature flag and add cleenui to settings.json.
Cody supports local MCP servers as of recent versions. There are two gotchas: (1) MCP support is behind a feature flag that has to be enabled first, and (2) only local STDIO servers are supported (no remote URL servers). For VS Code the config goes into the standard settings.json under the cody.mcpServers key; JetBrains uses a separate cody_settings.json file.
Cody's MCP support is gated. Open Cody settings via the extension's gear icon and look for the agentic context section. Toggle 'agentic-context-mcp-enabled' on.
For VS Code, open settings.json (⌘+Shift+P → 'Preferences: Open User Settings (JSON)'). Add cleenui under cody.mcpServers. For JetBrains the file is cody_settings.json — same JSON shape.
Cody picks up MCP servers on reload. Run 'Cody: Reload' from the command palette, or restart your editor.
Open Cody Chat. With MCP enabled, the cleenui tools surface to the agent automatically — just describe what you want.
In Cody settings, confirm agentic-context-mcp-enabled is on. If it isn't shown at all, your Cody version may be too old — update the extension.
Update the Cody extension. MCP support is recent — older builds don't expose the flag.
Confirm you're in Cody Chat (not the older command/recipe surface). MCP tools only flow through the Chat interface.
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.