Marketplace packages
Give your agents a new skill with one choice. A package is a ready-made piece for a space: a coding agent, a developer tool, a language toolchain, a connection to another service, or a set of instructions. The marketplace is the catalog of every package. Your admin picks which ones your organization installs, and Marshal handles the setup, the credentials and the network access each one needs.
What you can do with it
- Put Linear in the agent’s hands. Your admin installs
linear-mcpand adds it to the team stack. Each person connects their Linear account once, and the agent works with Linear issues, projects and cycles in every new space. - Ship with your own toolchain. Add
pythonandpostgresto your manifest. The agent getspip,uvandpsql, and the database password stays with Marshal. - Let editors connect. Add the
egress-vscodepackage so VS Code Remote-SSH can download its server into a space and reach the VS Code Marketplace.
See it end to end: A governed dev environment for every engineer.
How it fits
- An admin installs the package into the organization. Installing checks that the package works with your Marshal version.
- The package is added to a stack. A stack groups packages and is published as a version. See Manifests and stacks.
- A manifest uses that stack. You can add or remove installed packages in your own manifest.
- You start a space from the manifest. The space gets exactly the packages the manifest named.
A package can need a credential, and it declares the hosts its tools must reach, so its network access comes with it. See Network policy. Some packages need other packages: a browser-automation MCP server needs the chromium package.
Kinds of package
| Kind | What you get | Example |
|---|---|---|
| Agent | A coding-agent command line. | claude-code, codex |
| Tools | A self-contained command-line tool. | terraform |
| Toolchain | A language runtime and its build tools. | node, python, go |
| Authentication | A tool plus a credential type for a service. Marshal adds the credential when the tool calls the service. | github, aws |
| MCP server | A server that gives the agent more tools to call. | linear-mcp, sentry-mcp |
| Network | A list of addresses to allow. No tools and no credentials. | egress-dockerhub |
| Sidecar | An extra container that runs next to the agent. | docker |
| Content | Skills and instructions shipped as text. | |
| Webhook | A receiver for incoming events from a service. | generic-hmac-webhook |
A few built-in packages, such as tools-base, are in every space and need no install.
Versions
A published package version never changes. An installed package is a snapshot: a newer version in the marketplace does not replace it until an admin updates it, or until the admin ticks Auto-update on the package, which keeps it on the newest patch and minor version of its major version. An admin can turn Auto-update on for every installed package at once, and for every package installed from then on. Auto-update never installs a new major version: an admin installs it, and a stack can then be set to follow it. A version that needs a credential access or dependency you have not approved waits for an admin too. See Keep packages up to date automatically. The new version then reaches a stack when its owner publishes a new stack version, and reaches your spaces when your manifest moves to that stack version. Existing spaces keep the versions they started with.
When a package version has a successor, its publisher marks it Deprecated with a short note and, usually, the version to move to. The note can arrive at any time after the version ships, and the version itself stays exactly as published. New choices skip it: the marketplace install menu and the stack version picker offer only current versions, and Show n deprecated versions at the bottom of the version menu brings the rest back when you need one. Wherever a deprecated version is already in use, Marshal says so. The Installed tab, the stack editor and the manifest editor show the note with a link to the replacement, and in the stack editor Move to vversion pins the slot to the replacement in one click when it is a newer version of the same package. A deprecated version keeps working in every space that uses it, so you move on your own schedule.
When a version turns out to be vulnerable, an admin can block it so nothing launches with it. See Security Center.
Members browse the full catalog on the Marketplace page and pick from installed packages when they edit a manifest. Admins and owners install, update and uninstall.
Related
- Security Center: block a vulnerable version and fix what holds it.
- Package catalog: every package, with what it gives the agent.
- Install a package into a manifest.
- Integrations: connecting services such as GitHub and Slack.