Coolify-MCP

The server demonstrates strong security practices: secrets are loaded via environment variables (COOLIFY_API_URL, COOLIFY_API_TOKEN) and never exposed to AI agents. All tool inputs are rigorously validated using Zod schemas, preventing injection attacks and enforcing data integrity. The API client includes robust error handling with specific error codes for common issues (401, 403, 404, 409, 422, 429). Comprehensive logging provides an audit trail of tool invocations and API calls, aiding in security monitoring. Containerization is recommended, with the `docker-compose.yml` demonstrating hardened security options like `no-new-privileges:true`, `read_only: true`, `tmpfs`, `cap_drop: ALL`, and restricted `cap_add`. A dedicated `docs/SECURITY.md` file further outlines security considerations, best practices, and known limitations, indicating a proactive approach to security.