# Coolify MCP for AI Agents AI Agent Connect > Coolify MCP. Manage your self-hosting via Coolify. This Connector lets you monitor nodes, deploy applications, and manage databases directly from your AI agent. It handles the heavy lifting of infrastructure management so you can focus on building. Whether you're spinning up a new Nixpacks image or just need to check a Docker Swarm status, this Connector gives your agent the permissions it needs to act on your private cloud. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_2OtVSYxP6F0y5CH4pZP2Y6H6N3UqbNzYtv86n8vS/ai-agent-connect - **Tags:** self-hosting, docker, server-monitoring, deployment-automation, infrastructure-as-code, container-management ## Description You can manage your entire self-hosted infrastructure using natural language. This Connector connects your agent to Coolify so you can handle your private cloud without jumping between tabs. Instead of hunting for IP properties or checking Docker Swarm statuses in a dashboard, you just ask your agent to do it. You can trigger builds for your Nixpacks images, manage your PostgreSQL and MySQL configurations, or pull connection strings for your apps. It handles the heavy lifting of finding the right application UUIDs and mapping your project repositories. You'll find this Connector in the Vinkius catalog alongside other tools for infrastructure management. It turns your private cloud into a conversational interface where you can start, stop, and restart applications natively. You can also fetch elaborate internal topology metrics like mapped GitHub branches and Traefik proxy paths without digging through menus. It's built for people who want to move fast and keep their infrastructure organized without the manual overhead of traditional dashboard management. ## Tools ### get_application Fetch internal metrics for a specific app, including GitHub branches and Traefik paths. Use this to see the exact topology of a managed project. ### get_database Pull internal configuration arrays and connection strings for your datastores. This is perfect for linking new apps to backend databases. ### get_server See IP properties and SSH connection statuses for your nodes. Use this to verify the health of your physical endpoints. ### list_applications View every frontend and backend app currently managed by Coolify. This generates a map of all your active projects. ### list_databases See all your PostgreSQL, MySQL, and Redis configurations in one list. It helps you quickly find connection strings and backup timelines. ### list_servers Identify the physical endpoints running your Docker swarms. Use this to see the raw nodes attached to your instance. ### stop_application Halt an application to pause billing or restrict web ingress. This is useful for quickly taking a project offline. ### trigger_deployment Run a build pipeline to roll out the latest Git commit as a new Docker image. It handles fetching, rebuilding, and rolling out. ### restart_application Bounce an application to ensure new environment variables take effect immediately. It cycles the container states for you. ### start_application Spin up containers for any suspended application. Use this to resume projects that have been paused. ## Prompt Examples **Prompt:** ``` List all active servers in my Coolify instance ``` **Response:** ``` I found 2 nodes: 'Main-Hetzner-Node' (UUID: abc-123) and 'Backup-Vultr' (UUID: def-456). Both are connected and running Docker Swarm. Would you like to see the applications on either of these? ``` **Prompt:** ``` Trigger a deployment for application 'backend-api' ``` **Response:** ``` Deployment triggered for 'backend-api'! Coolify is now fetching the latest Git commit and rebuilding the Nixpacks image. I will notify you once the new version is live. ``` **Prompt:** ``` What is the connection string for database 'user-db-prod'? ``` **Response:** ``` Retrieving connection string for 'user-db-prod'... The internal URI is: `postgres://user:pass@coolify-db-abc:5432/user_db`. This URI is only accessible within your internal Docker network. ``` ## Capabilities ### Deploy new code Trigger builds for Nixpacks images and roll out the latest Git commits. ### Check node health Verify IP properties and Docker Swarm statuses across your cluster. ### Manage database configs Retrieve internal connection strings and configuration arrays for your datastores. ### Restart running apps Bounce applications to apply new environment variables to runtime RAM. ### Monitor project status See every frontend and backend app currently managed by your instance. ## Use Cases ### The Late Night Fix An engineer needs to restart a container because an environment variable changed. They ask the agent to use `restart_application` to bounce the app immediately. ### The New Release A developer wants to push the latest commit to production. They tell the agent to use `trigger_deployment` to rebuild the Nixpacks image and roll it out. ### The Audit A sysadmin needs to check the status of all nodes in a swarm. They ask the agent to use `list_servers` to verify the health of the physical endpoints. ### The Database Link A developer needs the internal URI for a new MySQL instance. They use `get_database` to get the connection string for their backend. ## Benefits - Stop manual dashboard navigation. Use `list_applications` to see your entire project map in one glance instead of clicking through menus. - Faster deployments. Use `trigger_deployment` to roll out the latest Git commits and rebuild Nixpacks images instantly via your agent. - Easier database linking. Use `get_database` to grab connection strings for your apps without having to copy-paste from multiple tabs. - Instant app updates. Use `restart_application` to push new .env variables to runtime without manual intervention. - Better node visibility. Use `get_server` to see IP properties and SSH statuses across your cluster in a single command. - Simplified lifecycle control. Use `start_application` and `stop_application` to manage your resources during maintenance or incidents. ## How It Works The bottom line is you get full control over your self-hosted cloud through a simple chat interface. 1. Subscribe to the Coolify MCP in the Vinkius catalog. 2. Provide your Coolify Instance URL and API Token from your dashboard. 3. Talk to your agent to manage your apps, nodes, and deployments. ## Frequently Asked Questions **Can the Coolify MCP manage my AWS instances?** No, this Connector is specifically designed to connect to your Coolify instance. It won't manage public cloud providers like AWS or GCP directly. **How do I connect Coolify MCP to my agent?** You just need to subscribe to the Connector and provide your Coolify Instance URL and your API Token. You can find your token in the Keys & Tokens section of your Coolify dashboard. **Can I use it to see my Docker Swarm status?** Yes, you can ask your agent to check the status of your nodes and Docker Swarm properties across your cluster using the list and get tools. **Does Coolify MCP support Nixpacks?** Yes, it can trigger raw build pipelines that rebuild Nixpacks images and roll out updated Docker versions directly to your applications. **Will it help me find my database connection strings?** Yes, it can pull the internal configuration arrays and connection strings for your managed PostgreSQL, MySQL, and Redis databases. **Can I restart my apps using the Coolify MCP?** Yes, you can ask your agent to bounce an application to ensure that new environment variables or configuration updates take effect in runtime. **Can my agent trigger a new deployment for a Coolify application?** Yes. Use the 'trigger_deployment' tool with the application UUID. The agent will initiate a full build pipeline, fetching the latest commit and rolling out the updated version directly on your server. **How do I retrieve the internal connection string for a managed database?** Provide the database UUID to the 'get_database' tool. Your agent will extrapolate the internal network URI (e.g., for PostgreSQL or MySQL), allowing you to securely link your apps without external port exposure. **Can I restart an application to apply new environment variables?** Absolutely. Use the 'restart_application' tool. The agent will execute an overlapping bounce, destroying old instances and initializing fresh replicas with the latest configuration and environment variables.