Autonomous Agent Publishing

Let agents publish, find and update work

Equip Claude Code, Cursor, or custom autonomous operators with instantaneous web app hosting and shareable deployments.

Publish this project's output to kailashe. Publishing guide: https://www.kailashe.com/for-agents.md

Compatible with:Claude CodeCursorChatGPTOpenCodeAiderAny MCP Agent

Copy the prompt

Send the one-line instruction to Claude Code, Cursor, or your local agent.

Approve once

When your agent triggers the terminal session, approve the publishing action.

Live URL & share

Receive an instant production URL with automatic previews and sharing controls.

Keep working after publishing

Ask the agent to update a site, rollback to a prior version, or search previous deployments. It follows your repository's access keys and team policies.

⚡ Instant delta updates🔒 Passcode & private read keys🕒 Automatic version snapshots

Current server: https://www.kailashe.com

Install the CLI

The CLI provides all operations from your terminal. MCP connects remotely without installing it.

Requires Node 24+ and npm on the machine running your CLI or agent.

npm install -g @kailashe/cli

If kailashe is not found, check npm's global bin directory is on PATH, then restart your terminal or agent client.

Authenticate

kailashe login --base 'https://www.kailashe.com'

Open the verification page, sign in and approve the session you started. The CLI saves this personal credential on this machine.

Publish and verify

kailashe whoami --base 'https://www.kailashe.com'
kailashe publish dist/ --base 'https://www.kailashe.com' --share none

Replace dist/ with your build output. A successful publish returns the site address.

Connect directly to this server over HTTP. No Node.js, CLI installation or local MCP process is needed.

MCP server address

https://www.kailashe.com/mcp

Authorize your agent

Clients with OAuth support — ChatGPT, Claude and others — need no token. Add the server address, choose OAuth, and the client opens this site's sign-in and a consent page; disconnect it at any time from My sites.

Copy MCP configuration

{
  "mcpServers": {
    "kailashe": {
      "url": "https://www.kailashe.com/mcp"
    }
  }
}

Verify the connection

Reload the client and check that 27 tools are available. Ask “What Kailashe sites have I published?” without naming MCP.

kailashe_connectionkailashe_publishkailashe_updatekailashe_editkailashe_findkailashe_folderskailashe_movekailashe_get_sitekailashe_readkailashe_forkkailashe_sharekailashe_set_officialkailashe_clear_officialkailashe_rollbackkailashe_claimkailashe_deletekailashe_exportkailashe_comments_listkailashe_comment_readkailashe_comment_imagekailashe_comment_resultkailashe_comment_contextkailashe_operation_statuskailashe_upload_statuskailashe_upload_startkailashe_upload_writekailashe_upload_cancel

Authentication & troubleshooting ↓Supported files & limits ↓Machine-readable guide ↗

Authentication and troubleshooting

CLI and remote MCP use the same Bearer credentials and account permissions. Configure each client separately. Operator tokens have broad privileges; remote MCP requires authentication for every request.

In CLI, an environment token overrides a saved token. Check the server address and stale KAILASHE_TOKEN when authentication fails. CLI logout removes local credentials.

CLI and MCP create public shares by default when publishing. Use --share none in the CLI to keep new work unshared; existing site visibility and sharing rules still apply.

Supported files and limits

HTML, folders, ZIP archives, and client-side web bundles. Hosted applications run sandboxed with full DOM, WebAssembly, Canvas, and external API fetch capabilities.

Full publishing reference