Skip to main content
Glama

Related Servers

Alternatives to NPM Context Agent MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to search the npm registry and retrieve package metadata, READMEs, download stats, GitHub details, and usage snippets via the Model Context Protocol.
      9
      6 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables querying NPM package download statistics, metadata, and dependency information through natural language.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching npm packages, retrieving package details and version histories, and fetching download statistics through the npm Registry API.
      367 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and other MCP clients to retrieve real-time documentation, type signatures, and code examples for any npm package, with intent-aware formatting, version and migration diffs, error diagnosis, package comparison, and dependency scanning. Results are pulled on demand from npm, CDNs, and GitHub with BM25 search over 25 concept synonym clusters and production-grade caching and retry logic.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and other MCP clients to retrieve context-aware documentation, type signatures, and code examples for any npm package, along with cross-version migration guides, error diagnosis, package comparison, and dependency scanning. Results are formatted to match query intent and drawing on real package types, changelogs, and GitHub docs.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and compatible MCP clients to retrieve real-time documentation, TypeScript signatures, prose, and code examples for any npm package, with natural-language search, version migration guidance, error diagnosis, package comparison, and dependency scanning.
      MIT

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific aspects of npm package analysis, with no ambiguity or overlap. For example, get_package_info provides general metadata while get_package_quality focuses on npms.io metrics, and get_package_size handles bundlephobia data.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout, using descriptive action verbs like 'get', 'search', and 'compare' paired with specific nouns. This creates a predictable and readable naming convention across all nine tools.

    Tool Count5/5

    Nine tools is well-scoped for npm package analysis, providing comprehensive coverage without bloat. Each tool earns its place by addressing distinct aspects like metadata, dependencies, versions, quality metrics, and search functionality.

    Completeness4/5

    The tool set provides excellent coverage for npm package research and comparison, including search, metadata, dependencies, versions, quality metrics, and bundle analysis. Minor gaps might include package installation/management operations or deeper GitHub integration beyond README access, but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues