Can AI agents automate Sentry?

Sentry is automatable today through a first-party hosted MCP server and a public REST API. The recommended agent path is the remote MCP endpoint at https://mcp.sentry.dev/mcp, which uses OAuth and HTTP streaming to search errors, analyze performance, triage issues, read docs, and manage projects. Connections can be scoped to an organization or project. The older getsentry/sentry-mcp-stdio server is superseded by this remote server. Self-hosted Sentry does not use the hosted mcp.sentry.dev OAuth path; the current @sentry/mcp-server stdio transport is the documented way to point MCP at a self-hosted host with a user auth token, and Seer tools may be unavailable there. This record covers Sentry error monitoring, performance issues, and project management. It excludes Codecov and Sentry's separate MCP-monitoring product for other servers. The REST API at /api/0/ is broader than MCP: it covers organizations, teams, projects, issues, events, releases, monitors, and related resources, with OAuth 2.0 (authorization code, PKCE, device flow), organization tokens, personal tokens, and internal-integration tokens. Public endpoints are generally stable, but the API is versioned v0 and some endpoints are beta. Pricing lists MCP access on the free Developer plan and API plus third-party integrations from the Team plan. Official error SDKs exist for JavaScript, Python, and many other platforms; @sentry/api is the official TypeScript client for the management REST API. Two official CLIs exist: sentry-cli for CI release and artifact work, and the newer sentry CLI at cli.sentry.dev for issue management, Seer analysis, and authenticated API calls, including self-hosted login. Zapier and Microsoft Power Automate had no Sentry.io connector in the catalogs checked on 2026-08-22; Make and n8n do. Computer-use viability is unassessed.

Best path today: mcp · Overall automatability: 8/10