- STALLED
- FAILED
- HEALTHY
- HUMAN
Short answer
How do I find out why my Cloudify deployment failed?
Your AI pulls the specific execution history and node states to see which step in the workflow hit an error. It identifies the exact node that stalled so you don't have to hunt through logs manually. You'll get a clear breakdown of the failure point below.
Investigation outcomes
Where every issue lands.
The AI categorizes the results of its investigation into these four areas.
STALLED
Identify the bottleneck
The AI finds the specific node that stopped responding. You get the exact point in the workflow where progress ceased.
FAILED
Pinpoint the error
The AI looks at execution logs to find the error message. It tells you which task failed and why.
HEALTHY
Confirm stable nodes
The AI checks that all other nodes are running correctly. This rules out widespread infrastructure issues.
HUMAN
Manual intervention needed
The AI flags issues it can't fix, like invalid credentials or missing resources. You decide how to resolve these.
The workflow
What your AI does when a deployment fails.
Instead of you clicking through a dashboard, your agent performs the investigation.
Locate the deployment
The AI finds the specific deployment you're asking about to get the full context.
get_deploymentCheck node status
The AI looks at every node in the environment to see which ones are active or stuck.
list_nodesReview execution history
The AI pulls the history of recent runs to see the sequence of events leading to the failure.
list_executionsSummarize the failure
The AI combines the node states and execution logs into a single report of what went wrong.
get_deploymentlist_executions
Try it
Copy these to start.
Use these prompts to kick off an investigation.
Starting points
These are starting points. Swap out the deployment IDs or node names for your actual Cloudify data.
Cloudify Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_YIdeRn0hAqBloQdQ3tH0JMinN2MrEDBkMrsxMQwv/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — Cloudify capabilities are ready to use.
{
"mcpServers": {
"cloudify-mcp": {
"url": "https://edge.vinkius.com/vk_preview_YIdeRn0hAqBloQdQ3tH0JMinN2MrEDBkMrsxMQwv/mcp"
}
}
}Why did deployment 'prod-web-server' fail during its last run?
Check the status of all nodes in my current Cloudify environment.
Look at the execution history for 'db-cluster-01' and tell me where it stalled.
Which node in my latest deployment is currently in a failed state?
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect Cloudify once, then ask.
Just click the link to connect. Your credentials stay encrypted, and you can immediately start asking your AI about your Cloudify workflows.
Connect Cloudify to your AIFAQ
How this task behaves.
- 01
Can the AI fix the failed deployment for me?
No. The AI can only read node states and execution histories to tell you what happened. You have to perform the actual fix.
- 02
Can the AI delete a deployment?
No. This MCP only has tools to list and get information. It cannot delete or modify your Cloudify resources.
- 03
Does the AI see all my Cloudify data?
The AI only sees the data it can access through the specific tools provided, like node lists and deployment details.
- 04
How does the AI know which deployment to look at?
You tell the AI the specific deployment name or ID in your prompt, and it uses that to target its search.
- 05
Can I use this with any AI client?
Yes, you can use this with any MCP-compatible client like Claude, Cursor, or Windsurf once you've connected it via Vinkius.
More questions about Cloudify? The Connector page answers them. See everything the Cloudify Connector can do
Connect Cloudify to Claude, Cursor, ChatGPT & more
