run.zero
OnlineNewDeploy apps, APIs and Postgres from your AI agent. EU PaaS hosted in Germany, OAuth sign-in.
What it can do: 53 tools
runzero_get_helpread-onlyLook up structured guidance on platform concepts and conventions. Topics: workflow, files, addons, procfile, domains. Call this whenever you need to understand addons, the Procfile/PORT convention, or the typical workflorunzero_list_appsread-onlyList the apps the authenticated user has access to (own + collaborated), newest first — one compact row each (name, slug, url, kind, status, flags). Details of one app: runzero_get_app.runzero_get_appread-onlyGet one app: slug, status, publish mode, services (URL, replicas, health, env var NAMES), addons, domains. Secret values are never returned.runzero_create_appCreate a new app. Optionally links to a Git repository — if no repo is given, you can attach one later.runzero_list_templatesread-onlyList the curated template library: finished, deployed page designs (landing pages, shops, portfolios …) that can be adopted as the starting point of a NEW app instead of building from scratch. Each entry has a live URL arunzero_adopt_templateCreate a NEW app as a full copy of a template from runzero_list_templates: app + repo + running instance, owned by the caller. Use this INSTEAD of runzero_create_app when a template matches the request, then adapt the corunzero_list_servicesread-onlyList the services (runtime processes) of an app with their build source, port, replicas and status.runzero_get_logsread-onlyGet the runtime log output of one service (stdout/stderr of its running containers), last N lines.runzero_get_metricsread-onlyCPU and memory usage of a service over a time window (default last hour). Returns per-pod current/min/max/avg — CPU in millicores, memory in MiB — not raw time series, to stay compact.runzero_screenshotread-onlySEE the deployed page with your own eyes: renders the live URL in a real browser and returns fresh screenshots as images — desktop (1280×800) and/or mobile (390×844). Use it after runzero_wait_for_build to review the visrunzero_rebuild_serviceRebuild a service from the latest commit of its repo branch; on success the new version rolls out to the live URL. Use after an external repo changed; pushes via runzero_push_files rebuild on their own.runzero_delete_appPermanently delete an app with all its services, addons (including database data), secrets and domains. Irreversible: only on an explicit request, and name the app back to the user before calling.runzero_deployDeploy an app. Fetches the repo and checks for run-zero.yaml (or the older itdone.yaml). If found, syncs all services + addons + domains from config. If not, deploys the repo as a single service. Services missing from thrunzero_deploy_previewread-onlyPreview what a deploy would change without making any changes. Use this before runzero_deploy to verify the diff.runzero_add_serviceAdd a new service to an app. Clones the repo, builds with buildpacks, and deploys. The web process must listen on $PORT.runzero_delete_servicePermanently delete one service of an app: its running containers, its public URL and its configuration. Irreversible, and it also deletes the persistent volume of the service with all its backups; to only stop it, scalerunzero_scale_serviceSet the replica count of a service (0-10). Scaling to 0 takes the service offline (its URL stops answering) without deleting it; scale up again to bring it back. A service with a persistent volume runs 0 or 1 replicas anrunzero_volume_statusread-onlyShow the persistent volume of a service: mount path, size, last backup, the backups that can be restored, and the state of a running or last restore or import. Volumes are declared under `volumes:` in run-zero.yaml (runzrunzero_backup_volumeStart a backup of the persistent volume now, on top of the automatic daily one. The service keeps running. It runs in the background; runzero_volume_status lists it once it is finished.runzero_restore_volumeReplace the data on the persistent volume with a backup. The service stops, the current data is backed up first, the backup is unpacked, and the service starts again. Takes minutes; follow it with runzero_volume_status (runzero_volume_import_linkStep 1 of moving existing data (an SQLite file, a pb_data folder) onto the persistent volume of a service. Returns a dashboard page where the USER drops the file, and a one-hour upload link with a ready curl command forrunzero_import_volumeStep 2: put an uploaded file (runzero_volume_import_link) onto the persistent volume. The service stops, the current data is backed up first, the file is placed, and the service starts again. Existing data is only replacrunzero_set_secretsSet one or more environment variables for an app or a specific service. Existing keys are overwritten; other keys are preserved. Affected services are redeployed automatically.runzero_list_secretsread-onlyList the secret keys for an app (values are never returned). Includes both app-wide and per-service secrets.runzero_delete_secretDelete a single secret from an app or a service. Affected services are redeployed automatically.runzero_list_buildsread-onlyList recent build records for an app. Returns kpack Build status (success/failed/running) per service. To WAIT for a build to finish, use runzero_wait_for_build instead of calling this in a loop.runzero_list_versionsread-onlyEarlier versions of a service that can be put back online, newest first. Each entry has an `image` (pass it to runzero_activate_version or runzero_preview_version), when it was built, and `summary` — the commit message,runzero_preview_versionShow an earlier version under a SECOND address without touching the live site — use this whenever the user wants to look before deciding. Returns a url; the pod needs a few seconds, so a first request may fail — retry onrunzero_work_urlThe URL where this app's UNPUBLISHED changes can be looked at, and a link that opens it (the plain hostname refuses without one). Call this after EVERY change to an app that publishes on request, and give the user the lirunzero_list_releasesread-onlyWhat the user has PUBLISHED, newest first, with the sentence they described each change with, and which one visitors see right now. This is the list to use when someone says "wie letzte Woche" or "vor der Umgestaltung" —runzero_publishPut the waiting changes on the real site — this is what VISITORS see, so only ever on an explicit request ("mach das live", "veröffentliche das"), never on your own initiative after finishing a change. Write `descriptionrunzero_restore_releasePut an earlier published state back on the real site. Use the id from runzero_list_releases. This CHANGES what visitors see. It does not touch the code: anything changed since is still there and still waiting, so this unrunzero_set_publish_modeSwitch between publishing every change immediately (auto) and collecting changes on a preview until the user releases them (manual). Explain the consequence before switching to manual: from then on nothing reaches theirrunzero_activate_versionPut an earlier version back online — this CHANGES what visitors see. Only do this when the user explicitly asks to go back; never on your own initiative after a failed build (fix the code instead). While an older versionrunzero_wait_for_buildread-onlyWait server-side until the newest build of an app is finished AND the new version is serving traffic — use this INSTEAD of polling runzero_list_builds, sleeping, or re-checking the site in a loop. Blocks up to 45 secondsrunzero_get_build_logsread-onlyGet the full log stream for a specific build (all kpack steps concatenated). Use runzero_list_builds first to find the build id.runzero_push_filesPush changes into the app's Git repository as ONE atomic commit (create, patch, and delete in a single push). CHANGING an existing file? Use `edits` — an exact-snippet replacement, like your editor's edit tool. Use `filerunzero_list_filesread-onlyList all files in the app's Git repository (platform-managed repos only). Optionally filter by path prefix.runzero_read_fileread-onlyRead a file from the app's Git repository (platform-managed repos only), UTF-8. Returns at most 250 lines per call (a note at the end says how to continue) — read the part you need with startLine/endLine instead of the wrunzero_upload_assetsread-onlyGet the dashboard upload link for an app so the USER can upload binary assets (icons, images, fonts) via drag & drop — real bytes, nothing travels through the model. Give the returned URL to the user, wait until they con
…and 13 more.
Connect it
claude mcp add --transport http run-zero https://api.run-zero.de/mcpSettings → Connectors → Add custom connector
URL: https://api.run-zero.de/mcp{
"mcpServers": {
"run-zero": {
"url": "https://api.run-zero.de/mcp"
}
}
}{
"servers": {
"run-zero": {
"type": "http",
"url": "https://api.run-zero.de/mcp"
}
}
}Questions
What does run.zero do?
Deploy apps, APIs and Postgres from your AI agent. EU PaaS hosted in Germany, OAuth sign-in. It exposes 53 tools to AI assistants.
What tools does run.zero provide?
53 tools, including runzero_get_help, runzero_list_apps, runzero_get_app, runzero_create_app, runzero_list_templates, runzero_adopt_template, runzero_list_services, runzero_get_logs, runzero_get_metrics, runzero_screenshot, runzero_rebuild_service, runzero_delete_app….
How do I connect run.zero to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://api.run-zero.de/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does run.zero require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is run.zero online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes run.zero?
run-zero.de. The official MCP Registry verified that the publisher controls this domain before accepting the listing.
Similar in Cloud & DevOps
-
CloudflareOnlineOfficialPopular
Cloudflare MCP servers
-
Google ComputeOnlineOfficialPopular
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
-
Google ContainerOnlineOfficialPopular
Provides read access to your GKE and Kubernetes resources.
-
Google ComposerOnlineOfficialPopular
Interact with your Google Cloud Composer resources using natural language commands.
-
Google BigtableadminOnlineOfficialPopular
Interact with your Google Bigtable resources using natural language commands.
-
Google DatastreamOnlineOfficialPopular
Interact with your Google Cloud Datastream resources using natural language commands.