krexel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KREXEL_API_URL | No | Base URL of the Krexel orchestrator API. | http://localhost:8787 |
| KREXEL_MASTER_KEY | No | 32-byte hex string for env-var encryption. Required for set_env tool. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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 |
| list_deploysB | List recent deploys from the local Krexel state file. Optionally filter by domain. |
| 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. |
| 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. |
| 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. |
| get_statusA | Return current account, deploy count, platform, and state directory. |
| list_filesA | List the files in a deployed site (paths, sizes, sha256). Returns metadata only — use read_file to fetch content. |
| 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'). |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.