InfraOps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token | |
| HETZNER_API_TOKEN | No | API token for Hetzner Cloud | |
| NAMECHEAP_API_KEY | No | API key for Namecheap | |
| NAMECHEAP_API_USER | No | Username for Namecheap API | |
| CLOUDFLARE_API_TOKEN | No | API token for Cloudflare | |
| CLOUDFLARE_ACCOUNT_ID | No | Account ID for Cloudflare | |
| COOLIFY_PROD_BASE_URL | No | Base URL of the Coolify production instance | |
| NAMECHEAP_PROXY_TOKEN | No | Proxy token for Namecheap | |
| SUPABASE_ACCESS_TOKEN | No | Access token for Supabase | |
| COOLIFY_PROD_API_TOKEN | No | API token for Coolify |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| coolify_list_projectsB | List all projects in the Coolify instance. Projects are the top-level organisational unit — each contains environments which in turn contain applications, databases, and services. |
| coolify_get_projectA | Get full details for a single project by UUID, including its environments and the resources within them. |
| coolify_create_projectA | Create a new project. After creation, add environments to it, then deploy applications/databases/services into those environments. |
| coolify_update_projectB | Update a project's name or description. |
| coolify_delete_projectA | Delete a project by UUID. WARNING: This will delete all environments and resources within the project. |
| coolify_list_environmentsA | List all environments within a project. Environments separate resources (e.g. production vs staging). |
| coolify_create_environmentA | Create a new environment within a project (e.g. 'production', 'staging', 'preview'). |
| coolify_delete_environmentA | Delete an environment from a project. WARNING: All resources in this environment will be removed. |
| coolify_list_applicationsA | List all applications across the Coolify instance. Returns a compact summary (uuid, name, status, fqdn, git) by default — pass summary:false for full objects. |
| coolify_get_applicationA | Get full details for a single application by UUID, including build config, health check settings, Git info, and deployment status. Webhook/basic-auth secrets are masked unless reveal:true. |
| coolify_create_application_publicA | Create an application from a public Git repository. You can deploy any kind of public repo from supported Git providers. For Devon's Flavor A apps (Coolify source build). |
| coolify_create_application_dockerimageA | Create an application from any Docker registry without Git. This is the standard pattern for Devon's Flavor B/C apps: GitHub Actions builds → pushes to ghcr.io/alobarquest/ → Coolify pulls. |
| coolify_create_application_dockerfileA | Create an application from a Dockerfile without Git. You can deploy a simple Dockerfile by providing its content directly. |
| coolify_create_application_deploykeyA | Create an application from a private Git repository with a deploy key. You can deploy private repos with a deploy key. Requires a private key already stored in Coolify (via coolify_create_private_key) and the public key added to GitHub (via github_add_deploy_key). |
| coolify_create_application_githubappA | Create an application from a private Git repository using a GitHub App. You can deploy public and private repos through your GitHub Apps. Requires a GitHub App already configured in Coolify. |
| coolify_create_application_dockercomposeB | Create a Docker Compose application without Git. You can deploy complex applications easily with Docker Compose by providing the raw compose file content directly. Note: Coolify marks this endpoint as deprecated in favor of /services, but it remains available in the UI. |
| coolify_set_compose_configA | Configure compose-specific fields for a dockercompose application: domain-to-service mapping, compose file location, and optionally clear stale custom_labels. This is required after creating a compose app to set up Traefik routing. |
| coolify_update_applicationA | Update an application's configuration. Supports changing name, description, domains, Git settings, build pack, health check config, ports, and more. Only supply the fields you want to change. |
| coolify_delete_applicationA | Permanently delete an application by UUID. This stops the app and removes all associated resources. |
| coolify_application_logsA | Retrieve recent logs for an application by its UUID. Returns an informational message (not an error) if the application is stopped. Requires: uuid (application UUID, not service UUID — use vps_docker_logs for compose services). |
| coolify_list_private_keysA | List all SSH private keys stored in Coolify. These are used for Git deploy key authentication and server SSH access. Returns UUID, name, description, and fingerprint for each key. |
| coolify_create_private_keyA | Generate an Ed25519 SSH key pair and store it in Coolify. Returns the UUID and public key. The public key should be added to GitHub as a deploy key (via github_add_deploy_key) or to a server's authorized_keys. The private key is stored encrypted in Coolify. |
| coolify_delete_private_keyA | Delete an SSH private key from Coolify by UUID. Will fail with 422 if the key is still in use by an application or server. |
| coolify_deployA | Trigger a deployment for one or more applications. Can deploy by application UUID or by tag (tags let you deploy an entire group of apps at once). Returns the deployment UUID for tracking. |
| coolify_list_deploymentsA | List deployment history for a specific application. Returns status, commit, timestamps, and deployment UUIDs. |
| coolify_get_deploymentA | Get full details and logs for a specific deployment by its deployment UUID. |
| coolify_cancel_deploymentA | Cancel a running or queued deployment by its deployment UUID (not the application UUID). |
| coolify_list_app_envsA | List all environment variables for an application. Values of secrets may be masked by Coolify. |
| coolify_create_app_envA | Add a new environment variable to an application. Remember: per infra standards, secrets should originate from BWS — this tool sets them in Coolify. |
| coolify_update_app_envA | Update an existing environment variable on an application. Coolify matches the var by key name — key and value are both required. |
| coolify_delete_app_envB | Remove an environment variable from an application. |
| coolify_bulk_create_app_envsA | Create or update multiple environment variables at once via a single API call. Coolify upserts: existing keys are updated, new keys are created. Useful when setting up a new application with all its required env vars from BWS. |
| coolify_list_service_envsA | List all environment variables for a Coolify service (Flavor C / docker-compose apps). Use this for services deployed as docker-compose — NOT for single-container applications (use coolify_list_app_envs for those). |
| coolify_create_service_envA | Add a new environment variable to a Coolify service (Flavor C / docker-compose apps). Use this for multi-container compose services — NOT for single-container applications. |
| coolify_update_service_envA | Update an existing environment variable on a Coolify service (Flavor C / docker-compose apps). Coolify matches the var by key name. Use for multi-container compose services. |
| coolify_delete_service_envA | Remove an environment variable from a Coolify service (docker-compose apps). |
| coolify_bulk_update_service_envsA | Create or update multiple environment variables at once for a Coolify service (docker-compose apps). Coolify upserts: existing keys are updated, new keys are created. Use for Flavor C apps (ContactHub, CRM, etc.) — NOT for single-container applications. |
| coolify_bulk_set_app_envA | Upsert ONE environment variable (key/value) across many applications at once. Useful for rotating a shared secret. Returns a per-app success/failure summary; a failure on one app does not stop the others. |
| coolify_list_databasesA | List all database resources managed by Coolify. Returns a compact summary by default; pass summary:false for full objects. |
| coolify_get_databaseA | Get full details for a database resource by UUID — connection info, status, configuration. |
| coolify_create_databaseA | Create a new database resource. For Devon's Flavor B apps, this is typically PostgreSQL 16 deployed on the same VPS. Supported types: postgresql, mysql, mariadb, mongodb, redis, keydb, clickhouse, dragonfly. |
| coolify_update_databaseA | Update a database resource's configuration. |
| coolify_delete_databaseA | Delete a database resource. WARNING: This destroys the database and all its data. |
| coolify_list_serversA | List all servers registered with Coolify. Returns name, IP, reachability status, and UUID for each. Compact summary by default; pass summary:false for full objects. |
| coolify_get_serverA | Get full details for a server by UUID — IP, settings, connectivity status, and validation logs. |
| coolify_validate_serverA | Test SSH connectivity and Docker prerequisites for a server. Use this to verify a server is properly connected before deploying resources. |
| coolify_server_resourcesA | List all applications, databases, and services deployed on a specific server. Great for getting a full inventory of what's running on your VPS. |
| coolify_server_domainsA | Retrieve all domain-to-resource mappings configured on a server. Shows which apps are reachable at which FQDNs. |
| coolify_list_servicesA | List all services (Docker Compose workloads) managed by Coolify. Compact summary by default; pass summary:false for full objects. |
| coolify_get_serviceA | Get full details for a service by UUID — includes compose config, status, and resource mapping. Webhook/basic-auth secrets are masked unless reveal:true. |
| coolify_create_serviceA | Create a new service from a Docker Compose definition or a one-click template. For Devon's Flavor C apps (like Contact Hub), supply the docker-compose.yml content. |
| coolify_update_serviceB | Update a service's configuration. |
| coolify_delete_serviceA | Delete a service. WARNING: Stops all containers and removes the service definition. |
| coolify_controlA | Start, stop, or restart an application, database, or service. This is the universal control tool — use it for lifecycle management of any Coolify resource. |
| coolify_reset_labelsA | Clear custom_labels on an application so Coolify auto-generates Traefik labels from the current domain config. Use this after changing domains to fix stale routing rules. Optionally triggers a redeploy. |
| coolify_versionA | Returns the Coolify instance version. Useful for verifying connectivity and API compatibility. |
| coolify_overviewA | Get a comprehensive snapshot of all servers, projects, applications, databases, and services. This is the best starting point when you need to understand the current state of the infrastructure. |
| coolify_diagnose_appA | Composite diagnostic for an application: fans out to fetch details, recent logs, env var count, and deployment history in parallel. Accepts UUID, app name, or FQDN/domain. |
| coolify_diagnose_serverA | Composite diagnostic for a server: fetches details, resources, domains, and runs a connectivity validation in parallel. Accepts UUID, name, or IP address. |
| coolify_find_issuesA | Scan all servers, applications, databases, and services for unhealthy or unreachable resources. Returns a summary with counts and a detailed issues list. |
| coolify_audit_standardsA | Scan all (or one) Coolify application and database against infra-brain standards (fetched from infra-brain's REST API; cached fallback). Returns proposals — each a deviation paired with a concrete remediation tool-call. Read-only: applies nothing. |
| coolify_list_storagesA | List persistent volumes and bind mounts for an application, database, or service. |
| coolify_create_storageB | Add a persistent volume or bind mount to an application, database, or service. |
| coolify_update_storageB | Update a storage entry (e.g. change mount path or host path). |
| coolify_delete_storageC | Remove a storage entry from an application, database, or service. |
| coolify_list_scheduled_tasksA | List all scheduled (cron) tasks for an application or service. |
| coolify_create_scheduled_taskA | Add a cron task to an application or service. |
| coolify_update_scheduled_taskB | Update a scheduled task's command, frequency, or enabled state. |
| coolify_delete_scheduled_taskC | Remove a scheduled task from an application or service. |
| coolify_list_task_executionsA | Retrieve execution history for a scheduled task. |
| coolify_list_database_backupsA | List configured backup schedules for a database. Returns frequency (cron), enabled state, S3 config, and retention. |
| coolify_get_database_backupB | Get a single backup schedule by its UUID. |
| coolify_list_backup_executionsA | List execution history (runs) for a backup schedule — status, size, filename, timestamps. |
| coolify_get_backup_executionA | Get a single backup execution by its UUID. |
| coolify_create_database_backupB | Create a scheduled backup for a database. |
| coolify_update_database_backupA | Update fields of an existing backup schedule. Only supplied fields change. |
| coolify_delete_database_backupA | Delete a backup schedule by UUID. Does not delete already-stored backup files. |
| coolify_delete_backup_executionA | Delete a single backup execution (and its stored file) by UUID. |
| coolify_list_github_appsA | List GitHub-App source integrations configured in Coolify. Returns id, uuid, name, organization. Use coolify_get_github_app for full detail. |
| coolify_get_github_appA | Get a single GitHub-App integration by its numeric id. |
| coolify_create_github_appC | Register a GitHub App as a Coolify deployment source. |
| coolify_update_github_appC | Update fields of a GitHub-App integration. Only supplied fields change. |
| coolify_delete_github_appB | Delete a GitHub-App integration by id. |
| coolify_list_github_app_reposA | List repositories the GitHub App can access (name, full_name, default_branch, private). |
| coolify_list_github_app_branchesB | List branches for a repo the GitHub App can access. |
| coolify_search_docsA | Search the official Coolify documentation and return the most relevant sections (title, url, description, snippet). Use for API/config/feature questions. No instance needed. |
| vps_execA | Run a shell command on the selected VPS and return stdout, stderr, and exit code. Targets Hetzner prod by default; pass instance='dev' to run inside the OrbStack ubuntu machine. Use for any ad-hoc operation: checking processes, installing packages, inspecting logs, etc. |
| vps_healthA | Get a comprehensive health snapshot of the selected VPS: uptime, CPU load, memory usage, disk usage, running Docker containers count, and top processes by CPU. Targets Hetzner prod by default; pass instance='dev' for the OrbStack ubuntu machine. |
| vps_read_fileA | Read the contents of a file on the selected VPS. Targets Hetzner prod by default; pass instance='dev' for the OrbStack ubuntu machine. |
| vps_write_fileA | Write content to a file on the selected VPS. Creates the file if it doesn't exist, overwrites if it does. Targets Hetzner prod by default; pass instance='dev' for the OrbStack ubuntu machine. |
| vps_docker_psA | List running Docker containers on the selected VPS. Shows name, image, status, ports, and size. Targets Hetzner prod by default; pass instance='dev' for the OrbStack ubuntu machine (docker is invoked via sudo on dev). |
| vps_docker_logsA | Retrieve logs from a Docker container on the selected VPS. Targets Hetzner prod by default; pass instance='dev' for the OrbStack ubuntu machine. |
| vps_docker_statsA | Get current CPU, memory, network, and disk I/O usage for all running containers on the selected VPS. One-shot snapshot (not streaming). Targets Hetzner prod by default; pass instance='dev' for the OrbStack ubuntu machine. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AlobarQuest/infraops-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server