mediora__get_patient_history — mediora mcp MCP Tool
mediora__get_patient_history
(mediora get patient history) is one of 14 tools on the
mediora mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call mediora__get_patient_history from your client
- Claude Code mediora mcp mediora__get_patient_history run in your project directory
- Claude Desktop mediora mcp mediora__get_patient_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mediora mcp mediora__get_patient_history ~/.cursor/mcp.json
- VS Code mediora mcp mediora__get_patient_history .vscode/mcp.json
- Zed mediora mcp mediora__get_patient_history ~/.config/zed/settings.json
- Windsurf mediora mcp mediora__get_patient_history ~/.codeium/windsurf/mcp_config.json
- Cline mediora mcp mediora__get_patient_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mediora mcp mediora__get_patient_history ~/.gemini/settings.json
- Grok mediora mcp mediora__get_patient_history .mcp.json (in your project root)
- ChatGPT mediora mcp mediora__get_patient_history Settings → Connectors → Advanced → Developer mode
- Claude.ai mediora mcp mediora__get_patient_history Settings → Connectors → Add custom connector
- LangChain mediora mcp mediora__get_patient_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mediora-mcp https://mcp.mediora.ai/mcpOther tools on this server
- mediora__list_markers
- mediora__explain_marker
- mediora__list_conditions
- mediora__explain_condition
- mediora__lookup_marker
- mediora__list_symptoms
- mediora__explain_symptom
- mediora__list_panels
- mediora__explain_panel
- mediora__whoami
- mediora__analyze_lab_pdf
- mediora__get_test_details
- mediora__longitudinal_trend
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.