Full Symptom Directory — AcuiQ MCP Resource

Full Symptom Directory is one of 2 resources on the AcuiQ MCP server. Connect the server and your client can attach it as context.

by client

How to attach Full Symptom Directory from your client

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

Other resources on this server

• AcuiQ LLM Briefing

AcuiQ also offers 4 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.