McpDeploy FAQs

Question 1

How does McpDeploy handle SSL and subdomain routing?

Accepted Answer

McpDeploy automatically provisions Let's Encrypt SSL certificates for all deployed applications and handles subdomain routing. Each deployed container gets its own unique subdomain (e.g., `myapp.yourdomain.com`) with HTTPS enabled out-of-the-box, powered by Traefik.

Question 2

What does 'LLM-driven deployment' mean in McpDeploy?

Accepted Answer

LLM-driven deployment means you can use natural language commands through an MCP (Model Context Protocol) client, such as Claude Code or Cursor, to interact with McpDeploy. This allows you to deploy, manage, and monitor your Docker containers using simple, conversational instructions.

Question 3

Can I deploy Docker images without an external registry?

Accepted Answer

Yes, McpDeploy supports direct image pushing, allowing you to build Docker images locally and send them straight to your VPS without the need for an intermediate registry. It also fully supports pulling images from external registries like DockerHub or GHCR.

Question 4

How can McpDeploy integrate with existing CI/CD pipelines?

Accepted Answer

McpDeploy provides a comprehensive REST API that mirrors all its functionalities. This allows seamless integration with CI/CD tools like GitHub Actions, Jenkins, or custom scripts, enabling programmatic deployment, logging, and management of applications.

Question 5

What is McpDeploy?

Accepted Answer

McpDeploy is a lightweight PaaS (Platform as a Service) designed for LLM-driven deployment of Docker containers to your Virtual Private Server (VPS). It operates without a database, using Docker as its source of truth, and allows management through natural language commands or a REST API.

McpDeploy

McpDeploy

Características Principales

Casos de Uso

Características Principales

Casos de Uso