Issue #217 opened: database tool missing destination_uuid in schema (fails on servers with multiple destinations)
What happened?
The database tool currently fails to create managed databases on Coolify instances that have multiple destinations configured. This happens because the database tool schema does not expose or accept a destination_uuid parameter, which the Coolify API strictly requires when ambiguity exists.
In contrast, the application tool works perfectly because it properly includes the destination fields in its schema.
Steps to reproduce
- Use an instance of Coolify with more than one destination configured on the server (e.g.,
localhost). - Attempt to create a managed database (like PostgreSQL) using the MCP
databasetool. - The Coolify API rejects the request since no destination is specified.
Expected behaviour
The database tool schema should accept an optional or required (fallback) destination_uuid parameter (similar to how applications handle it), allowing users to specify where the database should be provisioned.
Additional context
The tool fails with an error from the Coolify API:
“Server has multiple destinations. Please provide a destination_uuid.”
Looking at the tool definition, destination_uuid is stripped out or ignored because it's missing from the tool's input schema.