What can you do with this server?

This server provides an MCP interface to the npm registry, offering the following tools: * get_readme_from_npm: Fetches a package's README (with GitHub fallback) and optionally extracts usage examples. Supports specific versions and dist-tags. * get_package_info_from_npm: Returns detailed metadata, version info, download statistics, and optionally runtime and/or dev dependencies for a package. * search_packages_from_npm: Searches the npm registry by keyword/query, with control over result count (1–250) and optional filtering by minimum quality and popularity scores. Additionally, you can configure a GitHub personal access token to improve API rate limits when fetching READMEs from GitHub, and customize caching TTL and per-request timeouts.

Which integrations are available for this server?

Fetches npm package READMEs, metadata, and search results from the npm registry. Provides tools for retrieving package readmes, package info, and searching for packages.

How do I use @bradford-tech/npm-package-readme-mcp-server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@bradford-tech/npm-package-readme-mcp-server show me the readme for lodash" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

@bradford-tech/npm-package-readme-mcp-server

An MCP server that exposes npm registry data — package READMEs, metadata, and search — to MCP-compatible AI clients.

This is a maintained fork of naoto24kawa/npm-package-readme-mcp-server, republished under the @bradford-tech scope after the original was removed from GitHub and npm. No functional changes from the upstream 0.1.4 release.

Install

npm install -g @bradford-tech/npm-package-readme-mcp-server

Also works with pnpm add -g, yarn global add, or via npx (no install needed).

Related MCP server: npm-docs-server

Configure your MCP client

Add the server to your client's MCP configuration:

{
  "mcpServers": {
    "npm-package-readme": {
      "command": "npm-package-readme-mcp-server"
    }
  }
}

Or run on demand with npx:

{
  "mcpServers": {
    "npm-package-readme": {
      "command": "npx",
      "args": ["-y", "@bradford-tech/npm-package-readme-mcp-server"]
    }
  }
}

Tools

The server exposes three tools to the connected client.

`get_readme_from_npm`

Fetches a package's README and extracts usage examples. Reads from the npm registry first, falls back to the linked GitHub repository.

Parameter	Type	Default	Description
`package_name`	string	—	The npm package name (required).
`version`	string	`"latest"`	Specific version or dist-tag.
`include_examples`	boolean	`true`	Parse and return usage examples extracted from the README.

Example call:

{ "package_name": "react", "version": "18.2.0" }

`get_package_info_from_npm`

Returns package metadata and download statistics for the latest version.

Parameter	Type	Default	Description
`package_name`	string	—	The npm package name (required).
`include_dependencies`	boolean	`true`	Include runtime dependencies.
`include_dev_dependencies`	boolean	`false`	Include dev dependencies.

Example call:

{ "package_name": "express", "include_dependencies": true }

`search_packages_from_npm`

Searches the npm registry.

Parameter	Type	Default	Description
`query`	string	—	Search text (required).
`limit`	number	`20`	Max results, 1–250.
`quality`	number	—	Minimum quality score, 0–1.
`popularity`	number	—	Minimum popularity score, 0–1.

Example call:

{ "query": "testing framework", "limit": 10 }

How package data is fetched

Package metadata and READMEs come from registry.npmjs.org.
If the registry response has no README, the server resolves the repository field and fetches the README from the GitHub API.
Download statistics come from api.npmjs.org/downloads.
Responses are cached in memory (default TTL: 1 hour; search results: 10 minutes).

GitHub anonymous API requests are rate-limited to 60/hour. The server logs a warning when no token is available but still works for low-volume use.

Configuration

All settings are optional environment variables, passed via your MCP client's env field (or your shell, when launching directly).

Variable	Default	Description
`CACHE_TTL`	`3600`	Default cache TTL in seconds for `get_readme_from_npm` and `get_package_info_from_npm`. Search results have a fixed 10-minute TTL.
`REQUEST_TIMEOUT`	`30000`	Per-request timeout in milliseconds, applied to npm registry and GitHub API calls.
`GITHUB_TOKEN`	—	GitHub personal access token. Raises the GitHub API rate limit from 60/hour to 5000/hour.
`LOG_LEVEL`	`INFO`	One of `ERROR`, `WARN`, `INFO`, `DEBUG` (case-insensitive). Invalid values silently fall back to `INFO`. Logs are written to `stderr`.

