Installation lifecycle
Manage catalog versions, capability installations and dependent assets.
A catalog entry identifies the plugin and publisher. Artifact versions identify code/resource packages. An installation selects a version and stores workspace configuration; capability installations expose the chosen operations.
Install
Inspect publisher, package, version and declared contracts. Configure protected connection settings and enable the required capabilities. A plugin can be official or workspace-authored; workspace publication does not make it an official shared plugin.
Check and use
A check probes the supported connection path. Create a matching data endpoint for a source, destination or fact-store target, or select an installed transform on a pipeline node. Run a known bounded operation before scheduling production work.
Update
Separate connection changes from code changes. Installation updates change the stored name or configuration. A new published artifact changes implementation and may change contracts; inspect the version used by each installation and dependent asset rather than assuming automatic adoption.
After rotating credentials, run a check. After changing code, review tests and execute the bounded workflow again. Existing pipelines and endpoints may rely on prior contracts.
Remove or retire
Removing an installation can affect data endpoints and pipeline nodes. Retirement disables a published authored plugin, or deletes an unpublished draft, after dependency checks. Review consumers before either action and inspect any dependency error instead of bypassing it.
MCP operations
| Task | Tool |
|---|---|
| Inspect catalog | plugin_catalog_list, plugin_catalog_get |
| Inspect installations | plugin_installation_list, plugin_installation_get |
| Create and check | plugin_installation_create, plugin_installation_check |
| Change configuration | plugin_installation_update |
| Remove | plugin_installation_remove |
| Revise and publish | plugin_authoring_create, plugin_authoring_publish |
| Retire | plugin_authoring_retire |
Installation calls use resource IDs and the discovered schemas. Keep idempotency keys stable only for retries of identical requests. Caller permissions and resource ownership still apply.