Skip to content
Mistflow

Troubleshooting

“No MCP tools found” in my editor

Section titled ““No MCP tools found” in my editor”

Your editor can’t see the Mistflow MCP server.

  1. Check that the MCP config file exists and has the mistflow entry:

    • Claude Code: ~/.claude/mcp.json
    • Cursor: Settings > MCP Servers

  2. Restart your editor completely (not just reload).

  3. If the issue persists, re-run the installer:

    Terminal window
    npx @mistflow/installer

“Authentication failed”

Section titled ““Authentication failed””

Your API key is missing or expired.

  1. Re-run the installer to refresh:

    Terminal window
    npx @mistflow/installer

  2. Or manually update your API key in the MCP config. Get a new key from Settings.

Build fails during deploy

Section titled “Build fails during deploy”

The deploy tool runs a build check first. If it fails:

  1. Ask your AI to run debug-build — it returns parsed errors with fix suggestions.
  2. Fix the issues and retry the deploy.

Deploy succeeds but the site shows a blank page

Section titled “Deploy succeeds but the site shows a blank page”

This usually means:

  • The index.html is missing from the build output
  • JavaScript has a runtime error

Ask your AI: Debug why my deployed site shows a blank page — it will check the build output and logs.

Custom domain not working

Section titled “Custom domain not working”

DNS propagation can take up to 48 hours (usually 1-10 minutes).

  1. Check your DNS records match what the dashboard shows
  2. Click Verify in the dashboard to re-check
  3. Make sure you don’t have conflicting A/AAAA records for the same domain

”Deploy limit reached”

Section titled “”Deploy limit reached””

You’ve hit your plan’s monthly deploy limit. Options:

  • Wait until the next billing cycle
  • Upgrade your plan from Settings
  • On Pro, you can exceed the limit at $0.50/deploy

Something else?

Section titled “Something else?”