@kongyo2/npm-info-mcp-server
by kongyo2
README.md
# @kongyo2/npm-info-mcp-server
[](https://www.npmjs.com/package/@kongyo2/npm-info-mcp-server)
[](https://github.com/kongyo2/npm-info/actions/workflows/ci.yml)
[](https://deepwiki.com/kongyo2/npm-info)
MCP server that provides npm package information for AI agents during TypeScript development.
npm パッケージ情報を提供する MCP サーバー。AI エージェントが TypeScript 開発中に npm レジストリを参照できます。
## Tools
| Tool | Description | Parameters |
| -------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `npm_search` | Search packages | `query`, `limit` (1-30, default 10) |
| `npm_package_info` | Get package details | `package_name` |
| `npm_package_versions` | List versions | `package_name`, `limit` (1-100, default 20) |
| `npm_package_dependencies` | Get dependencies | `package_name`, `version` (version, dist-tag, or range), `depth` (1-5, default 1), `include_dev`, `include_peer`, `include_optional` (all default true) |
| `npm_package_readme` | Fetch README | `package_name` |
| `npm_package_types` | Check TypeScript type definitions | `package_name`, `version` (version, dist-tag, or range) |
| `npm_package_score` | Get quality / popularity / maintenance score | `package_name` |
`version` defaults to `latest`. With `depth` above 1, `npm_package_dependencies` walks the production tree (`dependencies` plus `optionalDependencies`, marked `(optional)`) regardless of the `include_*` flags, which only shape the direct-dependency listing; resolution stops after 200 packuments or 20 seconds and says so.
## Setup
```json
{
"mcpServers": {
"npm-info": {
"command": "npx",
"args": ["-y", "@kongyo2/npm-info-mcp-server"]
}
}
}
```
## MCP Client Configuration
### Claude Code
Install via CLI (MCP only):
```bash
claude mcp add --scope user npm-info -- npx -y @kongyo2/npm-info-mcp-server
```
### Codex
```bash
codex mcp add npm-info -- npx -y @kongyo2/npm-info-mcp-server
```
## Development
```bash
npm install
npm run dev # Start dev server
npm test # Run unit tests
npm run check # Type check, lint & format
npm run build # Build
```
## License
MIT
TDQS
A4.2/5.0
Scored across 7 tools
Disambiguation5/5
Each tool targets a distinct aspect of npm packages: dependencies, metadata, readme, scores, types, versions, and registry search. No two tools overlap in purpose.
Naming Consistency4/5
Six tools follow the pattern 'npm_package_<action>', but one uses 'npm_search' instead of 'npm_package_search'. This minor inconsistency does not hinder understanding.
Tool Count5/5
Seven tools cover the essential operations for an npm info server without being excessive. The scope is well-defined and each tool serves a clear function.
Completeness5/5
The tool set provides comprehensive coverage of npm package information: metadata, versions, readme, dependencies, type definitions, quality scores, and registry search. No obvious gaps for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues