when_to_seek_care — MedDroid MCP Tool
when_to_seek_care
(when to seek care) is one of 14 tools on the
MedDroid
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call when_to_seek_care from your client
- Claude Code MedDroid when_to_seek_care run in your project directory
- Claude Desktop MedDroid when_to_seek_care ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MedDroid when_to_seek_care ~/.cursor/mcp.json
- VS Code MedDroid when_to_seek_care .vscode/mcp.json
- Zed MedDroid when_to_seek_care ~/.config/zed/settings.json
- Windsurf MedDroid when_to_seek_care ~/.codeium/windsurf/mcp_config.json
- Cline MedDroid when_to_seek_care ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MedDroid when_to_seek_care ~/.gemini/settings.json
- Grok MedDroid when_to_seek_care .mcp.json (in your project root)
- ChatGPT MedDroid when_to_seek_care Settings → Connectors → Advanced → Developer mode
- Claude.ai MedDroid when_to_seek_care Settings → Connectors → Add custom connector
- LangChain MedDroid when_to_seek_care pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http meddroid https://medicalandroid.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.