Install
Two of these write the configuration for you. The rest are a line of JSON or a command, depending on where your agent keeps its servers.
One click
Those two links carry the whole server definition in their payload, so the editor opens with the form already filled in.
As a dev dependency
npm install --save-dev @modootoday/pmcp
Installing it is optional. Every configuration below runs it through
npx -y @modootoday/pmcp, which works with nothing installed; adding it
to the project pins the version your team gets.
A host that spawns servers over stdio
{
"mcpServers": {
"pmcp": { "command": "npx", "args": ["-y", "@modootoday/pmcp"] }
}
}
That is the shape most hosts read. The file it goes in differs by host, and the two commands below write it for you.
Claude Code
claude mcp add pmcp -- npx -y @modootoday/pmcp
VS Code, from a script
code --add-mcp '{"name":"pmcp","command":"npx","args":["-y","@modootoday/pmcp"]}'
The same thing the badge does, for setting up a workstation rather than clicking through one.
Options the server takes
--root <dir> |
a node_modules directory to walk, instead of
discovering upwards from the working directory; repeatable
|
--scope <prefix> |
only packages whose names start with this; repeatable, and takes a comma-separated list |
Both go in the args array beside pmcp. A host
that passes them with no command still gets the server, because a bare
spawn is what the protocol expects.
What arrives
- Node 22 or later, or Bun 1.3 or later.
-
Two runtime dependencies:
@modelcontextprotocol/serverandzod, both MIT. - No postinstall hook, and nothing downloaded at install time. Semantic ranking needs an optional peer you install yourself.
Check it before you trust it.
npx -y @modootoday/pmcp list prints what the server would see from
this directory, and exits 1 rather than 0 when that is nothing.
The five-minute version.