How Claude Marketplace plugins work in Claude Code

A Claude Code plugin can bundle several kinds of capability. Knowing what each one is - and when it activates - makes the marketplace plugins much easier to use.

What a plugin can add

Slash commands - namespaced as /<plugin>:<command> (for example /ableton:setup). Type / in a session to see them.
Skills - background instructions Claude loads automatically when your task matches. You don’t invoke these directly; the model picks them up when relevant.
Subagents - specialized helpers a plugin can dispatch for a focused job, like a review pass.
MCP servers - a bundled tool server that gives Claude new abilities (query GA4, edit DNS, drive Ableton). Most of our infrastructure and integration plugins are MCP-based.
Hooks - automation that runs on events like session start or after a tool call, for example surfacing a “new version available” notice.

When it takes effect

Plugin components load when Claude Code starts a session. After you install, update, enable, or disable a plugin, its commands, skills, and MCP tools generally appear (or disappear) the next time you start Claude Code - not mid-session. When in doubt, restart.

Scopes

You can install a plugin at three scopes: -s user (available in every project), -s project (shared with a specific project), or -s local (just your local checkout). Choose user for general tools you always want, project for something a repo’s collaborators should share.

Enable vs uninstall

disable keeps a plugin installed but inert and quick to re-enable; uninstall removes it entirely. Both take effect in a new session.

Want the details for a specific plugin? Each one has its own article, linked from Getting support for a Claude Marketplace plugin. Still stuck? Send us a message and a human will reply by email.