Skip to main content
Sentry connects to RubixKube today through the custom integrations path. There is no separate prebuilt app to install. Most teams start with Custom REST and move to Custom MCP when they want richer, semantic tools.

​
What to bring in

The signals that matter most when agents are investigating or writing RCAs:
  • Issues (/api/0/projects/{org}/{project}/issues/) for error grouping, counts, and recency.
  • Events (/api/0/issues/{issue_id}/events/) for specific stack traces and breadcrumbs that explain a failure.
  • Releases (/api/0/projects/{org}/{project}/releases/) to correlate error spikes with deploys.
  • Performance (transactions, p95 latency by transaction name) if you have Sentry Performance.
Read-only auth tokens are enough for all of the above.

​
Which path to pick

Start with REST

Sentry publishes a stable REST API. Point the custom REST integration at it with an OpenAPI wrapper.

Move to MCP when you need more

Wrap issue lookups and deploy correlation behind named tools (for example sentry_top_issues_since(release)).

​
Quick recipe: REST path

1

Create a Sentry auth token

In Sentry, create an internal integration with a read-only auth token covering the projects you want RubixKube to see.
2

Register the endpoint

In the RubixKube console, go to Integrations → Custom REST and register the Sentry API.
3

Enable the calls you care about

Start with issues list, single issue events, and releases. Transactions if you use Performance.
4

Set auth

Add the auth token to the workspace secret vault. Map it to the Authorization: Bearer <token> header.
5

Scope to skills

Attach the enabled endpoints to the skills that need Sentry context.
Once connected, the integration is tenant-wide.

​
Example tools worth having

  • sentry_top_issues(project, window) — returns the most frequent issues in the window with counts.
  • sentry_issue_detail(issueId) — returns the latest event, stack trace, and breadcrumbs.
  • sentry_since_release(project, release) — returns new issues introduced since a given release, useful after a deploy correlates with an incident.
  • sentry_transaction_p95(service, window) — returns p95 latency by transaction name.
Define these as skills (or as MCP tools if you want them to wrap multiple calls).

Custom REST Integrations

The full REST flow with auth options and approval rules.

Custom MCP Servers

When you want richer tool schemas and multi-call workflows.

Skills

How to compose Sentry lookups into custom workflows.