Npm Helper

Created By
Pink Pixela year ago
A Model Context Protocol (MCP) server providing tools for NPM package management and dependency updates. Helps LLMs like Claude interact with npm packages, search npm registry, and keep dependencies up-to-date.
Overview

What is NPM Helper?

NPM Helper is a Model Context Protocol (MCP) server designed to assist with NPM package management and dependency updates, enabling LLMs like Claude to interact with npm packages, search the npm registry, and maintain up-to-date dependencies.

How to use NPM Helper?

To use NPM Helper, you can run it using npx or install it locally. For npx, use the command: npx -y @pinkpixel/npm-helper-mcp. For local installation, run npm install -g npm-helper-mcp and configure it in your MCP client application.

Key features of NPM Helper?

  • Dependency Management: Tools for checking and upgrading outdated dependencies.
  • Conflict Resolution: Handles dependency conflicts effectively.
  • NPM Search: Search for packages and retrieve detailed information from the npm registry.
  • Version Control: Set version constraints and manage upgrades safely.

Use cases of NPM Helper?

  1. Automating the upgrade of project dependencies.
  2. Searching for new npm packages to integrate into projects.
  3. Ensuring compatibility of dependencies in large projects.

FAQ from NPM Helper?

  • Can NPM Helper manage all npm packages?

Yes! It can manage any npm package available in the npm registry.

  • Is NPM Helper free to use?

Yes! NPM Helper is open-source and free for everyone.

  • How does NPM Helper handle dependency conflicts?

It provides tools to resolve conflicts by checking peer dependencies and suggesting compatible versions.

Server Config

{
  "mcpServers": {
    "npm-helper": {
      "command": "npx",
      "args": [
        "-y",
        "@pinkpixel/npm-helper-mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Pink Pixel
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago