vi-status — Venture Insights Concept Diagnostic MCP Resource

vi-status is one of 4 resources on the Venture Insights Concept Diagnostic MCP server. Connect the server and your client can attach it as context.

by client

How to attach vi-status from your client

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

Other resources on this server

• vi-services
• vi-intake
• vi-intake-form

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.