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

linkedin-toolkit-mcp

v2.1.1

Published

MCP server, localhost bridge, HTTP action API, SQLite mirror and lit CLI for LinkedIn Toolkit.

Readme

linkedin-toolkit-mcp

The MCP server, localhost bridge, HTTP action API, SQLite mirror and lit CLI for LinkedIn Toolkit.

This package is the half that agents talk to. The other half is a Chrome extension that drives your own logged-in LinkedIn session — there is no headless browser, no hosted service, no account and no telemetry. This server does not touch LinkedIn itself; it hands actions to the extension over a WebSocket on loopback and passes the answers back.

npx linkedin-toolkit-mcp

Pairing

  1. Install the extension: download the linkedin-toolkit-extension-*.zip from Releases, unzip it, then chrome://extensions → Developer mode → Load unpacked → pick the folder.
  2. Run npx linkedin-toolkit-mcp. The first run prints a pairing token and stores it in ~/.linkedin-toolkit/config.json (owner-only).
  3. Paste that token into the extension popup → Settings → Local bridge, and enable the bridge. The badge turns to "connected".

Point your agent at the server. Claude Code, .mcp.json in your project root:

{
  "mcpServers": {
    "linkedin-toolkit": { "command": "npx", "args": ["-y", "linkedin-toolkit-mcp"] }
  }
}

lit serve --http additionally exposes POST /actions/{action}, POST /mcp and GET /openapi.json on 127.0.0.1:47830 for the Node and Python clients, n8n and anything else that speaks HTTP. Everything binds to loopback and requires the pairing token as a bearer token.

Add --fake to any serve to run the whole surface without a LinkedIn account: real envelopes, real error codes, demo data, no network calls.

lit cheat-sheet

lit serve --http                       # run the bridge + HTTP API (add --fake for demo mode)
lit status                             # connection, quotas, business hours, queue depth
lit config get token --reveal          # the pairing token
lit search "CTO fintech London" --json # sourcing; --csv also works
lit profile ada-lovelace --json
lit invite ada-lovelace --note "…"     # queues for approval in Copilot mode
lit queue list                         # what is waiting for you
lit queue approve <id>                 # you, at your own terminal
lit sync && lit sql "select * from profiles limit 5"
lit research rows.csv --out packs/     # research packs from a CSV

lit --help lists everything.

Safety

Copilot mode is on by default: invites, messages, InMails and comments from an agent wait in an approval queue until a human approves them in the popup. Views, follows and likes are metered against the visit bucket and go out directly. Daily hard caps live in the extension and cannot be raised by this server, the CLI, an agent or a config file.

Automating your LinkedIn account may breach LinkedIn's User Agreement, and accounts are restricted and banned for it. That risk is yours. Read docs/safety.md before you point anything at an account you care about.

Documentation

MIT licensed. Issues and pull requests: https://github.com/OpenRecruiterTools/linkedin-toolkit