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

@blinkpage/mcp

v0.3.5

Published

Blinkpage MCP server. Exposes `list_projects` and `upload_component` over stdio for LLM clients (Claude Desktop, Cursor, Cline).

Readme

@blinkpage/mcp

Stdio MCP server for Blinkpage. Lets an LLM client (Claude Desktop, Cursor, Cline) list a user's Blinkpage projects and upload custom components built from TSX or raw HTML.

Tools

| Tool | Purpose | |------|---------| | list_projects | List the user's projects (resources). Returns { id, name }[]. | | upload_component | Build a TSX or HTML component locally and upload it to a project. |

Install

The server is intended to be launched by an MCP client over stdio.

# from a published npm package (once published)
npx -y @blinkpage/mcp

For local development inside the Blinkpage monorepo:

cd blinkpage-mcp-server
npm install
npm run build
node dist/index.js   # waits for stdio frames

Claude Desktop config

Add this to your Claude Desktop claude_desktop_config.json:

{
  "mcpServers": {
    "blinkpage": {
      "command": "npx",
      "args": ["-y", "@blinkpage/mcp"],
      "env": {
        "BLINKPAGE_TOKEN": "bpat_<your-64-hex-personal-access-token>",
        "BLINKPAGE_API_URL": "https://api.blinkpage.com"
      }
    }
  }
}

Issue a Personal Access Token from the Blinkpage app (Settings → Developer → PATs). The token is shown exactly once at creation time.

Environment variables

| Name | Required | Description | |------|----------|-------------| | BLINKPAGE_TOKEN | yes | Personal access token (bpat_<64hex>). | | BLINKPAGE_API_URL | yes | Base URL of the Blinkpage backend (no trailing slash). | | BLINKPAGE_LOG_LEVEL | no | debug | info | warn | error. Default info. |

If either of the required vars is missing the server logs a single error line to stderr and exits non-zero.

Logging

All logs go to stderr. stdout is reserved for the MCP JSON-RPC transport; writing to it from anywhere in the process would corrupt the connection. Set BLINKPAGE_LOG_LEVEL=debug to see request URLs and tool args.

Scripts

| Script | Purpose | |--------|---------| | npm run build | Compile TS → dist/. | | npm run dev | Same, with --watch. | | npm run start | Run the compiled dist/index.js. | | npm run smoke | Spawn the server, send a tools/list frame, assert both tools register. |