diagnose_a_deployment — fline MCP Prompt
diagnose_a_deployment
is one of 7 prompts on the
fline
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke diagnose_a_deployment from your client
- Claude Code fline Prompt/diagnose_a_deployment run in your project directory
- Claude Desktop fline Prompt/diagnose_a_deployment ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor fline Prompt/diagnose_a_deployment ~/.cursor/mcp.json
- VS Code fline Prompt/diagnose_a_deployment .vscode/mcp.json
- Zed fline Prompt/diagnose_a_deployment ~/.config/zed/settings.json
- Windsurf fline Prompt/diagnose_a_deployment ~/.codeium/windsurf/mcp_config.json
- Cline fline Prompt/diagnose_a_deployment ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI fline Prompt/diagnose_a_deployment ~/.gemini/settings.json
- Grok fline Prompt/diagnose_a_deployment .mcp.json (in your project root)
- ChatGPT fline Prompt/diagnose_a_deployment Settings → Connectors → Advanced → Developer mode
- Claude.ai fline Prompt/diagnose_a_deployment Settings → Connectors → Add custom connector
- LangChain fline Prompt/diagnose_a_deployment pip install langchain-mcp-adapters
Other prompts on this server
Read from the server itself, by connecting to it and calling prompts/list on 17 October 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.