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

# Provision Integration Targets

> Configure integration-targets.json and sync built-in targets into a self-hosted Mistle deployment

## Overview

Self-hosted Mistle uses integration targets to expose built-in providers to the dashboard and runtime.

Operators define those targets in `integration-targets.json`, then sync them into the control-plane database:

```bash theme={null}
pnpm --filter @mistle/control-plane-api integration-targets:sync
```

<Note>
  If you are running this via the Docker Compose stack, this is automatically done as part of the
  start up script.
</Note>

## Start From The Example File

Use the repository example file as the starting point:

* `integration-targets.json`

Copy the targets you want, remove the ones you do not want, and commit the operator-managed manifest your deployment uses.

## Required Workflow

For every manifest change:

1. Edit `integration-targets.json`
2. Run `pnpm --filter @mistle/control-plane-api integration-targets:sync`

## Target Config Reference

These are the target-level fields operators own.

### Empty-config targets

These targets only need to be enabled:

* `agentmail-mcp`
* `aws-cli-default`
* `anthropic-default`
* `bugsnag-mcp`
* `cloudflare-mcp`
* `dataforseo-mcp`
* `datadog-default`
* `deepseek-default`
* `e2b-default`
* `expo-mcp`
* `fireworks-default`
* `gcp-mcp`
* `google-analytics-mcp`
* `google-business-profile-mcp`
* `google-search-console-mcp`
* `google-workspace-mcp`
* `googleads-default`
* `inception-default`
* `jira-default`
* `kimi-default`
* `klaviyo-mcp`
* `linear-default`
* `metaads-default`
* `minimax-default`
* `modal-default`
* `notion-mcp`
* `opencode-go`
* `opencomputer-default`
* `openrouter-default`
* `planetscale-mcp`
* `posthog-mcp`
* `railway-mcp`
* `render-mcp`
* `resend-mcp`
* `sentry-default`
* `signoz-mcp`
* `stripe-mcp`
* `supabase-mcp`
* `tensorlake-default`
* `xero-mcp`
* `zai-coding-plan`

Example:

```json theme={null}
{
  "targetKey": "linear-default",
  "enabled": true,
  "config": {}
}
```

### Slack

`slack-default` requires an API base URL:

```json theme={null}
{
  "targetKey": "slack-default",
  "enabled": true,
  "config": {
    "api_base_url": "https://slack.com/api"
  }
}
```

### GitHub

`github-cloud` and `github-enterprise-server` require API and web base URLs:

```json theme={null}
{
  "targetKey": "github-cloud",
  "enabled": true,
  "config": {
    "api_base_url": "https://api.github.com",
    "web_base_url": "https://github.com"
  }
}
```

```json theme={null}
{
  "targetKey": "github-enterprise-server",
  "enabled": false,
  "config": {
    "api_base_url": "https://ghe.example.com/api/v3",
    "web_base_url": "https://ghe.example.com"
  }
}
```

`github-cloud` is the default enabled GitHub target in the example manifest. `github-enterprise-server` is supported, but disabled by default until you explicitly turn it on for a GHES deployment.
At this point, `github-enterprise-server` is only supported for self-hosted deployments.

### OpenAI

`openai-default` requires the API base URL.

Use the `openai-default` block from `integration-targets.json` as your starting point. That block defines:

* `api_base_url`

### Meta Ads

`metaads-default` can use an empty config. By default, it routes through Meta Graph API `v25.0`.

Set `graph_api_version` only when your deployment needs to pin a different supported Meta Graph API version:

```json theme={null}
{
  "targetKey": "metaads-default",
  "enabled": true,
  "config": {
    "graph_api_version": "v25.0"
  }
}
```

### Google Ads

`googleads-default` can use an empty config. By default, it routes through Google Ads API `v24`.

Set `api_version` only when your deployment needs to pin a different supported Google Ads API version:

```json theme={null}
{
  "targetKey": "googleads-default",
  "enabled": true,
  "config": {
    "api_version": "v24"
  }
}
```

### Agent And Sandbox Runtime Targets

`anthropic-default`, `deepseek-default`, `fireworks-default`, `inception-default`, `kimi-default`, `minimax-default`, `opencode-go`, `openrouter-default`, and `zai-coding-plan` are model-provider targets for sandbox profiles that use OpenCode-compatible agent runtimes.

`e2b-default`, `modal-default`, `opencomputer-default`, and `tensorlake-default` expose sandbox runtime connection targets. Operators still configure deployment-level runtime settings in [Self-Hosted Configuration](/guides/self-hosted-configuration), while workspace admins can use integration connections when a profile should use workspace-owned runtime credentials.

## Scope Boundary

This page covers target provisioning only.

It does not cover:

* creating GitHub Apps
* choosing Slack bot scopes
* creating Jira credentials
* approving provider OAuth flows

Those tasks belong in the provider-specific connection guides.