Sites by Clize MCP: what works in Claude, ChatGPT, Cursor, and Grok Bot
Ship a real marketing site from your coding agent: domain, HTTPS and a working inbox.
Registry name: ai.clize/sites (v0.35.5) | GitHub stars | npm @clize/sites: ? weekly downloads
Status grid
| App | Status | Date tested |
|---|---|---|
| Claude | Untested | Not yet tested |
| ChatGPT | Untested | Not yet tested |
| Cursor | Untested | Not yet tested |
| Grok Bot | Untested | Not yet tested |
| MCP Inspector (reference client) | Untested | Not yet tested |
| MCP TypeScript SDK (reference client) | Untested | Not yet tested |
Hands-on test results
No hands-on tests yet. We do not publish results until we have actually tested.
Automated handshake
No public remote endpoint to check (local or package-only server).
Gotchas
None recorded yet. Gotchas come only from hands-on tests.
Compare with other tested connectors | Connector Weather
Request a hands-on test of Sites by Clize
Get the badge
Maintain Sites by Clize or write about it? Show its live ConnectorReport status in your README or docs.
Markdown (README, docs)
[](https://connectorreport.com/c/ai-clize-sites?utm_source=badge&utm_medium=embed&utm_campaign=ai-clize-sites)
HTML
<a href="https://connectorreport.com/c/ai-clize-sites?utm_source=badge&utm_medium=embed&utm_campaign=ai-clize-sites"><img src="https://connectorreport.com/badge/ai-clize-sites.svg" alt="Sites by Clize MCP status on ConnectorReport"/></a>
The badge updates on its own after every retest. How badges work