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

@mandelbaum/mrcp

v0.0.1

Published

Small framework for MCP apps with Vite + React.

Readme

mrcp

Small framework for MCP apps with Vite + React.

Conventions

  • Define UI resources (React components) in resources/**.
    • The default export is used as the resource component.
    • The resource name is derived from the file path under resources/ (for example resources/base-ui.tsx -> "base-ui").
  • Define tools (functions) in tools/**.
    • Tool UI linkage is app.resource, which is type-safe against discovered resource names.
  • Vite generates virtual modules:
    • virtual:mcp-resources
    • virtual:mcp-tools
  • Resources are server-rendered and then hydrated in the frontend via resource-hydrate.tsx.
  • Hydration script is injected inline in resource HTML (no external <script src="...">).
  • Tailwind CSS is enabled in Vite for both dev and production builds (production output is pruned automatically by Tailwind).

Commands

npm install
npm run dev

Dev server runs on http://localhost:3001/mcp and hot-loads resources/tools through Vite SSR.

npm run build

Build outputs compiled server code to dist/.

In both dev and production, the full hydration JavaScript is inlined into the resource HTML.

npm run start

Starts the compiled server from dist/server.js.

CLI

This package exposes two binaries:

  • mrcp with commands: dev, build, start, check, generate-types
  • create-mrcp to scaffold a new MRCP app

Example:

npx create-mrcp my-mcp-app
cd my-mcp-app
npm install
npm run dev