📦 NPM Helper - A tool to help your ai assistant with npm package management.🤖

Created By
pinkpixel-deva 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 AI assistants with NPM package management and dependency updates, enabling seamless interaction with npm packages.

How to use NPM Helper?

To use NPM Helper, you can run it via npx or install it locally. Configuration involves adding the server command to your MCP client application.

Key features of NPM Helper?

  • npm-check-updates Tools: Check for outdated dependencies, upgrade packages, resolve conflicts, and set version constraints.
  • NPM Search Tools: Search for npm packages, fetch package content, and retrieve version history.

Use cases of NPM Helper?

  1. Automating dependency updates in JavaScript projects.
  2. Assisting AI applications in managing npm packages.
  3. Providing insights into package versions and metadata.

FAQ from NPM Helper?

  • Can NPM Helper manage all npm packages?

Yes! It can handle any npm package as long as it follows the npm registry standards.

  • Is NPM Helper free to use?

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

  • How does NPM Helper ensure safe upgrades?

It uses the Model Context Protocol to safely manage upgrades and resolve conflicts.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pinkpixel-dev
Star
3
Language
JavaScript
License
MIT license

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