curl -LsSf https://get.modmon.org/install.sh | shmm builds your containers, resolves environments and secrets, serves trusted local HTTPS, and deploys from a plan you review first. On Docker Compose, Podman Compose, and Docker Swarm.
This terminal is interactive. Click it, then press3jenterl2?
mm agent setup connects Claude Code, OpenCode, Codex, or Cursor to mm's MCP server. An agent can deploy and run commands in local, restart jobs in staging, and only read status and logs in production.
The agents block in .config/mm.yaml gives each environment a level and, separately, exec. It takes effect only after you trust it on your machine, and again after every edit.
A call outside the grant changes nothing. It returns the exact mm command, and the agent asks you to run it in your own terminal.
An agent connects with its own key and gets only what the deployed commit allows, whatever a checkout says.
mm refuses to run inside a coding tool's shell, and every call that names an environment is written to the local audit journal.
localstagingproductionmm --environment production service exec api -- rails db:migrateKeep container commands, health checks, and volumes in Compose. mm adds what a monorepo needs around them, and shows you each change before it happens.
Builds, deployments, and shared services each produce a plan and print its hash. Apply takes the hash of the plan you reviewed. If the config, a secret, or the target moved in between, mm stops and asks you to plan again.
How plans work Wildcard .test DNS and a local certificate authority your machine trusts. Every routed service gets a hostname. No hosts-file entries, no browser warnings.
Config holds references. Values live in a separate store: local, OpenBao, or Vault. Plans include the reference and never the value.
Image repositories, environments, secret references, and routes go in one file next to them. Commands, health checks, and volumes stay in Compose.
modules:
backend:
path: backend
build:
image: ghcr.io/acme/api
services:
api: { stack: app, role: http }What goes whereThe same project runs on Docker Compose, Podman Compose, or Docker Swarm across nodes. Remote hosts run a small daemon and deploy exactly what is committed.
Declare migrations, cleanups, and recurring work next to your services. Run, retry, and cancel them from the CLI or the terminal interface.
mm dev dashboardA local web dashboard shows status across projects, and Mailpit catches every email your services send in development.
mm dev mountsDevelopment mounts map module source into running containers, with presets that keep dependencies and protected files out of the way.
The installer fetches a verified release and puts mm on your machine. Workstation setup is a separate step that shows its plan and asks before it changes anything.
curl --proto '=https' --tlsv1.2 -LsSf https://get.modmon.org/install.sh | shmm dev setup# local trust, ingress, dashboard, Mailpitmm# open the guided interfacex86-64 or ARM64