Skip to main content
Glama
YawLabs

@yawlabs/npmjs-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @yawlabs/npmjs-mcp

No user-submitted related servers found.

    Related Servers

    • @mgcrea/mcp-npm

      mgcrea
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to interact with the npm registry, covering package intel, dist-tags, trusted publisher configuration, access and team governance, tokens, security advisories, and publishing, with read-only tools by default.
      3
      15 npm
      MIT

    • npmswitch

      ApiCartOps
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to work with the npm registry across multiple named accounts, routing each call to the right token based on an explicit account, a matching package scope, or the default. Offers read tools for search, package details, downloads and account listing, plus confirmation-guarded write tools for publishing, deprecating and managing dist-tags.
      256 npm
      MIT

    • dev.augments/mcp

      Szymanski8483
      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

    • Augments MCP Server

      sRamirez9016
      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.
      -

    • dev.augments/mcp

      hunt0542
      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.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 64 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, with clear boundaries between metadata, downloads, security, teams, and hooks. A few auth-focused tools (npm_whoami, npm_profile, npm_verify_token, npm_check_auth) and download variants (npm_downloads, npm_downloads_range, npm_downloads_bulk) could be confused, but the descriptions help disambiguate them.

    Naming Consistency4/5

    The npm_ prefix and snake_case are consistent, and most tools follow a resource-first pattern (npm_team_create, npm_hook_add, npm_dist_tag_set). However, a handful of action-first verbs (npm_search, npm_compare, npm_audit) and bare nouns (npm_health, npm_tokens) break the pattern, creating minor inconsistency.

    Tool Count2/5

    64 tools is far beyond the well-scoped 3-15 range. Even for the broad npm registry API, this is excessive; an agent must parse many near-synonymous entries, and several groups (downloads variants, auth checks, team management) could be consolidated into fewer, more parameterized tools.

    Completeness4/5

    The server covers most of the npm registry domain: metadata, search, downloads, security, auth, teams, orgs, hooks, dist-tags, and unpublishing. The main gap is the absence of an actual npm_publish tool (only npm_publish_preflight exists), and token creation is deliberately omitted, so publishing workflows require a human handoff.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources