Kranz MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| runtimesA | List the Kranz project runtimes visible to this user. Read this first when a call answers runtime_required or runtime_not_found: every entry can be passed back as the runtime argument. |
| upA | Start the runtime of a project that has none, without starting any service. This creates a background process that outlives this MCP session and stays in kranz ps until someone stops it; use it only when asked to bring a project up. |
| downA | Stop a runtime this MCP session started with up. Runtimes started by a person are never stopped from here. |
| statusC | Return live status for selected services, including the structured cause of a state whose reason is not the state itself. |
| runsB | Return the bounded service and action run catalog with provenance and output retention state. |
| run_deleteA | Delete one completed absolute service or action run and its retained output after explicit confirmation. |
| changesB | Return what changed in the runtime after a cursor: service and action transitions, detected-port changes, and configuration reloads. |
| planA | Resolve a versioned start, stop, restart, or action plan without executing it. A parameterized action takes the same typed params object action_run takes, and the plan carries the exact command it would run. |
| graphB | Return the declared dependency, prerequisite, and ownership graph with live service state folded in. |
| portsB | Inspect declared and detected service ports without changing their owners. |
| port_inspectB | Identify the current listener on explicit port numbers, including processes Kranz does not manage. |
| logsC | Query bounded normalized service and action logs. |
| waitC | Wait cancellably for ready, running, stopped, healthy, or unhealthy. |
| healthB | Return readiness and liveness probe state, including the probed target and its last error, with recorded health history. |
| action_listB | List actions, optionally filtered by exact owner. |
| action_infoC | Describe one exact OWNER/ACTION. |
| action_resultC | Return a current or retained action result by absolute or negative-relative run. |
| doctorA | Run project preflight checks: configuration diagnostics, dependency cycles, service directories, env files, shells, and declared ports. |
| startC | Start selected services using the resolved application plan. |
| stopB | Stop selected services and affected dependents using the resolved application plan. |
| restartB | Restart selected services and affected dependents using the resolved application plan. |
| action_runA | Run one non-interactive action. Pass a typed params object for a parameterized action; action_info returns its advisory schema. MCP request cancellation does not cancel the action. |
| action_cancelC | Explicitly cancel a currently running non-interactive action. |
| logs_clearC | Clear explicitly selected bounded service/action log buffers. |
| reloadA | Re-read the configuration from disk and reconcile it into the running services. Use it after editing a Kranz configuration file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| runtimes | Registry sessions visible to this user. Global: it is the discovery primitive an unbound client reads first. |
| capabilities | Explicit Kranz MCP allow-list, addressing mode, and unavailable unsafe operations. |
| session | Identity, protocol, and generation of the runtime this read resolved to. |
| config | Effective config and provenance paths with secret-like environment values redacted. |
| services | Declared services and their live runtime snapshots. |
| actions | Service and project actions in declaration order. |
| runs | Bounded service and action run summaries with provenance and retention state. |
| graph | Nodes for services, action groups, and actions, with dependency, prerequisite, and ownership edges. |
| tags | The shared service/tag selector index. |
TDQS
Scored across 25 tools
Each tool targets a distinct operational concept (runtime lifecycle vs service lifecycle vs actions vs logs), and descriptions clarify edge cases like up/down vs start/stop. Some adjacent tools (ports vs port_inspect, status vs health vs wait, runs vs action_result) could be initially confused but are distinguishable on reading.
Names mix bare nouns (runtimes, status, logs), bare verbs (up, start, reload), and snake_case with resource prefixes (action_list, run_delete, logs_clear). The action_* family is consistent, but overall there is no single predictable verb_noun pattern. Still readable.
25 tools is heavy for an MCP surface, but the domain spans runtime, services, actions, logs, ports, health, and configuration, so most tools correspond to real operations. Borderline over-scoped rather than redundant.
Operational lifecycle is well covered: runtime up/down, service start/stop/restart/status/health/wait, action run/cancel/result, logs query/clear, plan, graph, ports, doctor, reload, and run deletion. Missing are config-editing operations and possibly service-level env/secret management, but these may be out of scope.