# Dockhold MCP server

Deploy a GitHub repo to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.

## Links
- Registry page: https://www.getdrio.com/mcp/eu-dockhold-dockhold
- Website: https://dockhold.eu

## Install
- Endpoint: https://api.dockhold.eu/mcp
- Auth: Auth required by registry metadata

## Setup notes
- Remote header: Authorization (required; secret)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://api.dockhold.eu/mcp
- Header: Authorization

## Tools
- list_apps (List apps) - List the apps in your Dockhold account, with each app's id, status, URL, and source repo. Call this first whenever the user asks about their apps, or when you need an app_id for any other tool. Endpoint: https://api.dockhold.eu/mcp
- get_app_status (Get app status) - Get detailed status for one app: deploy status, URL, last deployed commit, and any error message. Call this to check whether a deploy has finished, to get an app's live URL, or to see why an app is in error. Endpoint: https://api.dockhold.eu/mcp
- get_app_logs (Get app logs) - Get the most recent runtime logs for one app. Call this when an app is crashing, returning errors, or a deploy succeeded but the app misbehaves: the logs usually name the cause. Endpoint: https://api.dockhold.eu/mcp
- deploy_app (Deploy an app) - Deploy a GitHub repository as a live web app on Dockhold. Call this when the user wants to put an app online, get a shareable HTTPS URL, or host a demo. Returns the new app id. Two paths: a PUBLIC repo needs only repo_url; a PRIVATE repo needs repo_url plus github_installation_id (call list_github_repos first, each repo comes with the installation_id to pass here). Deploying a private repo turns on auto-deploy: future pushes to that repo redeploy the app automatically. The app builds and comes online automatically; poll get_app_status to watch it. This tool needs a GitHub repo URL: if the code only exists locally (no repo), it cannot be used here, and the user should run `npx dockhold login` then `npx dockhold deploy` in the project folder instead. Requires a token with the deploy scope. Endpoint: https://api.dockhold.eu/mcp
- redeploy_app (Restart an app) - Restart an existing app (rolling restart with zero downtime). Call this after changing configuration, or to recover an app that is stuck or misbehaving. It reruns the current build; it does not pull new code. Endpoint: https://api.dockhold.eu/mcp
- set_app_variable (Set an app variable) - Set a single environment variable on an app and roll it out. Call this when an app needs plain configuration such as LOG_LEVEL or a feature flag. For secrets (API keys, passwords, tokens) use the Secrets section of the Dockhold dashboard instead: this tool rejects secret-looking keys. Endpoint: https://api.dockhold.eu/mcp
- get_resource_usage (Show resource usage) - Show your account's compute, database-RAM, and storage pools: how much you've bought, how much is used, and how much is free, plus every app's current size. Call this before any resize tool (the allowed sizes come from its steps fields), and to explain to the user why an app ran out of memory or a deploy was refused for capacity. Endpoint: https://api.dockhold.eu/mcp
- resize_app (Resize app memory) - Change how much memory one app gets. Call this when an app is running out of memory (OOM) or the user asks to make an app bigger or smaller. memory_mb must be one of the sizes get_resource_usage reports under compute.steps_mb, and the new size has to fit your available compute pool (call get_resource_usage first). Applied with a zero-downtime rolling update. Endpoint: https://api.dockhold.eu/mcp
- resize_database (Resize database memory) - Change how much memory an app's managed database gets. Call this when the database is slow or out of memory. db_ram_mb must be one of the sizes get_resource_usage reports under db_ram.steps_mb and fit your database-RAM pool. WARNING: the database restarts briefly to apply the new size, so the app loses its database connection for a few seconds. Only works if the app has a managed database. Endpoint: https://api.dockhold.eu/mcp
- resize_database_storage (Grow database storage) - Grow the disk of an app's managed database. Call this when the database is running out of disk space. GROW-ONLY: you can increase storage but never shrink it. storage_gb must be one of the sizes get_resource_usage reports under storage.steps_gb and fit your storage pool. Applied online with no database restart. Only works if the app has a managed database. Endpoint: https://api.dockhold.eu/mcp
- list_github_repos (List connected GitHub repos) - List the GitHub repositories you have connected to Dockhold, across every installation. Call this before deploy_app when the target repo is private, or when the user asks which repos they can deploy. Each repo comes with its installation_id: pass that (with the repo's clone URL) to deploy_app to deploy a PRIVATE repository. Public repos don't need it. Endpoint: https://api.dockhold.eu/mcp
- deploy_group (Deploy a service group) - Deploy several connected services in one go (e.g. a frontend + an API). Call this when the user's project is split across multiple repos that must talk to each other; for a single repo use deploy_app. Each service is a public GitHub repo that gets its own URL. Wire them by setting an env var to the exact token ${services.<otherServiceName>.url} — Dockhold injects that service's live URL once it deploys. Give the backend its own database with "db":"enable" (DATABASE_URL is injected; a pure frontend doesn't need one). Builds run in parallel; poll get_app_status with each returned app_id. Endpoint: https://api.dockhold.eu/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: eu.dockhold
- Version: 0.1.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jul 5, 2026
- Source: https://registry.modelcontextprotocol.io