See the complete route index at https://crusible.dev/llms.txt before following links.

# Providers

What each surface ships with by default, and which providers you can connect instead.

- [MCP](https://crusible.dev/docs/reference/providers/mcp/) — Model Context Protocol is one of the two ways a tool becomes the provider behind a surface. Here is what an MCP connection gives you.
- [Notion](https://crusible.dev/docs/reference/providers/notion/) — Notion as the provider behind the Docs surface: Notion keeps the pages, and agents operate them through Notion over MCP.
- [Linear](https://crusible.dev/docs/reference/providers/linear/) — Linear as the provider behind the Issues surface: Linear holds the issues, and agents operate them through Linear over MCP.
- [GitHub](https://crusible.dev/docs/reference/providers/github/) — GitHub as the provider behind the Review surface: GitHub holds the pull requests, and agents operate them through GitHub over its API.
- [Sentry](https://crusible.dev/docs/reference/providers/sentry/) — Sentry as a provider behind the Dashboards surface: Sentry holds the errors, and agents operate them through Sentry over MCP.
- [Google Docs](https://crusible.dev/docs/reference/providers/google-docs/) — Google Docs as the provider behind Docs: Google keeps the documents, and the surface renders what Google holds.
- [GitLab](https://crusible.dev/docs/reference/providers/gitlab/) — GitLab as the provider behind Review: GitLab keeps the repositories and their merge requests, and Review renders them.
- [jam.dev](https://crusible.dev/docs/reference/providers/jam/) — jam.dev as the provider behind Test replay: jam.dev keeps the recordings, and the surface steps through what it holds.
- [SigNoz](https://crusible.dev/docs/reference/providers/signoz/) — SigNoz as a provider behind Dashboards: SigNoz keeps the traces and metrics, and the board renders what it holds.
- [Grafana](https://crusible.dev/docs/reference/providers/grafana/) — Grafana as a provider behind Dashboards: Grafana keeps the dashboards and their data sources, and the board renders them.
- [Mixpanel](https://crusible.dev/docs/reference/providers/mixpanel/) — Mixpanel as a provider behind Dashboards: Mixpanel keeps the product analytics, and the board renders what it holds.
- [Jira](https://crusible.dev/docs/reference/providers/jira/) — Jira as the provider behind Issues: Jira holds the issues. No screen shows the Issues surface, so little else is stated here.
- [ProductBoard](https://crusible.dev/docs/reference/providers/productboard/) — ProductBoard as the provider behind Roadmap: ProductBoard holds the roadmap. No screen shows the Roadmap surface.
- [Figma](https://crusible.dev/docs/reference/providers/figma/) — Figma as a provider behind Diagrams and Design preview: Figma keeps the files. No screen shows a surface running on a provider.
- [Miro](https://crusible.dev/docs/reference/providers/miro/) — Miro as a provider behind Diagrams: Miro keeps the boards. No screen shows a surface running on a connected provider.