book_physician_review — physician review MCP Prompt
book_physician_review
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 book_physician_review from your client
- Claude Code physician review Prompt/book_physician_review run in your project directory
- Claude Desktop physician review Prompt/book_physician_review ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor physician review Prompt/book_physician_review ~/.cursor/mcp.json
- VS Code physician review Prompt/book_physician_review .vscode/mcp.json
- Zed physician review Prompt/book_physician_review ~/.config/zed/settings.json
- Windsurf physician review Prompt/book_physician_review ~/.codeium/windsurf/mcp_config.json
- Cline physician review Prompt/book_physician_review ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI physician review Prompt/book_physician_review ~/.gemini/settings.json
- Grok physician review Prompt/book_physician_review .mcp.json (in your project root)
- ChatGPT physician review Prompt/book_physician_review Settings → Connectors → Advanced → Developer mode
- Claude.ai physician review Prompt/book_physician_review Settings → Connectors → Add custom connector
- LangChain physician review Prompt/book_physician_review pip install langchain-mcp-adapters
Other prompts on this server
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.