> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squasher.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations API

> List provider-agnostic integration setup metadata for CLI, API, and MCP flows.

Use the Integrations API to discover supported setup flows without hard-coding provider metadata into an agent.

## Operations

| Operation                    | Method and path                  | Purpose                                                                        |
| ---------------------------- | -------------------------------- | ------------------------------------------------------------------------------ |
| `integrations.listProviders` | `GET /v1/integrations/providers` | List provider-agnostic integration setup metadata for CLI, API, and MCP flows. |

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

```text theme={null}
Fetch Squasher integration provider metadata, then choose the smallest setup path for the user's source. Return required fields and the next docs link. Do not invent provider-specific fields that are not returned by the API.
```

Related: [CLI Reference](/integrations/cli-reference), [Logging overview](/integrations/logging-overview).