Sentry
Sentry as a provider behind the Dashboards surface: Sentry holds the errors, and agents operate them through Sentry over MCP.
- Which surface it backs
- Dashboards. Crusible's own boards are planned; today Dashboards runs on the tools a team already has.
- MCP or API
- Model Context Protocol (MCP).
- Who holds the record
- Sentry. The events, issues and alerts stay in Sentry, and Sentry is what answers for them.
- What agents may read and write
- Agents read errors, their frequency and their stack traces, and act on issues where the connection permits it. What an agent may write is bounded by the permissions the connection was granted.
- What happens on disconnect
- The Dashboards surface stops rendering Sentry data for that workspace. Nothing is removed from Sentry, and the channel is otherwise unchanged.
- What is not supported
- Anything the connection was not granted, and anything Sentry does not expose over MCP. Crusible adds no capability Sentry does not have.
- The graduation frame
- A team can connect Sentry behind Dashboards, or run Dashboards first-party once Crusible's own boards exist. Both directions are a provider switch and neither is up.
Sentry is a provider behind Dashboards wherever a workspace has connected it. Sentry holds the errors; the Dashboards surface renders them, and agents operate them through Sentry.
Who answers for the errors
Sentry. Retention, sampling, alert rules, the issue’s own state and its audit trail belong to Sentry and are governed by Sentry’s controls. Crusible holds no second copy, and the Dashboards board is a view rather than a store.
What changes in the product
One surface changes. The channel, its conversation, its agent roster and its permission model are identical either way.
An agent that finds something on the board posts it to the conversation as an artifact card, with the card opening back into the surface. A number worth acting on becomes a message with a priority rather than a chart nobody was watching.
An agent reading the board acts as the connection, so what it can reach in Sentry is what the connection was granted and no more. Where the connection permits it, an agent can act on an issue in Sentry as well as read it.
One board, several providers
Dashboards is the one surface that carries more than one provider at a time. An Infrastructure or Analytics channel’s board can show errors from Sentry beside service health and product analytics from other connected tools. Each number on the board belongs to whichever tool produced it, and each of those tools has its own row in the provider matrix.
What the board gives a reader is one place to act on what those tools already say.
Switching in either direction
Crusible’s own boards are planned. Today Dashboards runs on connected tools, and a team connecting Sentry keeps its errors exactly where they are. Switching a board to first-party later is a provider switch like any other: neither direction is up, and the graduation path runs both ways.