Pi Claude Marketplace

Access Claude plugin marketplaces from Pi Coding Agent.

Features

Installs plugins from the Claude plugin marketplace that contain these components:

• Commands.
• Skills.
• Agents. Requires pi-subagents.
• MCP servers. Requires pi-mcp-adapter.

Plugins that contain unsupported components are marked as "unavailable".

Prerequisites

• Pi Coding Agent
• pi-subagents (optional but recommended, pi install npm:pi-subagents)
• pi-mcp-adapter (optional but recommended, pi install npm:pi-mcp-adapter)

Usage

Install the Pi extension.

pi install npm:pi-claude-marketplace

Bootstrap the offical Claude plugin marketplace (anthropics/claude-plugins-official).

/claude:plugin bootstrap

List plugins available for installation.

/claude:plugin list --available

Install a plugin.

/claude:plugin install pr-review-toolkit@claude-plugins-official

Add another marketplace.

/claude:plugin marketplace add upstash/context7

List its plugins.

/claude:plugin list context7-marketplace --available

Add another plugin.

/claude:plugin context7-plugin@context7-marketplace

Then reload.

/reload

Name mapping

Command and skill names are prefixed with the plugin name. If the command or skill is already prefixed with the plugin name plus -, that common part is elided.

Commands and skill names use Pi's colon form:

Plugin name	Command or skill name	Pi name
foo	bar	/foo:bar
foo	foo-bar	/foo:bar
foo	foo	/foo:foo

Skills additionally use hyphenated generated names after the /skill: prefix:

Plugin name	Skill name	Pi name
foo	bar	/skill:foo-bar
foo	foo-bar	/skill:foo-bar
foo	foo	/skill:foo

MCP server names are not prefixed or rewritten. The server name is the key from the plugin's mcpServers object. If another MCP config already uses that name, the plugin install or update fails.

Plugin name	mcpServers key	Pi MCP server name
foo	api	api
foo	foo-api	foo-api
bar	api	conflict if api already exists

Scoping

Marketplaces and plugins can be installed in the user scope or in the current project's scope. The default is user scope.

The user scope is inherited, so it is possible to install a plugin from a user-scope marketplace in the project scope.

It is also possible to install the same plugin in both user and project scopes; the plugin in the user scope takes precedence.

/claude:plugin reference

This extension mirrors Claude Code's /plugin command. Use /claude:plugin in Pi for marketplace and plugin operations, then run /reload after installing, uninstalling, updating, or reinstalling plugins so Pi discovers the changed resources.

Marketplace

Add a marketplace from a GitHub repository owner/repo shorthand.

/claude:plugin marketplace add upstash/context7

Add the same marketplace from a GitHub URL.

/claude:plugin marketplace add https://github.com/upstash/context7-marketplace

Pin a GitHub marketplace to a branch, tag, or commit with a #ref suffix.

/claude:plugin marketplace add https://github.com/upstash/context7-marketplace#v1.0.30

Add a marketplace from the local filesystem. The path may be a directory containing .claude-plugin/marketplace.json or a direct path to a marketplace.json file.

/claude:plugin marketplace add ~/my-marketplace
/claude:plugin marketplace add ~/my-marketplace/.claude-plugin/marketplace.json

Add a marketplace local to the current project with --scope project. The default scope is user.

/claude:plugin marketplace add upstash/context7-marketplace --scope project

List configured marketplaces.

/claude:plugin marketplace list
/claude:plugin marketplace ls

Update one marketplace, or all marketplaces if a name is omitted.

/claude:plugin marketplace update context7-marketplace
/claude:plugin marketplace update

Remove a marketplace and all plugins installed from it.

/claude:plugin marketplace remove context7-marketplace
/claude:plugin marketplace rm context7-marketplace

Toggle marketplace plugin auto-updates. When the marketplace is updated manually, installed plugins are automatically updated.

