Same platform, from a terminal or an agent.
Install it with brew install xraph/tap/loomctl. loomctl does what the dashboard does, for terminals and CI. It runs on API keys that act as you, with your role, and can be read-only. loomctl mcp turns the same commands into tools an AI agent can use.
Let an agent plan. Decide whether it can deploy.
Make an API key under Settings, add loomctl mcp to your agent's configuration, and it can analyze, write a manifest and plan. Approving and retrying need --allow-deploy. A manifest that doesn't parse comes back with each problem and its line, so the agent can fix it and save again.
- The manifest schema is a resource the agent can read
- Secrets are set but never shown back
- Works with Claude Code:
claude mcp add loomplane -- loomctl mcp
{ "mcpServers": { "loomplane": { "command": "loomctl", "args": ["mcp"], "env": { "LOOMPLANE_URL": "https://loom.acme.dev", "LOOMPLANE_API_KEY": "lp_live_…" } } }}
What an agent can do.
| Tool | What it does |
|---|---|
whoami | Who the key acts as, and its permissions |
list_projects | The organization's projects |
analyze | Reads a project's repositories, or the ones named, and waits until each is done |
get_manifest, draft_manifest, save_manifest | Reads, drafts and saves loomplane.yaml |
create_plan, list_plans, get_plan, reject_plan | Plans an environment and reads the result, optionally scoped to some repositories |
list_deployments, get_deployment | Follows deployments step by step |
status | What runs where, with addresses and drift |
list_variables, set_variable | Variables, with secret values never shown |
approve_plan, retry_deployment | Only with --allow-deploy |
Plan on every merge. Approve where you review.
Run loomctl plan in CI so every merge produces a plan, and approve it from the dashboard or the terminal. Use a read-only key for status checks and a separate key for the people who approve.
on: push: { branches: [main] }jobs: plan: runs-on: ubuntu-latest steps: - run: echo "$LOOM_KEY" | loomctl login --url $LOOM_URL --key - - run: loomctl analyze mono - run: loomctl plan mono --env production
Deploy your monorepo to your own clouds this afternoon.
Open source and self-hosted. Your applications don't need Forge, or Go.
docker pull ghcr.io/xraph/loomplane:latestServerbrew install xraph/tap/loomctlCLI