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

@splicr/mcp-server

v0.15.1

Published

Splicr MCP server — route what you read to what you're building

Readme

@splicr/mcp-server

Route what you read to what you're building. Splicr captures knowledge from anywhere — articles, tweets, docs, code snippets — and surfaces it inside your coding agent exactly when you need it.

Quick Start

npx @splicr/mcp-server setup

That's it. This will:

  1. Open your browser to sign in (email + verification code, no password)
  2. Auto-detect your coding agents (Claude Code, Cursor, Codex, Cline, Antigravity)
  3. Configure Splicr in each one

One-time login. Token never expires.

Commands

| Command | Description | |---------|-------------| | npx @splicr/mcp-server setup | One-time setup: sign in + auto-configure all agents | | npx @splicr/mcp-server login | Re-authenticate (opens browser) | | npx @splicr/mcp-server uninstall | Remove Splicr from all agents + delete credentials | | npx @splicr/mcp-server help | Show all commands |

Manual Configuration

If you prefer to configure manually, or use an agent that isn't auto-detected, add this to your agent's MCP settings:

{
  "mcpServers": {
    "splicr": {
      "command": "npx",
      "args": ["-y", "@splicr/mcp-server"]
    }
  }
}

Config file locations:

| Agent | Config Path | |-------|-------------| | Claude Code | Run claude mcp add --scope user splicr -- npx -y @splicr/mcp-server | | Cursor | ~/.cursor/mcp.json | | Cline (VS Code) | VS Code settings > Cline MCP | | Antigravity | ~/.gemini/antigravity/mcp_config.json | | Codex | Run codex mcp add splicr -- npx -y @splicr/mcp-server |

MCP Tools

Once connected, your coding agent gets these tools:

| Tool | Description | |------|-------------| | search_knowledge | Semantic search across your saved knowledge | | get_project_context | New captures since last session (watermark-based) | | get_recent_insights | Cross-project view of recent saves | | save_from_agent | Save knowledge back to Splicr from your agent | | retry_failed | Retry captures that failed processing |

How to Capture

  • Telegram: Send any link to @splicr_bot
  • Browser: Chrome extension (coming soon)
  • Mobile: Share sheet app (coming soon)

AI automatically distills each save into an insight, routes it to your active projects, and generates embeddings for semantic search.

Auth

Splicr uses passwordless authentication:

  1. setup opens your browser
  2. Enter your email, get a 6-digit verification code
  3. Enter the code — done. Permanent API token saved to ~/.splicr/auth.json

No passwords. No token refresh. No expiry.

Links