[Bug] Coolify MCP tools return 'Tool not found' on staging

[up-guillaume]

Problem

All Coolify MCP tools consistently return errors like:

• coolify_list_servers → "Error: Tool 'list_servers' not found"
• coolify_list_databases → "Error: Tool 'database' not found"
• coolify_get_infrastructure_overview → "Error: Tool 'get_infrastructure_overview' not found"
• coolify_list_applications → "Error: Tool 'application' not found"
• coolify_projects → "Error: Tool 'projects' not found"

Impact

• Agents cannot access Coolify infrastructure data
• Agents waste time trying broken tools instead of using SSH alternatives
• 9 Coolify tools disabled via migration moiria_v1103_10 as workaround

Root Cause Analysis

The error messages suggest the MCP tool name resolution is stripping the coolify_ prefix:

• Agent calls coolify_list_servers
• MCP server looks for list_servers (without prefix)
• Tool not found

This is different from other MCP tools (Hetzner, SSH) which work correctly.

Current Workaround

Migration moiria_v1103_10 disables these 9 broken tools:

• coolify_system
• coolify_list_servers
• coolify_list_databases
• coolify_get_infrastructure_overview
• coolify_list_applications
• coolify_list_services
• coolify_projects
• coolify_teams
• coolify_list_deployments

Investigation Needed

1. Check Coolify MCP server configuration on LiteLLM staging
2. Verify tool name mapping in LiteLLM config
3. Check if Coolify MCP server needs re-import
4. Compare with working MCP servers (hetzner_cloud, mcp_ssh_bridge)

Acceptance Criteria

• Root cause identified
• Coolify MCP tools return actual data (not errors)
• Re-enable the 9 disabled tools
• Test with "list Coolify projects" → returns project list
• No regression on other MCP tools