audit_supplement_stack — Clarity by Health AI MCP Prompt
audit_supplement_stack
is one of 3 prompts on the
Clarity by Health AI
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke audit_supplement_stack from your client
- Claude Code Clarity by Health AI Prompt/audit_supplement_stack run in your project directory
- Claude Desktop Clarity by Health AI Prompt/audit_supplement_stack ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Clarity by Health AI Prompt/audit_supplement_stack ~/.cursor/mcp.json
- VS Code Clarity by Health AI Prompt/audit_supplement_stack .vscode/mcp.json
- Zed Clarity by Health AI Prompt/audit_supplement_stack ~/.config/zed/settings.json
- Windsurf Clarity by Health AI Prompt/audit_supplement_stack ~/.codeium/windsurf/mcp_config.json
- Cline Clarity by Health AI Prompt/audit_supplement_stack ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Clarity by Health AI Prompt/audit_supplement_stack ~/.gemini/settings.json
- Grok Clarity by Health AI Prompt/audit_supplement_stack .mcp.json (in your project root)
- ChatGPT Clarity by Health AI Prompt/audit_supplement_stack Settings → Connectors → Advanced → Developer mode
- Claude.ai Clarity by Health AI Prompt/audit_supplement_stack Settings → Connectors → Add custom connector
- LangChain Clarity by Health AI Prompt/audit_supplement_stack pip install langchain-mcp-adapters
Other prompts on this server
Clarity by Health AI also offers 2 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.