# GenPM [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/GenPM-net/genpm  
**GitHub Stars:** 0  
**npm Downloads (last month):** 483  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/genpm

## Description
Search, inspect and inject full source modules (code + AI rules + MCP) pinned to a Git commit.

## Tools
Capabilities this server exposes over MCP:

- **genpm_search** — Search the GenPM registry for injectable architecture modules (code + AI rules + MCP). Use before installing anything.
- **genpm_info** — Get the resolved manifest, dependencies, env vars, MCP servers and AI rules of a GenPM package, plus whether it is already installed here.
- **genpm_add** — Inject a GenPM package (and its GenPM dependencies), or every package of a recipe, into the project. ALWAYS call with dryRun:true first and show the plan to the user.
- **genpm_list** — List GenPM packages installed in this project with local modifications (drift).
- **genpm_remove** — Remove an installed GenPM package. Fails with E_DRIFT if the user modified its files; never deletes modified code silently.
- **genpm_outdated** — Compare installed GenPM packages with the latest published versions.
- **genpm_diff** — Unified diff between the installed version and a newer one, with paths remapped to where the package lives in this project, plus the local changes (drift). Use it to update a package while keeping the user's edits: apply the patch semantically, then call genpm_update with strategy "ai".
- **genpm_update** — Update an installed package. strategy "3way" merges upstream changes with local edits on disk (conflicts stay with <<<<<<< markers and are listed). strategy "ai" writes no files: use it only after you applied the genpm_diff patch yourself, to record the new version in genpm.lock. Call with dryRun:true first and show the plan to the user.
- **genpm_audit** — Verify integrity, registry signatures, security advisories and yanked versions. Run it before modifying installed packages and tell the user about any finding.
- **genpm_validate** — Validate a GenPM package being authored here (genpm.json, AI rules, files, security scan) before publishing.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "genpm": {
    "command": "npx",
    "args": ["-y","@genpm-net/mcp"]
  }
}
```

## Documentation

## What GenPM MCP server does

The GenPM MCP server connects an AI agent to GenPM’s module registry and project injection workflow. It helps an agent search for modules, inspect what a module contains, show an installation plan, and apply the selected module to the current project. GenPM packages can include source code, AI guidance, and MCP server configuration.

The GenPM MCP server is useful when you want imported functionality to become part of your repository instead of remaining behind a package-manager abstraction. Source files are placed under project paths such as `src/`, where they can be reviewed, changed, and committed with the rest of the application.

## How it works

GenPM resolves modules and their dependencies, then fetches them from Git revisions identified by 40-character commit SHAs. The resulting files are injected into the project, and a lockfile records the resolved state. MCP connections included by a module are added only after user consent.

Each module can provide an `AGENTS.md` file and rule files for Cursor, Copilot, Windsurf, and Claude Code. These files are located with the module so an AI agent can receive relevant instructions when working in that directory. GenPM scans AI rules for prompt injection, verifies downloaded content, and does not run package code or install scripts.

The MCP server is part of the native `genpm` binary. Agents can invoke it after registering `genpm mcp serve`; the `genpm mcp setup` command can write configuration for detected AI clients. A separate `npx -y @genpm-net/mcp` package is available when using the Node.js implementation.

## Setup and configuration

Install the native CLI on macOS or Linux with the project’s shell installer, or on Windows with its PowerShell installer. Homebrew, Scoop, npm, and npx installation paths are also documented by GenPM. The native binary does not require Node.js.

After installation, run `genpm mcp setup` to generate configuration for detected clients, or register the server manually. For Claude Code, the documented form is `claude mcp add genpm -- genpm mcp serve`. Cursor, VS Code, Windsurf, and Codex setup instructions are provided in the MCP documentation.

## Tools and capabilities

The GenPM MCP server supports workflows for:

- Searching the available module catalog.
- Inspecting module source, AI rules, MCP configuration, and dependencies.
- Showing a proposed installation plan before changes are applied.
- Injecting modules and resolved dependencies into a project.
- Pinning installed content to Git commit SHAs.
- Adding module MCP connections only with consent.

Developers can also publish modules separately through `genpm init`, `genpm validate`, and `genpm publish`. Published source remains on GitHub while the registry stores metadata.

## Limitations and notes

The registry and website are separate parts of the repository from the client packages. The client packages, including the MCP package, are MIT-licensed; the registry and website are all rights reserved. The project does not run package code or installation scripts, so modules that depend on those execution steps may require manual handling after injection.

The Node.js MCP package requires Node.js. The native binary avoids that requirement, but development of the repository itself requires Node 22.12 or newer, pnpm 10, and Git 2.25 or newer. Module connections are not added automatically without consent, and writes are restricted to the project.

_Full upstream README: https://allmcps.com/mcp/genpm/readme_