Kiwi
Kiwi

Kiwi for Sentry

Have the agent on a Kiwi step read the Sentry issue behind a bug, with its stack trace and events, before it fixes the code, through Sentry's MCP server.

  • Your agent works in Sentry through its own connection. Kiwi does not call Sentry and never holds its credentials.
  • A workflow skill can list Sentry among the tools it requires. When you supply your agent's available tools to a skill check and Sentry is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Sentry, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its Sentry connection, with report_configuration.
  • The agent submits links to its work in Sentry as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Sentry

  • Open a Sentry issue from its URL or ID and read its stack trace, tags and latest events.
  • Search errors, issues, traces and logs in an organization or project with a plain-language query.
  • Ask Seer to analyze an issue and propose a root cause.
  • Check whether an error still occurs after a fix by searching its recent events.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

    Coding agentsQuickstart

  2. Connect your agent to Sentry

    Add the Sentry MCP server to your agent with this URL. The credentials stay with your agent.

    https://mcp.sentry.dev/mcp

    Sentry documentation

  3. Example skill

    Publish instructions like these as a workflow skill that lists Sentry among its required tools.

    Read the bug report and the Sentry issue URL from the run's inputs.
In Sentry, read the issue's stack trace, tags and its latest events.
Fix the cause in the repository and add a test that reproduces the error.
Submit the pull request link and the Sentry issue URL as the step's outputs.
Leave resolving the Sentry issue to the run's Owner once the fix ships.
If the issue has no stack trace or you cannot reproduce it, report a blocker.
Get startedRead the setup guide