Providers
What each surface ships with by default, and which providers you can connect instead.
A provider is what runs behind a surface. The table below reads by surface — what Crusible built in, and what you can connect instead — never by transport or connection mode.
| Surface | Built in | Connect instead |
|---|---|---|
| Terminal | Included | Nothing to connect — Crusible provides this one. |
| Project | Included | Nothing to connect — Crusible provides this one. |
| Forge | Included | GitHub, GitLab |
| Docs | Included | Notion, Google Docs |
| Diagrams | Included | Figma, Miro |
| Design preview | Included | Figma |
| Test replay | Included | jam.dev |
| Review | Included | GitHub, GitLab |
| Flow | Included | Nothing to connect — Crusible provides this one. |
| Dashboards | Included | Sentry, SigNoz, Grafana, Mixpanel |
| Issues | Included | Linear, Jira |
| Roadmap | Included | ProductBoard |
Terminal
- Built in
- Included
- Connect instead
- Nothing to connect — Crusible provides this one.
Project
- Built in
- Included
- Connect instead
- Nothing to connect — Crusible provides this one.
Forge
- Built in
- Included
- Connect instead
- GitHub, GitLab
Docs
- Built in
- Included
- Connect instead
- Notion, Google Docs
Diagrams
- Built in
- Included
- Connect instead
- Figma, Miro
Design preview
- Built in
- Included
- Connect instead
- Figma
Test replay
- Built in
- Included
- Connect instead
- jam.dev
Review
- Built in
- Included
- Connect instead
- GitHub, GitLab
Flow
- Built in
- Included
- Connect instead
- Nothing to connect — Crusible provides this one.
Dashboards
- Built in
- Included
- Connect instead
- Sentry, SigNoz, Grafana, Mixpanel
Issues
- Built in
- Included
- Connect instead
- Linear, Jira
Roadmap
- Built in
- Included
- Connect instead
- ProductBoard
- 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 Notion as the provider behind the Docs surface: Notion keeps the pages, and agents operate them through Notion over MCP. Docs
- Linear Linear as the provider behind the Issues surface: Linear holds the issues, and agents operate them through Linear over MCP. Issues
- GitHub GitHub as the provider behind the Review surface: GitHub holds the pull requests, and agents operate them through GitHub over its API. Review
- Sentry Sentry as a provider behind the Dashboards surface: Sentry holds the errors, and agents operate them through Sentry over MCP. Dashboards
- Google Docs Google Docs as the provider behind Docs: Google keeps the documents, and the surface renders what Google holds. Docs Planned · Phase 2
- GitLab GitLab as the provider behind Review: GitLab keeps the repositories and their merge requests, and Review renders them. Review Planned · Phase 2
- jam.dev jam.dev as the provider behind Test replay: jam.dev keeps the recordings, and the surface steps through what it holds. Test replay Planned · Phase 2
- SigNoz SigNoz as a provider behind Dashboards: SigNoz keeps the traces and metrics, and the board renders what it holds. Dashboards Planned · Phase 2
- Grafana Grafana as a provider behind Dashboards: Grafana keeps the dashboards and their data sources, and the board renders them. Dashboards Planned · Phase 2
- Mixpanel Mixpanel as a provider behind Dashboards: Mixpanel keeps the product analytics, and the board renders what it holds. Dashboards Planned · Phase 2
- Jira Jira as the provider behind Issues: Jira holds the issues. No screen shows the Issues surface, so little else is stated here. Issues Not yet documented
- ProductBoard ProductBoard as the provider behind Roadmap: ProductBoard holds the roadmap. No screen shows the Roadmap surface. Roadmap Not yet documented
- Figma Figma as a provider behind Diagrams and Design preview: Figma keeps the files. No screen shows a surface running on a provider. Diagrams Not yet documented
- Miro Miro as a provider behind Diagrams: Miro keeps the boards. No screen shows a surface running on a connected provider. Diagrams Not yet documented