review_my_results — physician review MCP Prompt

review_my_results is one of 3 prompts on the physician review MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke review_my_results from your client

• Claude Code physician review Prompt/review_my_results run in your project directory
• Claude Desktop physician review Prompt/review_my_results ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor physician review Prompt/review_my_results ~/.cursor/mcp.json
• VS Code physician review Prompt/review_my_results .vscode/mcp.json
• Zed physician review Prompt/review_my_results ~/.config/zed/settings.json
• Windsurf physician review Prompt/review_my_results ~/.codeium/windsurf/mcp_config.json
• Cline physician review Prompt/review_my_results ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI physician review Prompt/review_my_results ~/.gemini/settings.json
• Grok physician review Prompt/review_my_results .mcp.json (in your project root)
• ChatGPT physician review Prompt/review_my_results Settings → Connectors → Advanced → Developer mode
• Claude.ai physician review Prompt/review_my_results Settings → Connectors → Add custom connector
• LangChain physician review Prompt/review_my_results pip install langchain-mcp-adapters

Other prompts on this server

• book_physician_review
• what_is_covered

physician review also offers 3 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.