folklore-variant-evidence-view — Folklore Clinical Variant Interpretation MCP MCP Resource
folklore-variant-evidence-view
is one of 1 resource on the
Folklore Clinical Variant Interpretation MCP
MCP server. Connect the server and your client can attach it as context.
by client
How to attach folklore-variant-evidence-view from your client
- Claude Code Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view run in your project directory
- Claude Desktop Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view ~/.cursor/mcp.json
- VS Code Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view .vscode/mcp.json
- Zed Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view ~/.config/zed/settings.json
- Windsurf Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view ~/.codeium/windsurf/mcp_config.json
- Cline Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view ~/.gemini/settings.json
- Grok Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view .mcp.json (in your project root)
- ChatGPT Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view Settings → Connectors → Advanced → Developer mode
- Claude.ai Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view Settings → Connectors → Add custom connector
- LangChain Folklore Clinical Variant Interpretation MCP Resource/folklore-variant-evidence-view pip install langchain-mcp-adapters
Folklore Clinical Variant Interpretation MCP also offers 5 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.