NPMLens MCP: a server exposing tools to search npm packages and fetch READMEs.
NPMLens MCP: a server exposing tools to search npm packages and fetch READMEs. Exposed over MCP by the npmlens mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
npmlens-mcp lets your coding agent (such as Claude, Cursor, Copilot, Gemini or Codex) search the npm registry and fetch package context (README, downloads, GitHub info, usage snippets). It acts as a Model‑Context‑Protocol (MCP) server, giving your AI assistant a structured way to discover libraries and integrate them quickly.
Everything the assistant can do here goes through one of these:
search_npm — The search_npm tool exposed by this serverget_readme — The get_readme tool exposed by this serverget_package_info — The get_package_info tool exposed by this serverget_downloads — The get_downloads tool exposed by this serverget_usage_snippet — The get_usage_snippet tool exposed by this serverget_package_versions — The get_package_versions tool exposed by this serverget_package_dependencies — The get_package_dependencies tool exposed by this servercompare_packages — The compare_packages tool exposed by this serversearch_by_keywords — The search_by_keywords tool exposed by this servernpmlens-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: GITHUB_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
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. Npmlens MCP's toolset — search_npm, get_readme, get_package_info 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.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search_npm | The search_npm tool exposed by this server. |
| get_readme | The get_readme tool exposed by this server. |
| get_package_info | The get_package_info tool exposed by this server. |
| get_downloads | The get_downloads tool exposed by this server. |
| get_usage_snippet | The get_usage_snippet tool exposed by this server. |
| get_package_versions | The get_package_versions tool exposed by this server. |
| get_package_dependencies | The get_package_dependencies tool exposed by this server. |
| compare_packages | The compare_packages tool exposed by this server. |
| search_by_keywords | The search_by_keywords tool exposed by this server. |
{
"mcpServers": {
"npmlens": {
"command": "npx",
"args": ["-y", "npmlens-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.