Kailashe MCP Server
Integrates with Cloudflare DNS for platform subdomain claims and custom domain setup, using a Cloudflare API token and zone ID to create proxied DNS records with Universal SSL.
Allows deploying static and frontend projects to Cloudflare Pages through the provider's CLI after plan approval.
Allows deploying serverless Worker projects to Cloudflare Workers through the provider's CLI after plan approval.
Allows deploying projects to DigitalOcean through its CLI on the user's logged-in account after plan approval.
Allows deploying projects to Modal through its CLI on the user's logged-in account after plan approval.
Allows deploying Next.js and other static or SSR front-end projects to Vercel, using the generated *.vercel.app domain, and can also handle Vercel DNS for platform domain claims.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Kailashe
Open source (MIT) CLI, stdio MCP server, and skill pack that takes an AI-built project from "runs locally" to "live URL" — and then operates it as a side business: market research, an archetype plan, a backlog, a tool manifest, and a composed prompt.md for Muse.
Kailashe never handles provider credentials. Deploys run through each provider's own CLI (AWS, DigitalOcean, Vercel, Cloudflare Pages, Cloudflare Workers, Fly, Modal) on your own logged-in account, behind an allowlisted, redacting, audit-logged runner. See SECURITY.md and PRIVACY.md.
Spec: docs/SPEC.md · Tasks: TASKS.md · Skill pack: skill/kailashe-operator
Commands
git clone https://github.com/Shvmshrd/kailashe-cloud.git
cd kailashe-cloud
pnpm install && pnpm build
cd packages/cli && npm link && cd ../.. # one-time: puts `kailashe-cloud` on your PATH
cd ../your-site
kailashe-cloud deploy # publish → live URL, then write business-plan.md + prompt.md
kailashe-cloud gate prompt.mdOther commands: kailashe-cloud init (install the operator skill pack), doctor, validate-pack, graph (read + graph the project, show the first hosting step), domain (tenant subdomain claims).
Deploying a site to kailashe.com
kailashe-cloud deploy publishes a site to the hosted
kailashe.com platform and returns the live
address you selected: https://<label>.kailashe.com. There is no build
step — the folder is uploaded as-is, so publish your build output folder
(dist/, public/, …) or any ready-to-serve site folder.
# one-time: install the platform CLI and sign in once in your browser
# (Kailashe runs `kailashe login` for you if you are signed out)
npm install -g @kailashe/cli
cd your-site
kailashe-cloud deploy # asks for the label → https://<label>.kailashe.com
kailashe-cloud deploy --label bcard # or pass it directly
kailashe-cloud deploy --label bcard --share none --no-plan --jsonNo token handling is needed for the default route: deploy checks the
platform CLI's login (kailashe whoami), runs kailashe login if you
are signed out, and publishes through that stored login — the token file
is read only by that CLI, never by Kailashe. If you prefer, set
KAILASHE_TOKEN in your own terminal instead and the same command
publishes over the platform's MCP endpoint with that token (sent only as
a bearer header, never logged or written to disk).
Projects that need a server runtime (server apps, APIs) are refused
with a "not fit for Kailashe at the moment" message (exit 6) — host
those on a provider below instead. A successful deploy is recorded in
.kailashe/deploy-state.json, and the same run then generates
business-plan.md and a composed prompt.md for Muse in the project
folder — both addressed at the live URL it just created (--no-plan
skips this). Finish with kailashe-cloud gate prompt.md.
For projects that need a server runtime, the provider hosting flow (kailashe-cloud graph shows the first step) asks which provider to use (it preselects one with a reason; AWS is never preselected), shows an exact plan — resources, commands, monthly cost, rollback — and runs nothing create/modify/delete until you approve.
Related MCP server: AI Knowledge Center MCP
Before & during the hackathon
Before: kailashe.com already existed as publishing infrastructure — hosted sites at https://<name>.kailashe.com, a remote Kailashe MCP server (27 tools) that agents can drive, the Kailashe CLI (kailashe login, kailashe publish), and an agent contract. It could put a site on the internet; everything after that needed a human.
During (this repo): Kailashe Cloud connects the platform to Muse. One command — kailashe-cloud deploy — reads your project, deploys it to your chosen <label>.kailashe.com, verifies it live, and in the same run generates business-plan.md + prompt.md. From there Muse operates the business: market research, GTM, a content engine, support, payments through approved connectors, and weekly operations — with approvals before anything is sent or spent, and unknowns listed instead of invented. Also built: multi-provider hosting (Vercel-first; Cloudflare, Modal, Fly, DigitalOcean, AWS), kailashe.tech tenant subdomains, a stdio MCP server, a skill pack, and a 646-test suite. Live proof: https://bcard.kailashe.com. Full story: HACKATHON.md.
How a deploy gets its domain
Kailashe first reads your project (kailashe-cloud graph) — detector profile plus a project graph. For the richest graph it can read Graphify output (optional, Apache-2.0, user-installed: pipx install graphifyy==0.9.97, graphify install, then /graphify . in Claude Code writes graphify-out/graph.json); without it, a built-in graph of files/packages/imports is used.
Then the flow is:
If the project fits Vercel (Next.js and other front ends), Kailashe offers Vercel first. A Vercel deploy uses the Vercel domain itself (
*.vercel.app) — there is no domain step at all.Any other host (Cloudflare Workers, Modal, Fly, DigitalOcean, … — you log in with that provider's own CLI; Kailashe never takes provider credentials): only now does Kailashe ask "Do you have a domain?"
Yes → Kailashe prints the exact DNS settings (apex +
wwwCNAMEs to your deployed host) for you to add at your registrar.No → pick a label, e.g.
zi1, and Kailashe claimszi1.kailashe.techfor you: a CNAME to your deployed host with HTTPS on (Cloudflare-proxied Universal SSL, or Vercel DNS automatic TLS, depending on where thekailashe.techzone is hosted). Every label is globally unique and can be claimed only once — it stays bound to its first user even after release, and each user holds one active label at a time.
kailashe-cloud domain setup --provider vercel --target my-app.vercel.app # Vercel: uses the Vercel domain
kailashe-cloud domain setup --label zi1 --target my-app.modal.run --user u1 # claim zi1.kailashe.tech
kailashe-cloud domain check zi1 # is the label still free?
kailashe-cloud domain custom mysite.com --target my-app.modal.run # your domain: DNS settings
kailashe-cloud domain release zi1 --user u1 # release (label stays yours)Tenant DNS writes need operator configuration the user never sees: CLOUDFLARE_API_TOKEN + CLOUDFLARE_ZONE_ID, or VERCEL_API_TOKEN if the kailashe.tech zone uses Vercel DNS. Without them, claims stop with exit 3 and nothing is claimed. KAILASHE_PLATFORM_DOMAIN overrides the platform domain (kailashe.tech). Claims persist in .kailashe/tenants.json.
Exit codes
Code | Meaning |
0 | ok |
1 | unexpected error |
2 | usage error (bad flags/args) |
3 | needs input, or approval denied |
4 | provider auth failed |
5 | deploy failed or partial |
6 | validation failed |
7 | budget exceeded |
130 | interrupted (SIGINT) |
Configuration
Copy .env.example to .env. Key settings: MODEL_API_KEY, KAILASHE_MODEL (default muse-spark-1.3), KAILASHE_LLM_BASE_URL (default https://api.meta.ai/v1; any OpenAI-compatible endpoint works), KAILASHE_MODEL_BUDGET_USD (default 3 per run), KAILASHE_MARKET_BUDGET_USD (no paid market calls while unset). Contributor-tier models (*-contributor) are refused unless KAILASHE_ALLOW_CONTRIBUTOR_TIER=1 — see PRIVACY.md.
MCP server
packages/mcp exposes a stdio MCP server: read tools detect_project, list_providers, status; write tools deploy, scan_business, build_prompt require explicit confirmation.
Development
pnpm install && pnpm build && pnpm typecheck && pnpm lint && pnpm testpnpm test:e2e needs KAILASHE_E2E=1 and real accounts; never run in CI. Contributing: CONTRIBUTING.md.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
MCP server for generating rough-draft project plans from natural-language prompts.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- AlicenseBqualityDmaintenanceProduction-ready TypeScript MCP server exposing utility, GitHub, and Microsoft Teams tools over stdio.141MIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.40 npmMIT
- AlicenseCqualityBmaintenanceProvides a deterministic MCP server that orchestrates projects across web, backend, games, AI, payments, fiscal, and infrastructure domains, with safe file writing, audit logging, and framework-aware context routing.88MIT

yotta-dev-mcpofficial
AlicenseNot gradedqualityBmaintenanceProvides deterministic local development tools over stdio MCP, including repository mapping, code review, secret and dependency scanning, release checks, whitelisted checks, scaffolding, and workflow state tracking.106 npmMIT