DEEPBOM browser-local artifact analyzer — DEEPBOM MCP Resource

DEEPBOM browser-local artifact analyzer is one of 1 resource on the DEEPBOM MCP server. Connect the server and your client can attach it as context.

by client

How to attach DEEPBOM browser-local artifact analyzer from your client

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

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.