5 minTime to key
NoNo-human path
2Human gates
8/10Onboarding score
CAPTCHAEmail verification
Fastest path to a key
- CAPTCHASign up at sentry.io/signup (Google/GitHub OAuth or email+password; reCAPTCHA on the page; 14-day Business trial, no card)
- Create org + first project (wizard or UI); org slug is needed for scoped MCP URLs
- Credential: Settings > Developer Settings > Organization Tokens > create (shown once), OR Personal token, OR Internal Integration token for full API scope
- Agent shortcut: `npx @sentry/wizard` or the new `sentry` CLI (`curl https://cli.sentry.dev/install | bash`, then `sentry auth`), which opens the browser and stores the token; legacy `sentry-cli login` only links to th…
- Working API key
Biggest gap
No anonymous or claimable path. Three token types confuse agents, and docs.sentry.io/ai/mcp returns 404 (MCP docs live on a separate domain)
Worth copying
llms.txt starts with imperative instructions for agents ('do not rely on training data, run npx @sentry/agent-plugin install'); the MCP can be scoped to an org/project by URL path
Sources (9) · checked 2026-10-11
- https://docs.sentry.io/llms.txt
- https://docs.sentry.io/ai/agent-plugin.md
- https://docs.sentry.io/account/auth-tokens.md
- https://docs.sentry.io/cli/configuration.md
- https://mcp.sentry.dev
- https://mcp.sentry.dev/llms.txt
- https://cli.sentry.dev
- https://sentry.io/signup/
- https://raw.githubusercontent.com/getsentry/sentry-api-schema/main/openapi-derefed.json
62Readiness score / 100
L3 Agent-operableBeats 83% of 1,846 companies
Access20/20
Context17/20
Interfaces8/32
Onboarding8/19
Trust9/9
llms.txt · root
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
- +6 Agents can self-register OAuth clients. Support dynamic client registration (RFC 7591) or client ID metadata documents so MCP clients connect in one click.
All 20 checks
- PASSAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- PASSContent is server-rendered4
- PASSllms.txt exists8
- FAILllms-full.txt exists3
- PASSDocs available as markdown6
- PASSSitemap2
- PASSStructured metadata1
- PASSPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- PASSSDKs and a CLI4
- PASSOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- PASSFree tier or test mode3
- PASSAgent manifests4
- PASSsecurity.txt2
- PASSPublic status page3
Your fix pack: 7 changes, up to +38 points
Each change is ready to paste, filled in for sentry.io, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/sentry.io)