Stacks
A stack is a set of capability packages that belong together, installed in one step under the usual trust, permission and approval rules.
A stack is a set of packages that belong together — a framework's skills and MCP servers, for example — installed in one step from Capabilities → Stacks.
Two kinds
| Stack | Made by | May hold |
|---|---|---|
| Platform | Server administrators, in Server → Marketplace → Stacks | Public packages only. Offered to every organization. |
| Organization | The organization's administrators (permission capability.manage) | Anything the organization can see, including its private packages |
An organization's stack with the same address (slug) as a platform stack is shown to its members instead of the platform's. A stack holds 1 to 30 packages.
Install all
Install all installs every package at one scope: the organization, a project, or just you.
Each package goes through the usual installation, so trust, permission and approval rules apply to each. The result lists, per package:
| Result | Meaning |
|---|---|
| Installed | With the version that was installed |
| Waiting for approval | The install policy or a permission needs someone's approval |
| Refused | Policy refused it; the reason is shown |
A stack never installs something the policy would refuse for a single package.
API
| Method and path | Purpose |
|---|---|
GET /orgs/:orgId/registry/stacks | The organization's own stacks, then the platform's |
GET /orgs/:orgId/registry/stacks/:slug | One stack with its packages |
POST /orgs/:orgId/registry/stacks | Create a stack of the organization |
PATCH / DELETE /orgs/:orgId/registry/stacks/:slug | Change or delete it |
POST /orgs/:orgId/registry/stacks/:slug/install | Install every package at scope ORGANIZATION, PROJECT (with projectId) or USER |
GET /catalog/stacks, GET /catalog/stacks/:slug | Platform stacks, without sign-in, when the public catalog is on |
Stacks are free groupings. Paid listings are not part of the marketplace.