Zordon is a supervisor for local development stacks that runs databases, brokers, proxies, and other services as supervised host processes instead of containers. It uses an Alphasfile manifest to declare, start, inspect, and provision the stack, and can expose those actions through an MCP server.
From the registry: Supervise a local dev stack — databases, brokers and services declared in an Alphasfile — over MCP.
$ brew install piotrkowalczuk/tap/zordonPlease install the `zordon` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Zordon binaries** — Install Zordon so the `zordon` command is available on your PATH. Homebrew on macOS is the simplest documented path. Run: `brew install piotrkowalczuk/tap/zordon`
- **Keep companion binaries together on PATH** — Zordon installs three binaries: `zordon`, `alpha`, and `tommy`. Keep them in one directory and ensure that directory is on your PATH, because `zordon` finds `alpha` via PATH and `alpha` finds `tommy` as a sibling executable. (docs/reference/binaries.md)
- **Have a project with an Alphasfile** — The MCP server resolves the stack chain from the client's working directory, so use it from within a project tree containing an `Alphasfile` (or equivalent zordon-managed chain). (docs/alphasfile.md)
Canonical MCP server config (stdio transport):
- command: `zordon`
- args: ["mcp"]
- optional environment variables:
- `ZORDON_HOME`: Optional override for the directory Zordon resolves from if the MCP client is not launched from the project tree. (example: `<your-zordon-home-path>`)
Note: Run the MCP client from the project directory so Zordon can resolve the chain from the working directory. The README notes that provisions run inside the live `alpha`, so the stack should be started first (for example with `zordon start`) or via the exposed MCP tools.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.