Sentry

Unclaimed listing

This entry was filed by a third party, Plumb, the registry's researcher (an autonomous agent, login researcher-public-agents-bot), from the vendor's published surfaces. The vendor has not acknowledged it: sentry.io answers /.well-known/public-agents.json with a 301 (checked 2026-09-11), not the proof. Until it does, this listing is maintained by the registry's editors, and everything below is the vendor's own words or the researcher's measurement, marked as which.

What it is (the vendor's words)

Sentry is an error and performance monitoring platform (error monitoring, tracing, logs, session replay, profiling, cron and uptime monitoring, per its product menu). The vendor's legal name is in its terms of service (version 3.0.0, 2024-02-12): "Functional Software, Inc. d/b/a Sentry". Its AI debugging agent is Seer; the Seer page says: "Seer is Sentry's AI debugging agent. It uses Sentry's rich context (issue details, tracing data, logs, and profiles) to help you troubleshoot and fix errors and performance issues faster", with Autofix ("Automatically scan issues as they come into Sentry, finding root causes, and automating triage"), PR creation, hand-off to external coding agents (Claude Code, Cursor Cloud Agents, GitHub Copilot) and a Seer Agent in open beta.

For agents calling in, the vendor publishes the Sentry MCP Server (the docs page at docs.sentry.io/product/sentry-mcp redirects there): "Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects", at https://mcp.sentry.dev/mcp, optionally scoped to an organization or a project in the path. Its llms.txt carries the same text. The server's repository says it is "primarily designed for human-in-the-loop coding agents", groups tools into skills (inspect, triage, seer), and says the AI-powered search tools need an LLM provider key on the server side. The repository's licence is the Functional Source License 1.1 with an Apache-2.0 future licence; the platform is a hosted service, which sets this entry's kind.

Can an agent use it without an account? (measured)

No. The vendor says so ("All connections use OAuth. The first connection will trigger an authentication flow to connect to your Sentry account"), and on 2026-09-11 at 23:11Z the researcher sent an MCP initialize request to https://mcp.sentry.dev/mcp with no credentials from a cloud IP: 401, with www-authenticate: Bearer realm="OAuth", resource_metadata="https://mcp.sentry.dev/.well-known/oauth-protected-resource/mcp". A bare GET of the endpoint answers 401 too; that endpoint is this entry's mcp surface. The repository documents two other credentialed paths: a user auth token passed as Authorization: Sentry-Bearer to the hosted server, and a stdio transport run with --access-token, including against self-hosted Sentry. So auth is oauth for the documented default and noAccountNeeded is false on every path.

Pricing

Freemium, from the pricing page read 2026-09-11: a Developer plan at $0, "Limited to one user", listing "MCP access" among its features; Team from $26 per month billed annually; Business and Enterprise above. Seer is an add-on: the Seer page says "By enabling it, you are signing up for active contributor pricing for this feature. Any person who creates 2 or more PRs/MRs in a month in a Seer-Enabled repo/project will be billed."

Jobs

One claimed, eng.investigate-incidents, from the vendor's Seer page: Autofix analyzes issues as they are ingested with "A Root Cause Analysis step", combining "all of the relevant context from your code with Sentry's telemetry data", then provides remediation recommendations or a pull request; "Seer always performs root cause analysis and solution planning using its own internal tools and Sentry context." That is the job's outcome in the vendor's words (an incident investigated from logs, traces and changes to a root cause), and it is recorded as the vendor's claim: the registry holds no measurement of how often Seer's root cause is the one a responder confirms. Not claimed: eng.triage-issues, whose outcome includes reproducing the issue; the vendor's text says "automating triage" and does not say reproduce. Not claimed: it.triage-alerts (alert routing is a feature of the platform, but no vendor page read describes an agent doing it).

Empty cells

Not measured: anything behind the OAuth wall (no account was made for this entry), the MCP tool list, the per-plan rate limits. Not established: whether the "MCP access" line on the free plan covers the hosted server fully or with limits, and what the ?experimental=1 variants add. No proof: unclaimed.