Documentation

MCP server

Coding agents search the live registry, fetch source, and — on a local project — compose, add pages, install, theme, and upgrade. Listed as io.github.pedrogbraz/cronus-ui on the official MCP Registry. Two transports: hosted HTTP for cloud builders, stdio for IDEs that can spawn a process.

Open /mcp llms.txt

Official MCP Registry

Name: io.github.pedrogbraz/cronus-ui. Clients that browse the registry get stdio (npx -y cronus-ui-mcp) and the hosted remote at https://aicronus.com/mcp.

Pick a transport

The hosted server is the same catalog as stdio. It cannot write files — there is no project on the other side of a URL.

Hosted Streamable HTTP versus local stdio.
Transport	Connect with	Tools	Use when
Streamable HTTP	`https://aicronus.com/mcp`	Read-only catalog	v0, Lovable, Replit, Bolt, Base44, or any client that takes a URL
stdio	`npx -y cronus-ui-mcp`	Read + write	Claude Code, Cursor, VS Code, Codex, Grok CLI, OpenCode, Zed

Greenfield is not an MCP tool

Scaffold with npx create-cronus-app my-app --template saas, then point the stdio server at that project. Write tools spawn the pinned cronus-ui CLI inside an already-inited app.

Hosted HTTP

Paste the URL into any client that speaks Streamable HTTP. No API key. This preview also serves the same handler at /mcp.

Custom MCP / Connectors

bash

https://aicronus.com/mcp

Paste the URL. No API key. Catalog only — install still happens in a local repo via the CLI.

A GET without the SSE Accept header returns a small JSON discovery document:

bash

curl -s https://aicronus.com/mcp

Local stdio

Full surface: search, install, compose, add-page, theme, upgrade. The process runs on your machine, so it can write the project.

One command writes every project file. Restart the agent afterwards.

bash

npx cronus-ui mcp init

terminal

bash

claude mcp add cronus-ui -- npx -y cronus-ui-mcp

Project scope: the same JSON in `.mcp.json` at the repo root.

Conductor and Kilo Code inherit the agent they wrap. A repo-root .mcp.json (stdio JSON above, the shape create-cronus-app already writes) is enough for Conductor Claude sessions. Kilo takes the same command + args as Cursor.

Which client

Config file and transport for each host. VS Code is the one that does not use mcpServers.

MCP-capable clients and how they connect to Cronus UI.
Client	Transport	Config	Notes
Claude Code	both	claude mcp add / .mcp.json	npx cronus-ui mcp init writes .mcp.json (stdio).
Cursor	both	~/.cursor/mcp.json or .cursor/mcp.json	Root key is mcpServers.
Windsurf	both	~/.codeium/windsurf/mcp_config.json	Same mcpServers JSON as Cursor.
VS Code / GitHub Copilot	both	.vscode/mcp.json	Root key is servers, not mcpServers.
Codex	both	~/.codex/config.toml	codex mcp add cronus-ui -- npx -y cronus-ui-mcp.
Grok CLI	both	~/.grok/config.toml	grok mcp add. Also reads .mcp.json / .cursor/mcp.json.
OpenCode	both	opencode.json	Root key is mcp; command is a single array.
Zed	stdio	settings.json → context_servers	Zed calls MCP servers context servers.
Antigravity	stdio	~/.gemini/config/mcp_config.json	Shared with Antigravity IDE and CLI. mcpServers JSON.
Kilo Code	stdio	kilo.json / .kilocode/	Local stdio. Same command + args as Cursor.
Conductor	stdio	inherits Claude Code / Codex / Cursor	.mcp.json in the repo is enough for Claude sessions.
v0 / Lovable / Replit / Bolt / Base44	http	Custom MCP URL field	Paste https://aicronus.com/mcp. Read-only catalog — no local CLI.

Tools

Hosted HTTP exposes the read list. stdio adds the write list, which spawns cronus-ui@pinned inside the detected project root.

Read

list_components
list_blocks
list_catalog
match_catalog
search_registry
get_component
get_install_command
get_design_context

Write (stdio only)

compose_app
add_page
set_theme
install_component
upgrade_components
apply_theme