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

@optilogic/mcp-ui

v0.2.1

Published

MCP Apps UI bridge for Optilogic widgets - postMessage host client, React hooks, and WidgetRoot for building sandboxed opti-ui widgets embedded in Claude

Downloads

285

Readme

@optilogic/mcp-ui

The bridge for building MCP Apps widgets — self-contained HTML UIs that Claude (and other MCP hosts) embed in a sandboxed iframe. It handles the boring, spec-defined parts so a widget is just an opti-ui component plus a data hook:

  • Host client — a typed postMessage / JSON-RPC transport that speaks the MCP Apps app↔host protocol (handshake, render-data delivery, tool callbacks, host context).
  • React hooksuseMcpData() (the tool's render data), useHostTheme() (host light/dark → opti-ui theme), useCallTool() (call a server tool back through the host).
  • <WidgetRoot> — wraps a widget: runs the handshake, injects @optilogic/core styles + theme, and renders loading / error states so every widget doesn't re-solve them.
  • @optilogic/mcp-ui/testing — a mock host for developing and Storybook-testing widgets offline, with no MCP host in the loop.

Widgets themselves live in the server that owns their tool data contracts (e.g. opti-mcp/web/widgets/*), not here. This package ships the reusable plumbing + the components they render come from @optilogic/charts / @optilogic/core.

Trust boundary

Everything arriving over postMessage is untrusted input. The transport validates every inbound message with hand-written type guards (unknown → narrowed) before it reaches widget code — never a cast. See src/protocol/.

Status

Foundation phase (opti-ui-foundation). The wire contract is being reconciled against the live MCP Apps spec; the transport's message format is isolated in src/protocol/ as the single swap-point.