Example, with a GitHub token:

{
  "mcpServers": {
    "npm-package-readme": {
      "command": "npm-package-readme-mcp-server",
      "env": {
        "GITHUB_TOKEN": "ghp_..."
      }
    }
  }
}

Requirements

Node.js >= 20

Contributing

Issues and pull requests welcome at bradford-tech/npm-package-readme-mcp-server. See CONTRIBUTING.md for the developer setup.

License

MIT. See LICENSE.

Available Tools

3 tools

get_package_info_from_npmB

Get package basic information and dependencies from npm registry

Inputs: package_name (required), include_dependencies, include_dev_dependencies.

get_readme_from_npmB

Get package README and usage examples from npm registry

Inputs: package_name (required), version, include_examples.

search_packages_from_npmB

Search for packages in npm registry

Inputs: query (required), limit, quality, popularity.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A3.6/5.0

Scored 2026-09-09 18:30 across 3 tools

Disambiguation5/5

Each tool targets a clearly distinct operation: searching for packages, retrieving package metadata, and fetching README content. There is no ambiguity between searching and retrieving specific package resources.

Naming Consistency5/5

All three tool names follow a consistent verb_noun_from_npm pattern (get_readme, get_package_info, search_packages). The verb choice appropriately reflects each action, and the structure is uniform throughout.

Tool Count4/5

Three tools is on the lean side, but the server has a narrow, focused purpose (npm package readme retrieval), so each tool earns its place. The count feels slightly thin rather than excessive or insufficient.

Completeness4/5

The core workflow is covered: search for a package, inspect its metadata, then fetch its README. Minor gaps exist, such as fetching version-specific readmes or resolving readmes from alternate sources, but there are no dead ends for the stated purpose.

Maintenance

ActivityNo data

ResponsivenessOutdated data

Resources

Related MCP Connectors

NpmA
io.github.pipeworx-io
npm MCP — wraps the npm Registry API (free, no auth)
Developer Tools Search API Testing
492
https://gateway.pipeworx.io/npm/mcp
Npm Package Info Mcp
io.github.varvararatta
Dive into the world of npm with our NPM Package Info MCP. Access crucial metadata about any npm
Developer Tools Search
2
https://npm-package-info-mcp.mcpize.run/mcp
UNPKGA
io.github.unpkg
Live npm and UNPKG data for AI agents: resolution, audits, import maps, malware/CVE checks.
Developer Tools Security Code Analysis
1411
https://mcp.unpkg.com/mcp
SkillAgentA
dev.skillagent
Search and fetch AI agent skills, rules files and MCP servers indexed from GitHub.
Autonomous Agents Developer Tools Search
41
https://skillagent.dev/mcp

Related MCP Servers

npm-search-mcp-server
Search Developer Tools
btwiuse
A
license
C
quality
D
maintenance
MCP server for searching npm packages
Updated 9 months ago (2026-02-20 23:48 UTC)
1
252 npm
16
MIT
npm-docs-server
Documentation Access Developer Tools
bsmi021
A
license
Not graded
quality
D
maintenance
Fetches metadata and README documentation for NPM packages, with local caching via SQLite for improved performance.
Updated 2 years ago (2025-04-03 21:42 UTC)
3
MIT
@kongyo2/npm-info-mcp-server
Developer Tools Code Analysis
kongyo2
A
license
A
quality
F
maintenance
MCP server that provides npm package information for AI agents during TypeScript development.
Updated 2 months ago (2026-09-21 07:13 UTC)
7
9 npm
1
MIT
mcp-npm-tools
Developer Tools Code Analysis
rog0x
A
license
A
quality
D
maintenance
MCP server providing npm registry search, package details, dependency auditing, bundle size estimation, and package comparison tools for AI agents.
Updated 8 months ago (2026-03-21 20:21 UTC)
5
39 npm
MIT

@bradford-tech/npm-package-readme-mcp-server

Install

Configure your MCP client

Tools

get_readme_from_npm

get_package_info_from_npm

search_packages_from_npm

How package data is fetched

Configuration

Requirements

Contributing

License

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

npm-search-mcp-server

npm-docs-server

@kongyo2/npm-info-mcp-server

mcp-npm-tools

`get_readme_from_npm`

`get_package_info_from_npm`

`search_packages_from_npm`