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

lantern-connect

v0.3.0

Published

CLI installer to connect AI tools (Claude, Gemini, Cursor) to Lantern

Readme

lantern-connect

CLI installer to connect AI tools to Lantern.

Installation

npx lantern-connect

Or install globally:

npm install -g lantern-connect
lantern-connect

Usage

# Production (default)
lantern-connect

# Local development with ngrok
lantern-connect --mcp-url https://your-ngrok-url.ngrok-free.dev/mcp

Options

| Option | Description | Default | |--------|-------------|---------| | --mcp-url <url> | MCP server URL | https://mcp.onlantern.com/mcp | | --help, -h | Show help message | |

What it does

  1. Detects installed AI tools (Claude Code, Gemini CLI, Cursor)
  2. Configures each detected tool to connect to Lantern's MCP server
  3. Each tool authenticates with Lantern on first use (via OAuth)

Supported Tools

| Tool | Config Location | Method | |------|-----------------|--------| | Claude Code | ~/.claude.json | claude mcp add | | Gemini CLI | ~/.gemini/settings.json | httpUrl config | | Cursor | ~/.cursor/mcp.json | url config |

Claude Web & Desktop

For Claude Web and Claude Desktop, use the built-in custom connector:

  1. Go to Settings → Connectors → Add custom connector
  2. Name it Lantern and paste: https://mcp.onlantern.com/mcp
  3. Click Add, then Connect

After Installation

  1. Fully quit and reopen your AI tools (Cmd+Q on macOS)
  2. Authenticate when prompted by each tool on first use
  3. Start using Lantern:
    • Say "save to lantern" to export a conversation
    • Say "list my lantern conversations" to see your library
    • Say "load my lantern collection" to import a collection

Local Development

# Start your local Lantern backend and MCP server
cd lantern && npm run dev

# Run the CLI with your local MCP server
cd lantern-connect
node bin/lantern-connect.js --mcp-url http://localhost:3002/mcp

Resetting / Uninstall

To remove Lantern configuration from all AI tools at once:

npx lantern-reset

This removes the Lantern MCP server from Claude Code, Gemini CLI, and Cursor. Restart your AI tools after running.

Manual Reset

If you prefer to reset manually:

Claude Code:

claude mcp remove lantern

Claude Web & Desktop: Go to Settings → Connectors and remove the Lantern connector.

Gemini CLI:

nano ~/.gemini/settings.json
# Remove the "lantern" entry from mcpServers, then save

Cursor:

nano ~/.cursor/mcp.json
# Remove the "lantern" entry from mcpServers, then save

Troubleshooting

Gemini CLI shows "Bad Request" for SSE

  • Make sure your backend has the latest MCP session handling code
  • Restart your backend server

Gemini CLI shows "Protected resource does not match"

  • Run npx lantern-reset to clear cached OAuth tokens
  • Then run npx lantern-connect again
  • Or manually delete ~/.gemini/mcp-oauth-tokens.json

CORS errors on localhost:3000

  • Make sure your frontend's .env.local has NEXT_PUBLIC_API_URL=http://localhost:3001
  • The --mcp-url flag is for the CLI/MCP tools, not the frontend