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

@sajalmishra/markpin

v0.1.1

Published

Visual feedback tool for AI coding agents — click any element to annotate it

Readme

@sajalmishra/markpin

Visual feedback tool for AI coding agents. Click any element on your dev app to leave structured annotations — bugs, improvements, questions. Your AI agent reads them via MCP and fixes the code directly.

Install

npm install @sajalmishra/markpin -D
# or
pnpm add @sajalmishra/markpin -D
# or
yarn add @sajalmishra/markpin --dev

Requirements: React 18+, development builds only (never ship to production)

Quick start

// src/App.tsx
import { Pinpoint } from '@sajalmishra/markpin';

export function App() {
  return (
    <>
      <MyRoutes />

      {/* Dev only — never ships to production */}
      {import.meta.env.DEV && (
        <Pinpoint />
      )}
    </>
  );
}

The toolbar renders into a portal at the bottom of <body> so it won't affect your app's layout or styles.

You also need the MCP server running so your agent can read the annotations:

npx @sajalmishra/markpin-mcp server

Next.js

// app/layout.tsx
import dynamic from 'next/dynamic';

const Pinpoint = dynamic(
  () => import('@sajalmishra/markpin').then(m => m.Pinpoint),
  { ssr: false }
);

export default function RootLayout({ children }) {
  return (
    <html><body>
      {children}
      {process.env.NODE_ENV === 'development' && (
        <Pinpoint />
      )}
    </body></html>
  );
}

Props

| Prop | Type | Default | Description | |------|------|---------|-------------| | endpoint | string | "http://localhost:4747" | MCP server URL. Override if you changed the port. | | sessionId | string | auto | Override the session ID (auto-generated if omitted). | | onAnnotationAdd | (ann: Annotation) => void | — | Called when an annotation is created. | | onAnnotationDelete | (ann: Annotation) => void | — | Called when an annotation is deleted. | | onAnnotationsClear | () => void | — | Called when all annotations are cleared. | | onCopy | (markdown: string) => void | — | Called when annotations are copied as markdown. | | onSessionCreated | (sessionId: string) => void | — | Called once when the session is established. |

Keyboard shortcuts

| Key | Action | |-----|--------| | Cmd/Ctrl+Shift+F | Toggle capture mode | | Esc | Close popup / exit current mode | | P | Pause / resume CSS animations | | H | Toggle marker pin visibility | | C | Copy annotations as markdown | | X | Clear all annotations | | L | Toggle layout mode |

Changing the port

If you start the MCP server on a different port, pass it explicitly:

<Pinpoint endpoint="http://localhost:8080" />

On the server side: markpin-mcp server --port 8080 or PINPOINT_PORT=8080 markpin-mcp server.

Full docs

See the Markpin documentation for guides on watch mode, critique mode, and all MCP tools.