krexel-mcp
This MCP server lets AI assistants deploy, inspect, edit, and manage live static websites via the Krexel hosting platform. Key capabilities include:
Deploy a site (
ship_site): Upload a local build folder to a custom domain. Supports framework hints (Next.js, Astro, Vite, static) and returns adeploy_idand preview URL.List deployments (
list_deploys): View recent deploys from local state, optionally filtered by domain.Rollback (
rollback): Mark a previous deploy as the current good version for a domain.Inspect deploy logs (
get_logs): Retrieve build logs for a specific deploy.List files (
list_files): Get metadata (paths, sizes, SHA256 hashes) for all files in a deployed site.Read a file (
read_file): Fetch the full content of a specific file from a deployed site.Edit a file (
edit_file): Patch a live site usingcreate,replace,replace_all, ordeleteoperations. Changes go live in ~8 seconds as a lightweight patch deploy.Set environment variables (
set_env): Encrypt and persist env vars for a domain using AES-256-GCM encryption.Check account status (
get_status): View account info, deploy count, plan, platform, and state directory.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@krexel-mcp Deploy my new site from the ./dist folder"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
krexel-mcp
Ship AND edit static sites from any AI assistant that speaks the Model Context Protocol.
krexel-mcp is the official MCP server for
Krexel — a "your AI ships and edits your live site"
API. Point any MCP-compatible client (Claude Desktop, Cursor, Windsurf,
VS Code) at this server and your assistant can deploy, list, edit,
rollback, and inspect sites just by talking.
Quickstart
Add krexel-mcp to your MCP client configuration:
{
"mcpServers": {
"krexel": {
"command": "npx",
"args": ["-y", "krexel-mcp"],
"env": {
"KREXEL_API_URL": "https://api.krexel.com",
"KREXEL_API_KEY": "krx_live_••••••••••••••••",
"KREXEL_MASTER_KEY": "<your-32-byte-hex-key>"
}
}
}
}Restart your client. The assistant now sees nine Krexel tools.
Related MCP server: StaticX MCP Server
Tools
Tool | What it does |
| Upload a built site folder. Returns a |
| Patch a deployed site (create / replace / replace_all / delete). 0.1 deploy. |
| List the files in a deployed site (path + size + sha256). |
| Read one file's content from a deployed site. |
| List recent deploys from local state. Optional domain filter. |
| Fetch build logs for a deploy. |
| Mark a previous deploy as the current good version. |
| Encrypt and persist an env var for a domain (AES-256-GCM). |
| Return account, deploy count, plan, and state directory. |
The conversational-edit flow
AI calls
list_files(deploy_id)to see what files exist on the site.AI calls
read_file(deploy_id, path)to read the file it wants to change.AI generates the new content itself, then calls
edit_file(deploy_id, op: "replace", file, find, value, message).Krexel ships the patch as a new deploy — live in ~8 seconds, 0.1 deploy against the customer's quota. The new
deploy_idandparent_deploy_idare returned so the AI can chain further edits on top.
The AI is the brain. Krexel is the hands.
All tools take plain JSON arguments and return JSON. Tool schemas are
discoverable via the standard MCP tools/list request.
Configuration
Env var | Required | Default | Notes |
| no |
| Base URL of the Krexel orchestrator API. |
| no* |
| Account API key. Forwarded as |
| yes* | — | 32-byte hex string for env-var encryption. *Required for |
State files are written under $KREXEL_HOME (default ~/.krexel/).
License
MIT © Syfer
Available Tools
9 toolsedit_fileA
Patch a file on a live deployed site and ship a new patch deploy. The AI decides what to change; the MCP ships the patch. Returns the new deploy_id + preview_url.
Inputs: op (required), file (required), deploy_id (required), find, +3 more.
get_logsA
Get build logs for a deploy. In Phase 1 these are mocked from the local manifest; Phase 2 will stream from the orchestrator.
Inputs: deploy_id (required).
get_statusA
Return current account, deploy count, platform, and state directory.
Inputs: no named parameters.
list_deploysB
List recent deploys from the local Krexel state file. Optionally filter by domain.
Inputs: limit, domain.
list_filesA
List the files in a deployed site (paths, sizes, sha256). Returns metadata only — use read_file to fetch content.
Inputs: deploy_id (required).
read_fileA
Read a single file's contents from a deployed site. Path is relative to the site root (e.g. 'index.html', 'assets/logo.svg').
Inputs: path (required), deploy_id (required).
rollbackA
Mark a previous deploy as the current 'last_good' for a domain. Phase 2 will actually push the rollback; Phase 1 just records intent.
Inputs: to (required), domain (required).
set_envA
Encrypt and persist an environment variable for a domain. Stored at $KREXEL_HOME/env/.enc with AES-256-GCM using KREXEL_MASTER_KEY.
Inputs: key (required), value (required), domain (required).
ship_siteA
Upload a built site folder to Krexel. Zips the folder, stages it locally, and POSTs to the Krexel orchestrator API. Returns a deploy_id (always) and preview_url. If the orchestrator is unreachable the response carries an api_ok: false flag with the upstream error — never fakes success.
Inputs: domain (required), folder (required), framework.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool serves a distinct purpose: editing files, getting logs, status, listing deploys, listing files, reading files, rolling back, setting env vars, and shipping sites. No two tools have overlapping responsibilities, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., edit_file, get_logs, list_deploys). Even 'rollback' is a clear single verb. No mixing of conventions or styles.
With 9 tools, the server covers the core deployment lifecycle without being overwhelming. The count is well-scoped for a focused platform like Krexel, allowing efficient agent interaction.
The tool set covers primary deployment operations: create (ship_site, edit_file), read (list_deploys, get_logs, get_status, list_files, read_file), update (edit_file, set_env), and delete (implied via rollback). Minor gaps like explicit env variable listing or deploy deletion are absent but not critical for basic workflows.
Maintenance
Related MCP Connectors
Deploy sites and apps from your AI coding agent: domains, DNS, logs, env, versions and rollback.
Deploy your project to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
Deploy and manage static websites on FluxHost directly from your AI assistant.
Deploy and manage Jade Hosting projects from AI clients. Jade account and OAuth required.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to deploy static websites to the Demox platform with automatic directory packaging and cloud storage integration. It includes tools for managing deployments, such as listing, viewing, and deleting websites.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to deploy static websites to StaticX, including creating sites, uploading builds, publishing releases, and managing domains.23 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to deploy generated files (HTML, PDF, images, etc.) directly to cloud71 hosting, returning a public URL, and manage cloud71 sites via natural language.MIT
- FlicenseBqualityCmaintenanceEnables deploying sites, managing databases, and troubleshooting deployments on Hostwares from AI assistants.14-