config-status
Retrieve the current configuration status of your Coolify deployments to verify infrastructure consistency and identify misconfigurations.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Implementation Reference
- src/mcp-server.ts:48-57 (registration)The 'config-status' tool is registered inline in the catch block of the client configuration step. It is only added if the Coolify client configuration fails (e.g., missing environment variables).
server.tool( 'config-status', {}, async () => ({ content: [{ type: 'text', text: 'Coolify MCP server is running but not configured. Please set COOLIFY_API_URL and COOLIFY_API_TOKEN environment variables to enable Coolify API access.' }] }) ); - src/mcp-server.ts:51-56 (handler)The tool's handler is an inline async function that returns a message explaining the configuration issue. It takes no parameters (empty schema {}) and returns a simple text message directing users to set COOLIFY_API_URL and COOLIFY_API_TOKEN.
async () => ({ content: [{ type: 'text', text: 'Coolify MCP server is running but not configured. Please set COOLIFY_API_URL and COOLIFY_API_TOKEN environment variables to enable Coolify API access.' }] }) - src/mcp-server.ts:50-50 (schema)The tool has no input parameters — the schema is an empty object {}.
{},