diagnostic.schema.json — tabnas MCP Resource

diagnostic.schema.json is one of 5 resources on the tabnas MCP server. Connect the server and your client can attach it as context.

by client

How to attach diagnostic.schema.json from your client

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

Other resources on this server

• grammar.schema.json
• error-codes.json
• plugins.json
• DIVERGENCE.md

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.