PUBLIC DOCUMENTATION
Universal Agent Plugins
Install Skills and MCP tools for the agents you use, or build a portable package of your own.
Choose your journey
Use plugins
Inspect a package, preview its changes, and install it for your account or one project.
Build plugins
Write a standard package with plugin.json, Skills and MCP configuration. Explore source-build authoring tools.
Integrate UAP
Hooks, host detection, Go installer and TypeScript management.
Explore more than installation
- Install packages for multiple agents, choose standalone Skills, or use the signed catalog, Git/SSH and archives. Install.
- Keep user and project dependencies separate with
uap.toml/uap.lock; update, repair and diagnose managed state. Manage. - Build portable Skills/MCP packages and embed Go/TypeScript SDKs. SDK · Build.
Install your first plugin
With Node.js 22 or newer:
npx universal-agent-plugins add context7The CLI asks which compatible agents to use. Review the plan and complete the activation or sign-in steps it reports. Prefer a native executable? Follow the native installation guide for macOS, Linux or Windows; the native manager itself does not require Node.js.
What is available
CLI is the current native installer release. It adds a local management API and native Pi extensions, Skills and stdio/Streamable HTTP MCP in user and eligible project scope. Signed Directory releases still require their own Pi target policy. See local management and Pi compatibility. It retains explicit project scope and locked restoration. Most commands default to your user environment. An install without a source argument selects the current project when that exact folder contains a regular uap.toml; explicit scope wins. Select project scope on maintenance commands. Check agentplugins version: automatic selection requires 0.1.94. Package-manager channels may lag; use the native installer for the verified release, or retain explicit project flags supported since 0.1.93. See installation and maintenance.
The current installer does not include agentplugins author. The Build guide explains manual packages and the authoring commands implemented in current source. Older authoring release evidence retains its original version and does not describe the current installer download.
Understand the result
Package validation, installation, client discovery, MCP tool execution and service authentication are separate checks. A successful file installation may still need client trust, a reload or a fresh session. Native tests cover specific client versions and platforms; they do not certify every plugin or every agent.