Skip to main content
Glama
@kongyo2/npm-info-mcp-server

@kongyo2/npm-info-mcp-server

by kongyo2

@kongyo2/npm-info-mcp-server

npm version CI Ask DeepWiki

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.

Related MCP server: agent-workspace-mcp

Setup

{
  "mcpServers": {
    "npm-info": {
      "command": "npx",
      "args": ["-y", "@kongyo2/npm-info-mcp-server"]
    }
  }
}

MCP Client Configuration

Claude Code

Install via CLI (MCP only):

claude mcp add --scope user npm-info -- npx -y @kongyo2/npm-info-mcp-server

Codex

codex mcp add npm-info -- npx -y @kongyo2/npm-info-mcp-server

Development

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

Available Tools

7 tools
npm_package_dependenciesGet npm Package DependenciesA
Read-onlyIdempotent

Get dependency information for a specific version of an npm package.

By default returns direct dependencies of all kinds (dependencies, devDependencies, peerDependencies, optionalDependencies) along with totals. When depth is greater than 1, resolves the transitive production dependency tree (using the abbreviated packument format and a bounded fetch limiter) and renders it as an ASCII tree with deduplicated nodes.

Args:

  • package_name (string): The npm package name

  • version (string, optional): Specific version to check (defaults to latest)

  • depth (number, optional, 1-5): Transitive production-dep depth (default 1)

  • include_dev (boolean, optional): Include devDependencies (default true; ignored when depth > 1)

  • include_peer (boolean, optional): Include peerDependencies (default true; ignored when depth > 1)

  • include_optional (boolean, optional): Include optionalDependencies (default true; ignored when depth > 1)

Returns:

  • Counts summary (runtime/dev/peer/optional)

  • Direct dependency lists by category

  • When depth > 1: a transitive production-dep tree, deduplicated on resolved version

Examples:

  • "express" -> Express direct dependencies at latest

  • "react", version="18.2.0" -> React 18.2.0 dependencies

  • "express", depth=2 -> Express + its production deps' dependencies

Inputs: package_name (required), depth, version, include_dev, +2 more.

npm_package_infoGet npm Package InfoA
Read-onlyIdempotent

Get comprehensive information about an npm package including latest version, description, license, homepage, repository, keywords, engines, and maintainers.

Args:

  • package_name (string): The npm package name

Returns: Package metadata including:

  • name, latest version, description

  • license, homepage, repository URL

  • keywords, engines (node/npm version requirements)

  • dist-tags (latest, next, beta, etc.)

  • maintainers list

  • author information

Examples:

  • "react" -> React package info with latest version, license, etc.

  • "@anthropic-ai/sdk" -> Anthropic SDK details

Inputs: package_name (required).

npm_package_readmeGet npm Package READMEA
Read-onlyIdempotent

Get the README content of an npm package.

Returns the package's README markdown content, which typically includes installation instructions, usage examples, API documentation, and configuration options.

Args:

  • package_name (string): The npm package name

Returns: README content in markdown format. Large READMEs are truncated to 25000 characters with a notice.

Examples:

  • "zod" -> Zod README with schema validation examples

  • "express" -> Express README with routing examples

Inputs: package_name (required).

npm_package_scoreGet npm Package ScoreA
Read-onlyIdempotent

Get quality, popularity, and maintenance scores for an npm package from npms.io.

Provides detailed metrics including download counts, GitHub stars, test coverage indicators, and release frequency.

Args:

  • package_name (string): The npm package name

Returns: Comprehensive scoring breakdown:

  • Overall score (0-100%)

  • Quality score: carefulness, tests, health, branding

  • Popularity: community interest, downloads, dependents

  • Maintenance: release frequency, commit frequency, open issues

  • GitHub stats: stars, forks, issues

  • Download statistics

Examples:

  • "react" -> High scores across all categories

  • "lodash" -> Well-maintained with high popularity

Inputs: package_name (required).

npm_package_typesCheck npm Package TypeScript SupportA
Read-onlyIdempotent

Check whether an npm package ships TypeScript type definitions.

Detects bundled types from three sources (in priority order):

  1. types field

  2. typings field

  3. exports map with a types condition (modern conditional exports)

Also checks for a DefinitelyTyped (@types/) companion package when no bundled types are found, and surfaces typesVersions (TS-version-specific type maps) when present.

Args:

  • package_name (string): The npm package name

  • version (string, optional): Specific version to check (defaults to latest)

Returns markdown with:

  • Whether bundled types are present and which field declared them

  • Type-definitions entry path

  • Number of subpaths typed via exports (when applicable)

  • Whether a typesVersions map is declared

  • Whether @types/ exists on DefinitelyTyped, plus its latest version

  • An install command when @types is needed

Examples:

  • "express" -> @types/express on DefinitelyTyped

  • "zod" -> Bundled types (TypeScript-first library)

  • "react" -> Bundled types via exports/types condition

Inputs: package_name (required), version.

npm_package_versionsList npm Package VersionsA
Read-onlyIdempotent

List published versions of an npm package with release dates, sorted by most recent first.

Args:

  • package_name (string): The npm package name

  • limit (number): Maximum versions to return, 1-100 (default: 20)

Returns: Version list with publish dates, dist-tags, and deprecation notices. Includes:

  • version number and publish date for each version

  • dist-tags annotation (latest, next, beta, etc.)

  • deprecation warnings where applicable

  • total version count

Examples:

  • "react" -> Lists recent React versions with dates

  • "typescript", limit=5 -> Last 5 TypeScript releases

Inputs: package_name (required), limit.

Tool Schema Changelog

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

Loading tool schema changelog…

    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

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables LLMs to understand and work with TypeScript APIs they haven't been trained on by providing structured access to TypeScript type definitions and documentation.
      34 npm
      46
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A TypeScript-aware MCP server that provides coding agents with repository discovery, code intelligence, and web project context for local codebases. It enables deep symbol navigation, diagnostic reporting, and structural analysis of monorepos without requiring full IDE integration.
      7
      16 npm
      1
      MIT
    • 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.
      5
      39 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server that provides TypeScript type inference and hover information using tsgo, enabling AI agents to get type details, diagnostics, references, and more without needing an editor.
      8 npm
      1
      MIT