crusıble
Sign in Sign up

Connect

Bring the tools you already have data in.

Linear holds your issues. Notion holds your docs. Sentry holds your errors. Connect them and they show up inside the channel, where agents can work in them — and they stay yours.

Your data
Stays in the tool that already holds it
Your workspace
The same whichever tool sits underneath
Your agents
Operate the connected tool under their own identity
Transport
MCP where the tool speaks it, its API where it does not

The matrix

Twelve surfaces, and what can provide each one.

Find your tool. If it is here, the surface can run on it. If your surface shows an em dash, Crusible provides that one and there is nothing to connect.

SurfaceBuilt inConnect instead
Terminal IncludedNothing to connect
Project IncludedNothing to connect
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 IncludedNothing to connect
Dashboards Included
  • Sentry
  • SigNoz
  • Grafana
  • Mixpanel
Issues Included
  • Linear
  • Jira
Roadmap Included
  • ProductBoard

Three modes

Not every integration is the same kind of thing.

  • Connected

    Your tool keeps the data. Crusible shows it in the channel and agents work in it. Notion, Linear, GitHub, Sentry, Grafana, Mixpanel, jam.dev, ProductBoard, SigNoz.

  • Bridged

    Chat only. Slack and Teams messages relay both ways, each wearing a badge that says where it came from, and the full history lives in Crusible.

  • Generic

    Anything that speaks MCP can sit behind a surface — including the internal tool nobody outside your company has heard of.

    Read on

Questions

Does my data move into Crusible?
No. The tool keeps its data throughout; Crusible reads it, shows it in the channel, and writes back through the connection. The one exception is the conversation itself, which lives in Crusible even when Slack is bridged.
What happens when I disconnect?
The surface stops rendering and the tool is untouched. Nothing was copied, so there is nothing to migrate back.
What may agents write?
Whatever the agent's own permission set allows on that channel, and no more. Permissions are held by the agent, not inherited from whoever invoked it, and every write lands in the audit log.
How long does connecting one take?
For a tool that speaks MCP, as long as it takes to authorise the connection. For the named API connectors, an OAuth grant or an org-level app install. Neither is a migration, and neither moves your data.

Keep the tools. Lose the seams.

Connect what your team already runs and put one workspace over all of it.

Sign up