PackageLens MCP: a server exposing tools to search package registries (npm today) and fetch READMEs.
If you already use Packagelens MCP, the packagelens mcp mcp server is the piece that lets your assistant work with it directly. PackageLens MCP: a server exposing tools to search package registries (npm today) and fetch READMEs.
packagelens-mcp lets your coding agent (such as Claude, Cursor, Copilot, Gemini or Codex) search package registries across multiple ecosystems (npm, PyPI, RubyGems, Crates.io, Packagist, Hex) and fetch package context (README, downloads, GitHub info, usage snippets). It features smart ecosystem auto-detection, so your AI can find packages without needing to specify which ecosystem to search. It acts as a Model‑Context‑Protocol (MCP) server, giving your AI assistant a structured way to discover libraries and integrate them quickly.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
smart_package_info — Get detailed package infoArgs — packageName, ecosystem?, context?, includeReadme?Example — "Tell me about react" → detects npmsmart_get_readme — Fetch package READMEsmart_get_usage_snippet — Extract code examples from READMEsmart_get_versions — List package versionssmart_get_dependencies — Get package dependenciessmart_get_downloads — Get download statisticscompare_packages — Compare packages across ecosystemspackagelens-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: GITHUB_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Packagelens MCP's toolset — smart_package_info, Args, Example and 6 more — is a fair guide to whether it matches your workflow. It is maintained by rakeshmenon; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| smart_package_info | Get detailed package info |
| Args | packageName, ecosystem?, context?, includeReadme? |
| Example | "Tell me about react" → detects npm |
| smart_get_readme | Fetch package README |
| smart_get_usage_snippet | Extract code examples from README |
| smart_get_versions | List package versions |
| smart_get_dependencies | Get package dependencies |
| smart_get_downloads | Get download statistics |
| compare_packages | Compare packages across ecosystems |
{
"mcpServers": {
"packagelens": {
"command": "npx",
"args": ["-y", "packagelens-mcp@latest"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GITHUB_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.