Bundles and Deployments

The two-layer model

Everything in the platform sits on two layers:

• A bundle is a named collection of MCP entries - a config, not a running thing. Each entry references an MCP listing, an alias (how it's addressed within the bundle), and an auth_strategy.
• A deployment is a running instance of a bundle, bound to whoever created it. Deployments hold the actual credentials and issue the bearer tokens an agent connects with.

You edit bundles. You deploy, authenticate, and connect through deployments. This split exists so the same bundle can be deployed more than once - by different people, or by the same person for different purposes - without those deployments sharing credentials or tokens.

Bundles are a config, deployments are a snapshot

Creating a deployment snapshots the bundle's entries at that moment. Editing the bundle afterward - adding an MCP, changing an alias - does not retroactively change deployments already created from it. If you want an existing deployment to pick up a bundle change, you create a new deployment (or the equivalent update path, if your workflow supports it) rather than expecting live propagation.

Deleting a deployment does not delete the bundle it came from - the config and any other deployments made from it are unaffected.

Auth strategy vs. deployment credentials

An entry's auth_strategy on the bundle describes how credentials for that MCP are expected to be resolved, not the credential itself - the actual secret is supplied later, per deployment, in one of two ways:

• A one-off credential via PUT /deployments/{deployment_id}/credentials/{entry_id}
• A linked vault entry via the /vault variant of that same endpoint, when you want one stored credential reused across multiple deployments

MCPs that authenticate via OAuth2 instead of a static credential use a separate three-step flow - see the Authentication concepts page and the OAuth2 section of the API reference.

Where to go next

• Tutorial walks the full path end to end with real request/response bodies: create a bundle, add an MCP, deploy it, issue a token, connect.
• Full endpoint list: Bundles and Deployments in the API reference.