Condition lens definitions — Clarity by Health AI MCP Resource

Condition lens definitions is one of 2 resources on the Clarity by Health AI MCP server. Connect the server and your client can attach it as context.

by client

How to attach Condition lens definitions from your client

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

Other resources on this server

• Clarity evidence model & methodology

Clarity by Health AI 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.