Sites by Clize

Name: Sites by Clize
Author: cooldk

by cooldkversion 0.35.5i★ 0iRuns on your computer

Registry nameai.clize/sites

How to install

What it does

Ship a real marketing site from your coding agent: domain, HTTPS and a working inbox.

Connects Runs on your computer
Account or key No key needed
Category Developer tools

Install

Pick the AI app you use, then copy the settings.

Passed 3/3 checks · Runs on your computer

First: which AI do you use?

ClaudeWeb · app · phoneChatGPTWebClaude CodeTerminalCursorCode editorVS CodeCode editorOtherOther apps

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Done

Paste these settings and save the file

{
  "mcpServers": {
    "sites": {
      "command": "npx",
      "args": [
        "-y",
        "@clize/sites",
        "--profile",
        "sites"
      ]
    }
  }
}

Done

Quit Claude and open it again
Done
Try it
Use Sites by Clize and tell me what you can do for me, then show me one thing
✓ If Claude says it is using Sites by Clize or shows a Sites by Clize tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Sites by Clize yet

Sites by Clize runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Sites by Clize

Steps for Claude →Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Steps for Claude Code →Install Node.js on your computer first (one time)
Steps for Cursor →Install Node.js on your computer first (one time)
Steps for VS Code →Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Sentry✓ ChatGPT
Compiler Explorer✓ ChatGPT
GitDiagram✓ ChatGPT

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Done

Paste this command and press Enter

claude mcp add --scope user sites -- npx -y @clize/sites --profile sites

Done

Type /mcp in Claude Code
You should see Sites by Clize listed as connected
Done
Try it
Use Sites by Clize and tell me what you can do for me, then show me one thing
✓ If Claude Code says it is using Sites by Clize or shows a Sites by Clize tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Click this button to open Cursor
Open in Cursor
Cursor asks you to confirm; click Install
Done
Open the AI chat in Cursor in Agent mode
Done
Try it
Use Sites by Clize and tell me what you can do for me, then show me one thing
✓ If Cursor says it is using Sites by Clize or shows a Sites by Clize tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Click this button to open VS Code
Open in VS Code
VS Code asks you to confirm; click Install
Done
Open the AI chat in VS Code in Agent mode
Done
Try it
Use Sites by Clize and tell me what you can do for me, then show me one thing
✓ If VS Code says it is using Sites by Clize or shows a Sites by Clize tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Sites by Clize💬 Discussion →

