Activity

Problem

When fetching environment details via the environments tool (which calls Coolify's /projects/{uuid}/{environment_name_or_uuid} endpoint), Dragonfly, KeyDB, and ClickHouse databases are not included in the response.

The Coolify API response includes arrays for:

• postgresqls
• mysqls
• mariadbs
• mongodbs
• redis

But does NOT include:

• dragonflys
• keydbs
• clickhouses

Impact

When checking what resources exist in a project/environment, these database types are invisible. This can lead to:

• Attempting to delete projects that appear empty but still have running Dragonfly/KeyDB/ClickHouse instances
• Incomplete infrastructure audits
• Confusion when resources exist but aren't surfaced

Reproduction

1. Create a Dragonfly database in a project
2. Call the environments tool to get details of that environment
3. Observe that redis: [] is empty despite Dragonfly being Redis-compatible and running
4. Call list_databases - the Dragonfly instance appears correctly with database_type: "standalone-dragonfly"

Root Cause

This is an upstream Coolify API limitation - they added these database types but never updated the environment endpoint response schema to include them.

Suggested Approach

Cross-reference list_databases when fetching environment details to ensure all database types are captured.