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.
Overview
Self-hosted Mistle uses integration targets to expose built-in providers to the dashboard and runtime. Operators define those targets inintegration-targets.json, then sync them into the control-plane database:
If you are running this via the Docker Compose stack, this is automatically done as part of the
start up script.
Start From The Example File
Use the repository example file as the starting point:integration-targets.json
Required Workflow
For every manifest change:- Edit
integration-targets.json - 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:aws-cli-defaultdatadog-defaultjira-defaultlinear-defaultplanetscale-mcpsignoz-mcp
Slack
slack-default requires an API base URL:
GitHub
github-cloud and github-enterprise-server require API and web base URLs:
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
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