Use plugins
Universal Agent Plugins installs standard packages for the AI agents you select. A package can contain Skills, MCP server configuration, or both. You can install for your account or keep a project's dependencies separate.
Get the CLI
With Node.js 22 or newer, run the npm wrapper directly:
npx universal-agent-plugins search docsFor repeated use, install it globally:
npm install -g universal-agent-plugins
agentplugins versionHomebrew is another option:
brew install 777genius/agentplugins/agentpluginsThe native installation guide provides macOS, Linux and Windows instructions. Native installation needs no Node.js for the manager, although individual plugins may need their own runtime. Examples in this journey use agentplugins; npx universal-agent-plugins can run the same installer commands.
Follow the installation journey
- Find and inspect a package. Check its source and prerequisites.
- Preview your intended targets and scope with
--dry-run. - Apply the reviewed installation and follow its activation instructions.
- Maintain the installed state with list, update, repair and removal.
- Restore a shared dependency set from
uap.tomlanduap.lockwhen needed.
CLI is the current native installer. It adds a local management API and Pi extensions, Skills and stdio/Streamable HTTP MCP in user and eligible project scope. See local management and Pi compatibility. Package-manager channels can lag; check agentplugins version before relying on release-specific behavior. Use the native installer for the verified release. Explicit project scope works since 0.1.93. Most commands default to user scope. Since 0.1.94, install without a source argument or explicit scope selects a project only when a regular uap.toml exists in the exact current folder; it does not search parents. Select --scope project on project maintenance commands. Project support and client activation differ by target.
Read the result at the right level
Installation can still leave a client reload, trust prompt, manual activation or OAuth step. A Prepared result means more client work remains. Read each target's result rather than treating the whole operation as proof of runtime success. See client compatibility for the evidence behind versioned native observations.
If you are writing a package
Start with Build plugins. The shared handoff is a directory with root plugin.json and its components. It does not require the installer user to run source-build authoring tools.
| Command | Purpose |
|---|---|
agentplugins validate ./my-plugin | Read and validate a local package for installation. |
agentplugins doctor | Diagnose installer-managed state. |
agentplugins author validate ./my-plugin | Check authoring conformance and readiness in an authoring-enabled source build. |
agentplugins author doctor ./my-plugin | Inspect project and toolchain evidence in that source build. |
The current npm and native installer release does not include agentplugins author.