DORA numbers go wrong when a tool infers who owns what and quietly attributes work to the wrong team. Coderbuds says it does not guess, which is the right posture even though it means someone has to configure the mapping. The per-person token rule follows from the same principle: metrics read through a shared token stop meaning anything about a person.
Coderbuds' insights endpoint. Rather than a published tool list, their documentation describes the data surface: what is waiting for review, what is deployed, how the team ships, and the metrics over it.
- The review queue and current deploy state
- Shipping norms for the team
- DORA and SPACE metrics, and monthly rollups
OAuth 2.1, discovered through a 401 with protected-resource metadata, scope mcp:use; a bearer token is available for headless use. Tokens are per person and the documentation states they must not be committed or shared.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen