# kranz-org/kranz [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/kranz-org/kranz  
**GitHub Stars:** 61  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/kranz-org-kranz

## Description
Local service orchestrator with a stdio MCP server for inspecting and controlling development services, logs, ports, actions and run history across live project runtimes.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What kranz-org/kranz does

The kranz-org/kranz MCP server connects coding agents to local development runtimes managed by Kranz. It gives an agent access to the same operational view used by Kranz’s terminal UI and command-line interface rather than creating an independent copy of the project stack.

Through MCP, an agent can inspect services, check readiness and runtime ports, read bounded logs, invoke configured actions, and review numbered service or action runs. These operations are useful when an agent needs to diagnose a local application, restart a service, run a project action, or verify that a dependency is ready.

Kranz is part of the Developer Tools category and is intended for processes that would otherwise be spread across terminal tabs. It can be used alongside Docker Compose when containers remain the appropriate place to run infrastructure.

## How it works

Each project runtime has its own user-level supervisor. The TUI, CLI, and MCP act as clients of that supervisor, so a change made through one interface is reflected in the others. An attached coding agent shares the existing runtime and does not own its lifecycle; disconnecting the agent does not stop the project stack.

The MCP process runs over stdio with the command `kranz mcp`. It does not take a project at registration time. Instead, each request identifies the runtime to use, allowing one global MCP registration to cover multiple projects. Connecting to the server creates no runtime or second stack.

The server uses Kranz’s existing application operations and contracts for resources, tools, cursors, confirmations, and errors. The exact project configuration determines which services and actions are available.

## Setup and configuration

Install Kranz on macOS or Linux with Homebrew:

```bash
brew install kranz-org/tap/kranz
```

Alternatively, install it with Go 1.26 or newer:

```bash
go install github.com/kranz-org/kranz/cmd/kranz@latest
```

After the binary is available on the client’s PATH, register `kranz mcp` as a stdio MCP server. The README describes this as a one-time global registration. No environment variables or project argument are documented for starting the MCP process.

Claude Code users can install the repository’s Kranz plugin after installing the binary:

```bash
claude plugin marketplace add kranz-org/kranz
claude plugin install kranz@kranz
```

The standalone agent skill is also available for Codex, OpenCode, and other clients that support Agent Skills. OpenCode is not listed as a separately supported client in this directory’s client vocabulary.

## Tools and capabilities

The kranz-org/kranz MCP server supports agent access to:

- Live service state and runtime selection
- Readiness information and runtime port discovery
- Bounded service logs
- Configured service actions and project action groups
- Numbered service and action run history
- Shared runtime state also visible in the TUI and CLI

The underlying Kranz runtime can manage dependency-aware startup and shutdown, health checks, process recovery, detached resources, and typed action parameters. Whether a particular operation is available through MCP depends on the configured runtime and its actions.

## Limitations and notes

This is a local-runtime control interface, not a remote hosting service. It attaches to runtimes already managed by Kranz and does not itself start a project when the MCP connection is created. The MCP server also does not replace the Kranz supervisor; the supervisor remains responsible for each project runtime.

The README documents installation for macOS and Linux. It does not provide a list of environment variables for MCP operation. For exact request, confirmation, cursor, resource, and error behavior, consult Kranz’s MCP reference documentation.

_Full upstream README: https://allmcps.com/mcp/kranz-org-kranz/readme_