Debugging your application with MCP

These are common situations where it's faster to ask your connected assistant than to click through the dashboard yourself.

"My deploy failed"

Ask: "Why did my last deploy fail?"

The assistant reaches for diagnose_deploy_failure — a single tool that chains together build history, the failing build's logs, every resource's status, self-healing history, runtime logs, missing environment variables, missing Dockerfile build arguments, and (if you give it a local repo path) an actual local Docker build test. It comes back with a failure category, a list of concrete issues with evidence, and a plain-language verdict — instead of you opening five different dashboard tabs.

"My app is down or crashing"

Ask: "Is my server crashing? What's going on with it?"

The assistant pulls runtime logs from the live container and cross-checks self-healing history. Repeated restart attempts that never reach HEALED are flagged as a suspected (not confirmed) sign the instance isn't responding — enough to point you in the right direction.

"My build keeps failing and I don't know why"

Ask: "Test the generated Dockerfile against my local repo."

This runs a real docker build against your actual checked-out code (requires the MCP server running on your own machine, with Docker installed). It's the most reliable way to catch a Dockerfile issue, because it reproduces the real build instead of relying on stored metadata.

"A value looks wrong but I can't tell what's configured"

Ask: "Does the STRIPE_SECRET_KEY I have locally match what's configured on Kuberns?"

The assistant fetches a SHA-256 hash of the configured value and compares it against a hash of your local value — never exposing either value in plaintext. A mismatch tells you there's a stale value, a typo, or extra whitespace, even though it can't show you the exact difference.

"My custom domain won't go live"

Ask: "Why is my custom domain stuck?"

The assistant checks the domain's status and process_status — telling you whether it's stuck on CNAME verification, A-record verification, SSL certificate generation, or final activation.

"I can't start my server"

Ask: "Why won't my server start?"

Usually a credits problem. The assistant checks whether you have enough available credits for that specific resource, and reports the required vs. available amount.