Use DEEPBOM.
Choose your workspace.

1. Download deepbom-1.103.0.mcpb.
2. In Claude Desktop, open Settings → Extensions → Advanced settings → Install Extension.
3. Select the model directory DEEPBOM may read, then start a new chat and ask it to inspect a file in that directory.

The extension bundles the local analyzer. Model bytes stay local; the tool result goes to Claude. This is an installable extension, not a claim of Anthropic directory approval.

Run the command for your host in the model workspace. The first command previews the managed files; the second installs them.

npx -y deepbom@1.103.0 integrate codex
npx -y deepbom@1.103.0 integrate codex --apply

npx -y deepbom@1.103.0 integrate claude-code
npx -y deepbom@1.103.0 integrate claude-code --apply

Start a new session and ask for a static model audit. The host needs access to the file and permission to run the analyzer.

1. Install and sign in to Antigravity CLI; Node.js 20+ and agy must be on PATH.
2. Download and extract plugin 1.0.0.
3. Run its installer with the directory containing your models:

node "/path/to/extracted/deepbom/install.mjs" --workspace "/path/to/models"

Replace both paths. Restart agy, check /mcp, then ask /deepbom:deepbom-inspect to inspect a file. The archive includes analyzer 1.103.0. Approvals remain under your control.

Independently distributed, not a Google-reviewed store listing. Windows/macOS commands are documented but have not been host-tested. This package targets Antigravity CLI.

With Node.js 20+ installed, add this server to your workspace's .vscode/mcp.json. Merge it with existing servers. It restricts DEEPBOM's model access to the workspace.

{
  "servers": {
    "deepbom": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "deepbom@1.103.0", "mcp"],
      "cwd": "${workspaceFolder}",
      "env": { "DEEPBOM_MCP_ALLOWED_ROOTS": "${workspaceFolder}" }
    }
  }
}

Start the server using VS Code's MCP controls, approve the tools you want to use, and ask your agent to inspect a workspace file. This is MCP configuration, not a dedicated DEEPBOM Marketplace extension.

Developer-mode testing is available where your account and workspace permit it. Public directory review is pending as of the date above.

1. Enable Developer mode in ChatGPT settings, then add a plugin/MCP connection.
2. Use the endpoint below with no DEEPBOM authentication.
3. Attach one supported model, enable the connection in a new chat, and ask DEEPBOM to analyze it.
4. When the widget displays Static evidence ready, choose Report in chat.

https://deepbom.org/mcp

The attachment already belongs to your ChatGPT conversation. DEEPBOM parses it in the host's browser sandbox and returns bounded evidence. Save via ChatGPT provides generated export downloads; Send PNG to chat shares a picture. For ChatGPT desktop, use this connection only if that client exposes the required plugin features.

On a Claude client with custom connectors and MCP App support, add the following endpoint. No DEEPBOM account is required.

https://deepbom.org/mcp/claude

Ask to open the analyzer, then select the file inside the app. Claude attachments are not read automatically. This path currently provides static results and a model-summary table; use the website or local tools for diagram and BOM exports.

Prepared for host testing; directory approval and compatibility with every Claude client are not claimed.

Configure your client's local MCP command as:

npx -y deepbom@1.103.0 mcp

Set the process's working directory to your model folder, or set DEEPBOM_MCP_ALLOWED_ROOTS to an existing absolute directory. In clients such as Gemini CLI, use that client's MCP settings; this does not imply an official extension-store listing or a tested host integration.

Available tools: deepbom_capabilities, deepbom_audit, deepbom_diff, and deepbom_explain_rule. A server waiting on standard input is normal; the MCP client sends the requests.