· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →mittwald v1.0.0
Manage mittwald hosting
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.
From the marketplace listing
Manage your mittwald (mStudio) hosting infrastructure from ChatGPT. List and inspect projects, apps, servers and domains; provision and manage MySQL and Redis databases, users, backups and backup schedules; work with containers, stacks, cron jobs and volumes; configure domains, DNS zones, virtual hosts, SSL certificates and mail addresses; manage organization and project members, SSH users and keys, and API tokens. Read-only tools inspect resources, while write tools create, update or remove them on the authenticated user's behalf.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: mittwald-migrate description: Migrate an arbitrary application from an external platform to mittwald mStudio. Use when the user mentions "migrate to Mittwald", "Umzug nach Mittwald", "move to mStudio", "Container Hosting auf Mittwald", "stack_deploy", or asks for help moving a workload (K8s, Docker Compose, VPS, another hoster, another mStudio project) onto Mittwald. Source is open, target is always mStudio. --- # mittwald-migrate You are guiding an operator through a migration **to Mittwald mStudio**. The source can be anything (Kubernetes, Docker Compose, bare-metal/VPS, another hoster, another mStudio project) — the **target is always mStudio**. This skill is a workflow orchestrator: it routes to focused playbooks under `playbooks/` and pulls in shared references from `references/`. Do **not** inline the playbook content here — read them when the relevant phase begins. ## How to run this skill 1. **Detect available surfaces.** The skill can drive mStudio via MCP, the `mw` CLI, or the HTTP API — see [references/mittwald-surfaces.md](references/mittwald-surfaces.md). Probe in preference order: - **MCP** — check for `mcp__mittwald__mittwald_*` tools in this session. - **CLI** — `command -v mw && mw user get -o json` (logged-in check). - **API** — operator can supply an `MITTWALD_API_TOKEN`; spec at `https://api.mittwald.de/v2/openapi.json`. Pick the highest-preference one available and announce it. If **none** are available, stop and tell the operator: "No Mittwald surface (MCP, CLI, or API token) is available — I won't guess calls." Stay consistent within a phase; mixing surfaces mid-phase is fine only when one surface lacks a capability (e.g. MCP doesn't stream MySQL dumps — fall back to `mw database mysql dump`). 2. **Open with a phase plan.** Create a TodoWrite list with these six phases (mark only the first as in-progress): - Discovery — inventory the source - Plan — target shape, downtime budget, rollback - Provision — create project, stack, virtualhosts, domains - Migrate — move data (DBs, files, secrets) - Verify — smoke test against the default `<shortId>.project.space` domain - Cutover — DNS swap, decommission window 3. **Confirmation gates.** Before each destructive or externally-visible action, summarize what you're about to do and call `AskUserQuestion`. Never run `DROP`, `DELETE`, container/stack deletion, DNS changes, or anything that mutates the source without explicit approval **for that specific step**. 4. **Idempotency.** On every resume, re-check current state (`project_get`, `stack_list`, `stack_ps`, `domain_virtualhost_list`, `database_*_list`) before acting. A project may already exist; a DB may already have data. 5. **Always smoke-test on the default domain.** Every Mittwald stack gets a `<shortId>.project.space` address with a valid Let's Encrypt cert from the first virtualhost. Use it for verification **before** DNS cutover. 6. **Optional wrap-up — offer to contribute learnings.** When the migration reaches a natural end (Verify passed, Cutover done, or it was rolled back), you *may* offer to draft a short, **fully sanitized** GitHub issue summarizing the migration so the skill improves over time. Read [playbooks/contribute-learnings.md](playbooks/contribute-learnings.md). **Strictly opt-in** (default no, never nag), **no secrets or identifying details ever**, and the operator reviews the exact body before anything is filed. If declined, end silently. ## Phase routing | Phase | Playbook | When to read it | |---|---|---| | Discovery | [playbooks/discover-source.md](playbooks/discover-source.md) | First phase, always. Pulls source inventory regardless of source type. | | Plan + Provision | [playbooks/provision-target.md](playbooks/provision-target.md) | After Discovery is approved. Decides Managed-App vs Stack, lays out compose, creates project & virtualhosts. | | Migrate Postgres | [playbooks/migrate-postgres.md](playbooks/migrate-postgres.md) | If s
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 20 — file references are metadata, not package contents.
--- name: mittwald-zerodeploy description: Deploy an arbitrary application from your local machine or a Git repository to mittwald mStudio. Use when the user mentions "deploy to Mittwald", "move to mStudio", "Container Hosting auf Mittwald", "stack_deploy", or asks for help deploying a workload (K8s, Docker Compose, VPS, another hoster, another mStudio project) onto Mittwald. Source is open, target is always mStudio. --- # mittwald-zerodeploy Zero-config deployment to mittwald mStudio container hosting using Railpack build inference. --- ## Description This skill guides users through deploying containerized applications to mittwald mStudio **without requiring Docker knowledge**. The workflow uses Railpack to automatically detect project types and generate build plans, then deploys via the mittwald CLI or GitHub Actions. **Perfect for**: Developers who want to deploy quickly without writing Dockerfiles. **Not for**: DevOps teams needing explicit container definitions (use `deploy-container-action` instead). --- ## When to use this skill Trigger this skill when the user wants to: - Deploy an app to mittwald without writing a Dockerfile - Set up automated deployment with GitHub Actions to mittwald - Troubleshoot Railpack-based deployment failures - Transition from local CLI testing to CI/CD automation - Fix issues with faulty AI-generated Dockerfiles - Understand why their deployment isn't working --- ## Workflow ### Phase 1: Local Testing (CLI) **Goal**: Validate the deployment locally before setting up automation. 1. **Load** `playbooks/01-provision-target.md` - Verify mStudio project exists and user has API token - Confirm project ID is configured or can be passed explicitly - Check CLI is installed and authenticated 2. **Load** `playbooks/02-cli-deploy-local.md` - Run `mw experimental deploy` from project root - Handle environment variables via `--env` or `--env-file` - Parse deployment output for URL and container ID - Verify the app is reachable 3. **Load** `playbooks/05-verify.md` - Check container status in mStudio web UI - Test HTTP endpoints and validate responses - Confirm environment variables are applied correctly ### Phase 2: Automation (GitHub Actions) **Goal**: Set up continuous deployment after local testing succeeds. 1. **Load** `playbooks/03-setup-github-action.md` - Create `.github/workflows/zerodeploy.yml` - Configure GitHub secrets (`MITTWALD_API_TOKEN`, `MITTWALD_PROJECT_ID`) - Handle runtime secrets via workflow `.env` generation - Test with manual workflow dispatch 2. **Test automated deployment** - Trigger workflow manually - Monitor workflow logs for errors 3. **Load** `playbooks/05-verify.md` again - Confirm automated deployment produces same result as CLI ### Troubleshooting (As Needed) **When deployment fails or behaves unexpectedly:** - **Load** `playbooks/04-troubleshoot-deployment.md` - Guide user to mStudio web UI logs - Identify common error patterns - Check for faulty Dockerfiles to delete - Reconfigure ports if needed **When encountering the 3 critical gotchas:** - **Load** `references/pitfalls.md` - Faulty pre-existing Dockerfiles - Hidden port configurations - Exotic projects that won't work with Railpack **When stuck after 2-3 attempts:** - **Load** `references/when-to-escalate.md` - Recognize escalation triggers - Document errors for handoff - Avoid endless iteration --- ## Critical References (Load on Demand) ### Build & Detection Issues - `references/railpack-overview.md` - when Railpack can't detect project type or build fails ### Configuration Issues - `references/secrets-management.md` - when handling API keys, database passwords, or `.env` files - `references/port-configuration.md` - when app won't respond on expected port or ingress issues occur ### Failure Patterns - `references/pitfalls.md` - the 3 most common gotchas with solutions - `references/when-to-escalate.md` - whe
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 11 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugin_asdk_app_6a68b368b8588191afee9a7e2b327d63
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.