Connections

Ask your AI to install it.

The GenPM MCP server gives your agent the same engine as the CLI. It can search, inspect and inject modules, and it always asks before touching anything outside your code.

Step 1

Add the server to your client

$claude mcp add genpm -- genpm mcp serve

Or run genpm mcp setup and GenPM writes the config for every client it detects.

No genpm binary? Use npx -y @genpm/mcp instead (needs Node.js).

Then ask

Add GitHub login to this project with genpm.

Find a billing module with Stripe and show me its rules before installing.

Which genpm packages in this repo are outdated?

Step 2

What your agent can do

Eight tools. No publish, login or force: credentials stay outside the agent’s reach.

Tool	What it does
genpm_search	Find packages by need. Sponsored results are never returned to agents.
genpm_info	Read a package: manifest, rules, MCP and scan, before installing.
genpm_add	Plan and inject. Dry run first; asks you before MCP config or npm installs.
genpm_list	What is installed in this project, with versions, SHAs and local changes.
genpm_remove	Remove a package and its rules cleanly; never deletes code you modified.
genpm_outdated	Packages with newer versions available.
genpm_audit	Verify integrity, signatures and security advisories.
genpm_validate	Validate a package you are authoring before publishing.

Safety

Defaults that protect your project

MCP off by default

A package’s MCP servers are only added after you confirm, with the full command shown.

Writes stay in your repo

The server only writes inside the project root, through the same path checks as the CLI.

No npm without you

npm dependencies are proposed, never installed silently.