Drive Kleap from any AI agent
Connect ChatGPT, Claude, or Cursor to Kleap and build, edit and publish real websites in natural language. The agent does the talking — Kleap hosts, deploys, and guarantees it's actually live.
The verified-live guarantee
Other tools tell the agent “it's online” the moment a deploy is requested. Kleap reports a site as published only once the new version is provably serving at its live URL — otherwise it rolls back and says “not confirmed live.” An agent can never hand your user a dead link.
One backend, two ways to connect
Local — Claude Desktop, Cursor
A tiny stdio server your client runs locally. Authenticates with your kleap_live_sk_ key.
Remote — ChatGPT & hosted agents
A hosted connector at kleap.co/api/mcp. Connect with OAuth — no local process.
Both expose the same tools and arguments — anything you write for one works on the other.
The tools your agent gets
| create_app | Create a site from a prompt → returns a task |
| modify_app | Ask the app's AI to change it → returns a task |
| check_task | Poll a create/modify task to completion |
| retry_task | Resume a failed/stalled build — the agent's recovery path |
| publish_app | Publish with the verified-live guarantee |
| get_publish_status | Confirm a site is actually published & live |
| connect_domain | Connect a domain the user owns to a published app |
| search_domains | Find available domains (purchase stays user-confirmed) |
| list_apps | List the apps on your account |
| get_app | One app's status, slug & production URL |
| get_credits | Remaining credit balance & plan |
Set it up in 2 minutes
Pick your agent. Every path starts with one key.
Get your key
Go to Settings → API key and, under MCP / API access, click Generate MCP key. It looks like kleap_live_sk_…. Copy it — it's shown once.
⚠️ The other key on that page (kl_…) is for the Chrome extension only and will not authenticate the MCP.
Claude Desktop
Add Kleap to your claude_desktop_config.json and restart the app:
{
"mcpServers": {
"kleap": {
"command": "node",
"args": ["/absolute/path/to/kleap-mcp-server.mjs"],
"env": { "KLEAP_API_KEY": "kleap_live_sk_..." }
}
}
}Cursor
Same shape, in your project's .cursor/mcp.json:
// .cursor/mcp.json
{
"mcpServers": {
"kleap": {
"command": "node",
"args": ["/absolute/path/to/kleap-mcp-server.mjs"],
"env": { "KLEAP_API_KEY": "kleap_live_sk_..." }
}
}
}Verify the server starts:
KLEAP_API_KEY=kleap_live_sk_... node kleap-mcp-server.mjs
# → [kleap-mcp] ready (stdio) → https://kleap.co. Tools: list_apps, ...ChatGPT & hosted agents
No local process. Add a connector pointing at the remote MCP URL and authorize with OAuth (or paste your key):
https://kleap.co/api/mcpWhat it feels like
Give your agent a place to ship
Hosting, deploys, custom domains and the verified-live guarantee — handled. Your agent just builds.
Generate your MCP key