diagnose_windows_issue — WindowsForum MCP Server MCP Prompt
diagnose_windows_issue
is one of 4 prompts on the
WindowsForum MCP Server
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke diagnose_windows_issue from your client
- Claude Code WindowsForum MCP Server Prompt/diagnose_windows_issue run in your project directory
- Claude Desktop WindowsForum MCP Server Prompt/diagnose_windows_issue ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WindowsForum MCP Server Prompt/diagnose_windows_issue ~/.cursor/mcp.json
- VS Code WindowsForum MCP Server Prompt/diagnose_windows_issue .vscode/mcp.json
- Zed WindowsForum MCP Server Prompt/diagnose_windows_issue ~/.config/zed/settings.json
- Windsurf WindowsForum MCP Server Prompt/diagnose_windows_issue ~/.codeium/windsurf/mcp_config.json
- Cline WindowsForum MCP Server Prompt/diagnose_windows_issue ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WindowsForum MCP Server Prompt/diagnose_windows_issue ~/.gemini/settings.json
- Grok WindowsForum MCP Server Prompt/diagnose_windows_issue .mcp.json (in your project root)
- ChatGPT WindowsForum MCP Server Prompt/diagnose_windows_issue Settings → Connectors → Advanced → Developer mode
- Claude.ai WindowsForum MCP Server Prompt/diagnose_windows_issue Settings → Connectors → Add custom connector
- LangChain WindowsForum MCP Server Prompt/diagnose_windows_issue pip install langchain-mcp-adapters
Other prompts on this server
WindowsForum MCP Server also offers 17 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 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.