/claude:plugin marketplace autoupdate context7-marketplace
/claude:plugin marketplace noautoupdate context7-marketplace

Plugin

List plugins available for installation. Omit the marketplace name to list across configured marketplaces.

/claude:plugin list context7-marketplace --available
/claude:plugin list --available

Filter the list by plugin status, installed, available for installation, or unavailable to install.

/claude:plugin list --installed
/claude:plugin list --available
/claude:plugin list --unavailable

Install a plugin, using the <plugin>@<marketplace> format.

/claude:plugin install context7-plugin@context7-marketplace

Install in the project scope instead of the user scope.

/claude:plugin install context7-plugin@context7-marketplace --scope project

Update one installed plugin, every installed plugin from one marketplace, or all installed plugins.

/claude:plugin update context7-plugin@context7-marketplace
/claude:plugin update @context7-marketplace
/claude:plugin update

Reinstall one installed plugin, every installed plugin from one marketplace, or all installed plugins. Reinstall uses the cached marketplace manifest and the installed record's existing version; it does not fetch, pull, or otherwise sync the marketplace from the network:

/claude:plugin reinstall pr-review-toolkit@claude-plugins-official
/claude:plugin reinstall @claude-plugins-official
/claude:plugin reinstall

Limit reinstall to one scope with --scope user or --scope project. The flag can appear before or after the target:

/claude:plugin reinstall --scope project
/claude:plugin reinstall @claude-plugins-official --scope user

The --scope flag selects which installed plugin records and generated resources are reinstalled; the marketplace reference identifies the source marketplace. For an explicit plugin target, reinstall reports not installed in the selected scope instead of failing just because that marketplace is configured in another scope.

Use --force only when reinstalling a plugin whose own previous agent files were manually edited or otherwise look foreign. --force can overwrite that plugin's previous agent content, but it does not override other-plugin ownership conflicts, unsafe names, path-containment failures, or MCP server name collisions:

/claude:plugin reinstall pr-review-toolkit@claude-plugins-official --force

Reinstall targets installed plugins only. If no installed plugins match the selected target set, the command reports No plugins installed. and does not emit a reload hint. Plugin data directories are deleted only after replacement resources and state.json commit successfully; if reinstall fails, the previous plugin state, resources, and data remain available.

[!NOTE] Agent definitions in plugins may include a preferred model for running the agent, e.g. "sonnet", "opus", etc. These are discarded by default, but the --map-model option for install can be used to make a best-effort attempt at mapping these models to Pi models.

Uninstall a plugin.

/claude:plugin uninstall context7-plugin@context7-marketplace

Reload Pi after changes.

/reload

Bootstrap

Bootstrap is a convenience one-shot setup of the official Anthropic marketplace in the user scope with autoupdate enabled.

/claude:plugin bootstrap

This is equivalent to running.

/claude:plugin marketplace add anthropics/claude-plugins-marketplace
/claude:plugin marketplace autoupdate anthropics/claude-plugins-marketplace

Import

Import is a convenience command to import marketplaces and plugins already defined in Claude Code settings.

/claude:plugin import

By default, marketplaces and plugins are added in accordance to the scope that they're defined in Claude Code. It's also possible to limit the import to a specific scope.

/claude:plugin import --scope user
/claude:plugin import --scope project

Plugins that are not available for installation in Pi because of unsupported components are skipped with a warning.

Development

Install pre-commit hooks.

pre-commit install
pre-commit install --hook-type commit-msg

Enable Git LFS for large binary assets such as images and videos.

git lfs install

Build.

npm install
npm run check

AI disclaimer

This project is developed with AI agent engineering practices using the GSD spec-driven development system.

The author vibe-coded a prototype until it was feature-complete for a first release, then extracted and reviewed a PRD from the implementation.

The PRD was then used to guide GSD through discussion, planning and implementation phases of a new implementation.

License

This project is licensed under the MIT License. See the COPYING file for details.

Copyright 2026 Alessandro Colomba