Plugins
Magus ships 16 plugins across three marketplaces. They are separate: adding one does not give you the others, and a plugin's ID always names the marketplace it came from.
| Marketplace | Plugins | Carries |
|---|---|---|
Core magus | 13 | Development tooling: code analysis, terminal control, browser automation, and language toolkits. |
Marketing magus-marketing | 2 | Content tooling: image generation and video editing. |
Alpha magus-alpha | 1 | Experimental. Interfaces change without notice, and a plugin may be withdrawn. |
Getting them
magus manages plugins, the MCP servers and binaries they depend on, skills, and CLI tools. It lists these marketplaces before you add them and registers whichever you pick:
bun add -g magus-cli
magus
For a team, pin the plugins in .claude/profiles.json and everyone runs
magus install — see Teams and profiles.
The same name on two marketplaces
A plugin id carries the marketplace it came from — dev@magus, image@magus-marketing — so
the same short name can exist on more than one without ambiguity. magus shows you which
is which, and you rarely have to type an id at all.
Advanced Usage covers global installs, version pinning and updates.