Skip to main content
Glama
krexel-mcp
by Syfer-web

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

ship_site

Upload a built site folder. Returns a deploy_id and preview URL.

edit_file

Patch a deployed site (create / replace / replace_all / delete). 0.1 deploy.

list_files

List the files in a deployed site (path + size + sha256).

read_file

Read one file's content from a deployed site.

list_deploys

List recent deploys from local state. Optional domain filter.

get_logs

Fetch build logs for a deploy.

rollback

Mark a previous deploy as the current good version.

set_env

Encrypt and persist an env var for a domain (AES-256-GCM).

get_status

Return account, deploy count, plan, and state directory.

The conversational-edit flow

  1. AI calls list_files(deploy_id) to see what files exist on the site.

  2. AI calls read_file(deploy_id, path) to read the file it wants to change.

  3. AI generates the new content itself, then calls edit_file(deploy_id, op: "replace", file, find, value, message).

  4. Krexel ships the patch as a new deploy — live in ~8 seconds, 0.1 deploy against the customer's quota. The new deploy_id and parent_deploy_id are 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

KREXEL_API_URL

no

https://api.krexel.com

Base URL of the Krexel orchestrator API.

KREXEL_API_KEY

no*

~/.krexel/auth.json

Account API key. Forwarded as Authorization: Bearer *** to every API call. *Required unless saved by krexel login.

KREXEL_MASTER_KEY

yes*

—

32-byte hex string for env-var encryption. *Required for set_env.

State files are written under $KREXEL_HOME (default ~/.krexel/).

License

MIT © Syfer

Available Tools

9 tools
edit_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

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers