npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@iqsteel/mcp-bridge

v0.19.0

Published

MCP server bridging Claude Desktop (or any MCP client) to a running iQSteel / ifc-viewer browser tab via WebSocket.

Downloads

101

Readme

@iqsteel/mcp-bridge

MCP server that bridges Claude Desktop (or any MCP client) to a running ifc-viewer browser tab via WebSocket.

How it works

Claude Desktop  ←(stdio MCP)→  @iqsteel/mcp-bridge  ←(WebSocket)→  ifc-viewer tab
  • The viewer (browser) opens the WebSocket as a client — browsers can't listen() on a port.
  • The bridge opens a WebSocket server on 127.0.0.1:<port> and waits for the viewer to dial in.
  • Authentication uses a pairing token displayed in the viewer's Settings → MCP section. The same value goes into the bridge CLI args and the Claude Desktop config.

Step 7 (current): read-only toolslist_models, get_model_summary, get_spatial_tree, get_element, query_elements, get_selection, get_camera_state.

Write tools (select_elements, set_visibility, focus_camera, set_color, run_script) land in Step 8 — gated per-tool from Settings.

Install / run

The bridge is published to npm so Claude Desktop can spawn it via npx:

npx -y @iqsteel/mcp-bridge --port 7800 --token <paired-token>

--token is required. Get it from ifc-viewer → AI tab → Settings → MCP section → Pairing token.

Claude Desktop config

Add to claude_desktop_config.json (under mcpServers):

{
  "mcpServers": {
    "iqsteel": {
      "command": "npx",
      "args": ["-y", "@iqsteel/mcp-bridge", "--port", "7800", "--token", "PASTE_TOKEN_HERE"]
    }
  }
}

Config locations:

| OS | Path | |---------|------------------------------------------------------------| | macOS | ~/Library/Application Support/Claude/claude_desktop_config.json | | Windows | %APPDATA%\Claude\claude_desktop_config.json |

Restart Claude Desktop after editing.

Connecting

  1. Open the viewer in your browser.
  2. Open AI tab → Settings → expand the MCP section. Copy the pairing token.
  3. Paste it into the Claude Desktop config (or run the bridge directly).
  4. Restart Claude Desktop. The bridge spawns, waits for the viewer.
  5. In the viewer, click Connect in the MCP section. Status flips to "✓ Connected to bridge."
  6. In Claude Desktop, ask it to call any of the read tools — e.g. "List the IFC models loaded in the viewer."

If the viewer is closed or refreshed, click Connect again. The bridge stays alive until Claude Desktop closes it.

Security notes

  • The bridge listens on 127.0.0.1 only — no remote network access. Use --host 0.0.0.0 only if you understand the implications (anyone on your network could connect to your viewer).
  • The pairing token is a 32-char base64url secret. Treat it like a password. Revoke from the viewer when you're done; the bridge will refuse the old token afterwards.
  • Read tools are safe — they read viewer state, no mutations. Write tools (Step 8) are gated by an explicit toggle.

Troubleshooting

| Symptom | Likely cause | |----------------------------------|--------------------------------------------------------------| | Bridge refused: code 4401 | Token mismatch. Re-copy from viewer Settings. | | connect ECONNREFUSED | Bridge not running, or wrong port. | | Tools time out (30s) | Viewer hasn't connected yet (click Connect in Settings). | | Claude Desktop doesn't see tools | Restart Claude Desktop after editing the config file. |