Get started with a Physician Health Review — physician review MCP Resource

Get started with a Physician Health Review is one of 3 resources on the physician review MCP server. Connect the server and your client can attach it as context.

by client

How to attach Get started with a Physician Health Review from your client

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

Other resources on this server

• Pick a time for your Physician Health Review
• Your booking and payment

physician review also offers 3 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, 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 resource's type and contents.