Plugins & connectors
Manage organization plugins with `cluster plugins` and `/plugins`, and connect Agents services through `/mcp` — including model-assisted install and sign-in requests during chat.
Beyond your own custom skills, Cluster Build can use plugins and connections that your organization administers centrally.
- Plugins are verified, versioned skill packages an organization installs once and members can then activate per turn.
- Connectors are authenticated Agents service
connections — for example Gmail — that a turn can use without you signing in
again. Manage them from
/mcpalongside your local and built-in MCP servers.
Manage plugin installations
cluster plugins manages your organization's installed plugins. It requires a
trusted workspace, since it runs headlessly like cluster exec.
cluster plugins catalog
cluster plugins list
cluster plugins install <plugin> <revision> --generation <n>
cluster plugins uninstall <plugin> --generation <n>
cluster plugins inspect <plugin>| Subcommand | Effect |
|---|---|
catalog | List admitted plugin revisions with their installation generations, including the retained generation of uninstalled plugins |
list | List the organization's installed plugins with their revisions and installation generations |
install <plugin> <revision> --generation <n> | Select an admitted, immutable revision; --generation 0 creates a new installation, and the generation shown by catalog reinstalls or updates one |
uninstall <plugin> --generation <n> | Uninstall a plugin from the organization at its current generation |
inspect <plugin> | Download and verify the complete installed package without activating it |
Pass --organization <id> to act on an organization other than your signed-in
account's default:
cluster plugins list --organization <org-id>The global --plugin-organization <id> flag sets the same organization for a
whole run, including an interactive session's /plugins view.
Writes use the generation you observed; a conflict means the installation
changed, so refresh with catalog or list and retry with the new
generation.
Use a plugin or connector in a session
Installed plugins and your connected accounts, are resolved for
each turn of an interactive session — there are no per-run --plugin or
--connector flags. Manage them from the session itself:
| Command | Effect |
|---|---|
/plugins | Browse the organization plugin catalog and install, update, or uninstall plugins inline |
/mcp | Inspect local, built-in, and Cluster services together; connect or manage an account, inspect tools, and refresh — see MCP servers |
Because selection is refreshed per turn, a plugin uninstalled mid-session stops being available on the next turn.
Model-assisted discovery and installation
Asking for a capability (for example, "a plugin for design documents") lets
the assistant search the admitted plugin catalog and, with your explicit
approval, install an exact revision. Consent shows the resolved organization
and the plugin's complete capability list. The assistant can only add a plugin
that isn't installed — including reinstalling an uninstalled one — and it
becomes available on the next turn. Updating to a different revision or
uninstalling still goes through /plugins. Installing a plugin grants no
account access, and uninstalling one does not disconnect a shared account.
If the plugin needs an account connection, the assistant can request one with
request_service_connection. Approving it shows an account-management link
you can open on any device; the CLI waits up to ten minutes for the
connection and never opens a browser itself or sees your credentials.
Headless, child, and plan-mode sessions can only discover — approving an
install or a connection requires interactive root chat.
Next steps
- Interactive sessions — the full slash-command
reference, including
/plugins,/mcp, and/skills. - Exec & sessions — run one-shot prompts non-interactively.