For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user sites -- npx -y @clize/sites --profile sites

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "sites": {
      "command": "npx",
      "args": [
        "-y",
        "@clize/sites",
        "--profile",
        "sites"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "sites": {
      "command": "npx",
      "args": [
        "-y",
        "@clize/sites",
        "--profile",
        "sites"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "sites": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@clize/sites",
        "--profile",
        "sites"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub stars i: 0
Downloads per weeki: 87/wk
Verified domain: ✓ clize.ai
Licence i: MIT
Connection: Runs on your computer
Transport: stdio
Latest versioni: 0.35.5
Categoryi: Developer tools
Published to registryi: Sep 3, 2026
Code last changedi: Oct 1, 2026
Maker: cooldk
Packages: npm: @clize/sites
Repo: cooldk/clize-cli
Website: clize.ai
Registry status: Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

Claude Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Raycast

All apps, with pros and cons →

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 12, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain clize.ai (the registry checks domain ownership)
✓ Pass
Still maintained
Code last changed 42 days ago
✓ Pass
Has a licence
Uses MIT
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

User reviews

No reviews yet

Compared with others in Developer toolsi

More stars than 0% of the other 5811 servers in this category
Published to the registry more recently than 32% of the other 5811 servers in this category
Basic checks equal to or better than 100% of the other 5811 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sites by Clize safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 42 days ago, and the latest version (0.35.5) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: REA, GitHub, Serena MCP: the IDE for your agent

Others in the same category

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 453.3KUpdated today

Runs on your computer

Install

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.4KUpdated 9 days ago

Computer or cloud

Install

Serena MCP: the IDE for your agent

A powerful toolkit for coding, providing semantic retrieval and editing capabilities.

by oraiosWidely used↓ 35.2K/wk★ 31.3KUpdated 6 months ago

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Clize

Clize is a CLI and MCP server that gives AI coding agents real-world actions: domains, email, deploys, payments, and media generation. Your agent already has a brain — Clize gives it hands: a domain, a working inbox, a live website. One CLI (plus an MCP server) so coding agents in Claude Code / Codex can register domains, run real email, build & ship sites and short clips, generate media, and collect payments from their customers — across as many projects as you run.

→ [clize.ai](https://clize.ai)

Install

npm i -g @clize/clize

clize install # wire clize into your coding agent (Claude Code / Codex)

clize install is the step that makes your agent actually *reach for* clize — a binary on your PATH doesn't tell the agent it exists. By default it drops clize's skill (when to use it + the safety gates) into each agent's skills dir; the skill is lightweight — only its short description sits in context until something triggers it. It auto-detects Claude Code (~/.claude), Codex (~/.codex) and Pi (~/.pi); Codex and Pi share the open ~/.agents/skills directory, so any agent that reads it gets the skill too. Scope with --claude / --codex / --pi, preview with --dry-run. Add --mcp to also register the clize-mcp server — opt-in, because an MCP server's tool list stays in context every session.

Update later with one command — pulls the latest release and refreshes the skill together:

clize update            # or `clize update --check` to only check for a newer version

If something looks stale after an update, clize doctor prints what's installed vs what's actually running — CLI version (and the upgrade command that works for your install manager: volta / pnpm / asdf / …), skill drift, and control-plane reachability.

Output is English by default. CLIZE_LANG=zh (or a zh* system locale) switches the CLI, the MCP tool descriptions and the control plane's messages to Chinese; the dictionary lives in src/i18n/zh.ts.

Quickstart (hosted)

clize login                              # browser authorize; the first login creates your account

clize claim acme --email # free identity: acme.clize.app + support@acme.clize.app clize init --handle acme # bind this directory (deploy / send / inbox infer the rest) clize email inbox --wait-for "verify" # give the new inbox a minute, then the agent signs up with support@acme.clize.app and reads the code here clize status # who is waiting (real people + codes only), this month's spend clize email send --to a@b.com --subject "Re: …" --text "…" # queued for a one-tap approval in the console; --confirm sends now clize deploy ./site # ship a static site → https://acme.clize.app

Examples you can run (recorded 2026-10-01, with timings, costs and what failed)

Example	What it does	Cost
01 · first verification email	install → claim an address with an inbox → read a verification code → queue a reply a person must approve	$0
02 · HTML → HTTPS → your domain	a three-file folder to `https:// .clize.app`, then a domain and a mailbox on it	$0 (+ the domain, quoted first)
03 · one SEO loop	`clize seo check` on a real site → two changes tied to numbers → publish → dated re-read	$0

Each one is Clize's own account and site (self-use), not a customer story.

Hosted — just log in

Log in with	What runs where
`clize login` (web: GitHub / Google / email) — or `clize login --token clize_…` for CI / headless	Commands call the clize backend; resources run on clize's infra. You never touch Cloudflare / Vercel keys.

clize is a thin client: the CLI / MCP carry no infrastructure credentials and talk only to the clize control plane — domains, email, deploy, and media all run hosted. (Credentials live in your dashboard; bring-your-own Cloudflare / Vercel is configured there, not on your machine.)

A few specifics worth knowing:

clize deploy and clize email send need --domain / --from — unless the directory is bound with clize init --handle , which infers both from ./clize.json. Deploy is directory-based (multi-file static sites).
gen image --ref/--mask (image-to-image / inpainting / multi-image composition) work hosted — reference-image caps follow the upstream model: 16 for gpt-image-2, 14 for nano-banana-2 (video/veo takes 3); each ≤10 MB, ≤80 MB total. gpt-image-2 runs as an async task (heavy multi-ref jobs take minutes — no sync-pipe timeouts): the CLI waits by default (--timeout, default 300 s), or use --async and collect with gen status ; one image per task (--n > 1 → split), --mask inpainting is nano-banana-2 only. gen budget pre-approval isn't hosted yet: every generation confirms individually with --confirm.
Free *.clize.app handle: clize claim . Your own domain: clize domain buy / clize domain import. Run clize check to verify your login.
Free-tier quotas (anti-abuse, per tenant): 3 handles · 5 mailboxes · 10 claim attempts/day · 30 outbound emails/day · 20 deploys/day · 500 MB per site. Any top-up lifts you to the trusted tier (10 · 30 · 30 · 200 · 100 · 5 GB). Over-limit calls return a plain 429 — nothing is charged.
A deploy target is a free handle or a whole domain in your account; a subdomain of your domain (blog.example.com) is not a separate deploy target today. Names bought with clize domain buy are registered with Clize's registrant contact at the underlying registrar — to be the registrant of record, register elsewhere and clize domain import. Some ccTLDs (.de .fr .es .jp .kr .com.br .uk .eu) are not registrable through Clize; clize domain tlds lists the 555 that are.

What it does

Area	Commands
Identity	`clize claim --email` — a first-come, free identity for your agent: `.clize.app` (site placeholder) plus a receiving `support@ .clize.app`. Without `--email` you get the name and the site only (`clize email setup` opens the inbox later) — inbound is opt-in because each inbox costs 4 DNS records in the shared `clize.app` zone, and that zone is the whole platform's free-handle capacity
Domains	`clize domain search / tlds / buy / import / list`; `clize domain check` runs six layers in repair order — registry delegation (public DoH) → Cloudflare zone → worker binding → content → edge AI-crawler policy (Cloudflare `ai_bots_protection`; new zones default to blocking AI crawlers from 2026-09-15, and a blocked edge beats any robots.txt) → http→https (a real `http://` request must get a 301 to https; clize turns on Cloudflare's Always Use HTTPS on every zone it deploys to, imports or registers, and `domain canonicalize` does too)
Email	The mailbox your agent signs up for services with and reads verification codes from (`clize email inbox [domain] --wait-for` polls until the mail arrives), and the inbox real people write to. `clize email address add` opens a mailbox in one step (object + receiving) on any domain you own — as many per domain as you need (`ops@`, `sales@`, one per agent or per person); `--forward me@gmail.com` copies mail to a personal inbox, `--owner` makes it someone's private mailbox. `support@ .clize.app` is available on any claimed handle via `clize email setup` (or `clize claim --email`). Read with `inbox` (triaged: promos / notices / spam are filtered, `--all` shows everything) / `show` / `thread` / `search`, correct triage with `mark`, send with `send` (`--attach`). Mail is stored permanently and indexed. Multi-user: `clize members invite alice@corp.com --mailbox alice@` lets a person log in and use their own mailbox; owners/admins see every mailbox in the account. Per-agent keys: `clize email key create --scope read,send --address ops@` . Command reference: clize.ai/docs/commands.
Outbox	Interactive `clize email send` without `--confirm` lands in an outbox instead of vanishing as a draft: a person approves or rejects it in the console (Home → needs you → Inbox), or from the digest email's signed one-tap link; `clize email pending` lists what is waiting and `status` counts it. A standing allowlist (a recipient or `@domain`, weekly cap 5) can be set only in the console — approvals and the allowlist are refused to CLI-issued keys, so a prompt injection cannot grant itself an exemption. Sends to allowlisted recipients within the cap go out without `--confirm`.
Send API (server-callable)	`POST /v1/email/send` — transactional email from a long-running backend (fly.io / cron), Resend/Postmark-shaped, sending from a domain already in Clize (no second email vendor). Auth is a scoped send key (`clize_sk_…`: send-only, lockable to specific domains) — `clize email key create/list/revoke`. No `--confirm` (the human-review gate stays on interactive `email send`). Idempotency-Key, HMAC-signed delivery webhooks (bounce/complaint), RFC 8058 one-click unsubscribe + suppression lists (`email delivery-webhook / suppressions / messages`). Walkthrough: sending from a backend with a scoped key · webhooks and delivery events.
Media	`clize gen image / video / music` — text→image (`gpt-image-2` / `nano-banana-2`, with `--ref` / `--mask` for image-to-image and inpainting), text/image→video (`veo`), text→music (`suno`); long tasks via `gen jobs / status`. Every spend is gated by `--confirm` (`gen budget` pre-approval for hosted is on the roadmap). Results land as local files, ready to `deploy` or `email --attach`.
Build · site (hosted methods)	`clize build site start` — a hosted design system that briefs your agent on a cohesive style before it writes the site, so pages land with taste instead of AI-template sludge. Then `build site recommend / list / get / search / review` + `build site stack` for stack-specific guidance (React / Next / SwiftUI / …). The former `clize design …` spelling still works as a hidden alias. `clize build site check [--live ]` is the free pre-ship lint: doorway-shaped near-duplicates (≥60% shared visible text) and thin pages, `_redirects` targets (probed live with `--live`), hreflang reciprocity, FAQ text vs JSON-LD, canonical/noindex conflicts, sitemap membership — errors exit non-zero. Since 0.41.0 it also reports three GEO warnings (never errors): a comparison page whose first 200 words do not name your own product, a comparison page with no , a content page with no visible date or one over 12 months old.
Build · clip (hosted methods)	`clize build clip start` → your agent writes a shot-by-shot blueprint → `build clip check` (free local lint: continuity, dialogue coverage, timing) → `build clip render --confirm` (💰 one summed quote, batch-generate + merge, resumable). One-off footage stays `gen video`.

| Deploy | clize deploy --domain — multi-file static sites; free *.clize.app or your own domain. Preview locally first with clize serve (proper Range support — pages actually play in Safari). Deploy runs the same guards as build site check before uploading — doorway-shaped near-duplicates block the upload (--allow-similar to override), and after upload every _redirects rule is probed live; the result rides along in the deploy output as guards (including the three GEO warnings from build site check). Deploy only adds or overwrites: a live path missing from stays online and is listed under `o

Only the beginning is shown; read the rest in the repo

Sites by Clize

What it does

Install

Install Node.js

Open the Claude desktop app’s settings file

Paste these settings and save the file

Quit Claude and open it again

Try it

What you can do instead

Install Node.js

Open Terminal

Paste this command and press Enter

Type /mcp in Claude Code

Try it

Install Node.js

Click this button to open Cursor

Open the AI chat in Cursor in Agent mode

Try it

Install Node.js

Click this button to open VS Code

Open the AI chat in VS Code in Agent mode

Try it

Installed on your computer

At a glance

Which apps can use it

Related guides

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Discussion

User reviews

Compared with others in Developer toolsi

Common questions

Others in the same category

REA

GitHub

Serena MCP: the IDE for your agent

README from the maker

Clize

Install

Quickstart (hosted)

Examples you can run (recorded 2026-10-01, with timings, costs and what failed)

Hosted — just log in

What it does