Skip to main content
The integrations API returns the catalog of supported integrations and how to set each one up. Use it so that an agent does not have to hard-code provider setup details.

​
Operations

Use the response to route users to the right integration guide, setup mode, declared fields, required flags, and setupRules field dependencies. The lifecycle object also declares the supported connection adapters and the dashboard adapter’s owner, project-binding requirement, and display order. Do not use catalog metadata as evidence that a project has already connected a provider; connection state remains project- and account-specific.

​
CLI and MCP

Use squasher integrations providers for terminal workflows. In MCP Code Mode, call search("integrations").

​
Agent handoff

Related: CLI Reference, Logging overview. For project connection state and one-click setup actions, use the Provider connections API. Provider catalog metadata does not contain customer credentials or prove that a project connection is active.