GenPM

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.