Skip to main content
Connect’s setup agent can research and prepare a package outside the built-in library. For ordinary use, start with the CLI quickstart. This page describes the package inputs and setup tools for application authors.

​
Setup tools

The host selects trusted runtimes, permitted acquisition profiles and resource locations. The agent selects the integration, version, entrypoint and operations.

​
Describe the package

Prepare an IntegrationPackage in package.json and an ActivationManifest in activation.json. Obtain the canonical package digest with:
Use summary.package_content_digest in the activation manifest. It identifies the canonical package content; raw file hashes identify the input files.

​
Input layouts

Retain the original server wheel and a complete dependency closure with exact versions and hashes. The manifest selects the module entrypoint and literal arguments. The installer verifies wheel ownership and installed files, then uses ordinary offline pip.
Exact package schemas and installer contracts are in crates/toolkit-package/PYTHON-INSTALL.md, NODE-INSTALL.md and sdk/consumer-setup/SELECTED.md in the source distribution.

​
Validate and install

Call setup_selected_check with the prepared inputs. Review its proposal, then pass the returned proposal ID and digest to setup_selected_install. Installation uses a new destination and retains the selected input hashes and resulting launch configuration. The host then supplies account credentials, approves operation access and attaches the emitted connection through the native MCP owner.

​
Inspect the installed server

Discover the server’s tools and schemas through the selected MCP connection. Choose the operations needed for the task, apply the host’s access policy and invoke them through the intended agent. For an update, prepare the new selection in a separate directory, switch the consumer and retire the old process. Keep the original selection available for recovery.

​
Reuse a selection

Save the exact package, activation and source observations as a local recipe. Future setup can read that recipe and apply current configuration and access decisions. See local recipes.

​
Container-backed selections

A host can expose setup_acquire_compose to acquire an exact container graph and immutable images from allowed registries. It produces a proposal for the host’s Compose execution path. See deployment and activation for lifecycle management.