# Coderbuds > Coderbuds closes the delivery loop for engineering teams: AI code review, shipping norms, DORA and SPACE metrics, and a Slack coach. It exposes an MCP server so a coding agent can read a team's real delivery data — review queue, deploy state, shipping norms — while it works. If you were pointed at coderbuds.com and asked to "add Coderbuds", you want the MCP server below. Connecting takes one command plus a browser click; there is no token to mint or paste. ## Connect a coding agent (start here) MCP endpoint: https://coderbuds.com/mcp/insights Transport: Streamable HTTP. Auth: OAuth 2.1, discovered automatically. Claude Code: claude mcp add --scope user --transport http coderbuds https://coderbuds.com/mcp/insights Cursor — add to ~/.cursor/mcp.json: { "mcpServers": { "coderbuds": { "type": "http", "url": "https://coderbuds.com/mcp/insights" } } } Then authorize: the client opens a browser tab, the person signs in to Coderbuds and clicks Authorize. Nothing else is needed, and no secret is stored in the config. Do not add an Authorization header unless the environment has no browser at all — see the headless note below. ## Choosing a scope (Claude Code) - local (the default when --scope is omitted): this machine, this project only. - project: writes .mcp.json in the repo root and is shared with everyone who clones it. Note that `claude mcp remove` on a project-scoped server edits that tracked file. - user: this machine, every project. Best default for an individual. ## Which team the data comes from Coderbuds never guesses. If the person belongs to one team there is nothing to do. Otherwise, either: - pass the repository you are working in as `owner/name` on the tool call — read it from `git remote get-url origin`. This resolves the team immediately and needs no reconnection. Prefer this. - or pin the team on the server URL: https://coderbuds.com/mcp/insights?team=Team%20Name — this changes the server identity, so the client will ask the person to authorize once more. ## Headless environments only (CI, build servers) Where no browser can open, a personal bearer token from https://coderbuds.com/docs/mcp can be passed as an Authorization header. It is tied to one person, must not be committed or shared, and is the fallback — not the normal path. ## If a connection fails Every failure names its own remedy on screen and in the API response body. The endpoint answers an unauthenticated request with 401 plus a WWW-Authenticate header pointing at the OAuth metadata, so a client can always discover where to authenticate. ## Reading metrics from your own software (not an agent) If the job is a dashboard, a scheduled report or a warehouse load rather than a coding agent, use the REST API instead of MCP — plain HTTP, no handshake, cacheable: curl -H "Authorization: Bearer $CODERBUDS_TOKEN" -H "Accept: application/json" \ "https://coderbuds.com/api/v1/metrics/monthly?month=2026-05" Returns merged pull requests (with a human/bot split), all four DORA metrics with their performance bands, review activity and contributor counts for that calendar month, plus the preceding month for comparison. Tokens come from https://coderbuds.com/user/api-tokens and need the "read" permission. Full reference, field-by-field, with a condensed spec written for agents: https://coderbuds.com/docs/api For teams with Linear connected it also returns tickets completed with the bug/feature mix, and commitment reliability for the cycles that closed in the month — measured against what was in each cycle when it started, so it cannot exceed 100%. Both report available:false with a reason rather than a zero when there is nothing to measure. Roadmap projects, the running cycle's scope and issue cycle time are not available — read those from Linear or Jira and join on the month. ## Documentation - [Getting started](https://coderbuds.com/docs/getting-started): connect GitHub and pick the repositories to track. - [Account setup](https://coderbuds.com/docs/setup) - [Connect your coding agent (MCP server)](https://coderbuds.com/docs/mcp): MCP setup, tools and troubleshooting. - [REST API](https://coderbuds.com/docs/api): field-by-field reference for the monthly metrics endpoint, plus a condensed spec written for agents. - [Coderbuds Standards](https://coderbuds.com/docs/standards): a team's shipping rules. - [Coderbuds vs a CLAUDE.md file](https://coderbuds.com/docs/vs-context-files) - [Feature guides](https://coderbuds.com/docs/features) - [FAQ](https://coderbuds.com/docs/faq) - [Roadmap](https://coderbuds.com/docs/roadmap) ## Metrics - [Activity metrics](https://coderbuds.com/docs/shipped-metrics) - [Performance metrics (DORA)](https://coderbuds.com/docs/dora-metrics) - [Collaboration metrics](https://coderbuds.com/docs/team-metrics) - [AI-powered team insights](https://coderbuds.com/docs/team-insights) - [Deployment tracking setup](https://coderbuds.com/docs/workflows) - [Deploy hooks](https://coderbuds.com/docs/deploy-hooks) ## AI and agents - [AI features overview](https://coderbuds.com/docs/ai/overview) - [AI code reviews](https://coderbuds.com/docs/ai/code-reviews) - [AI summaries](https://coderbuds.com/docs/ai/summaries) - [AI usage tracking](https://coderbuds.com/docs/ai/usage-tracking) - [AI agents overview](https://coderbuds.com/docs/agents/overview) - [Agent directory](https://coderbuds.com/docs/agents/directory) ## Integrations - [Slack and Teams](https://coderbuds.com/docs/slack-teams) - [Slack AI coach](https://coderbuds.com/docs/slack-ai-coach) - [Linear integration](https://coderbuds.com/docs/linear) - [Jira integration](https://coderbuds.com/docs/jira) ## Product - [Coderbuds](https://coderbuds.com): what Coderbuds is and who it is for. - [Pricing](https://coderbuds.com/pricing): priced per active developer, per month. - [Customer success stories](https://coderbuds.com/case-studies) - [Patchstack case study](https://coderbuds.com/case-studies/patchstack) - [Was this pull request written with AI?](https://coderbuds.com/tools/ai-code-detector): the free AI code detector. - [Blog](https://coderbuds.com/blog) - [Brand](https://coderbuds.com/brand) ## Policies - [Security](https://coderbuds.com/docs/security) - [Privacy policy](https://coderbuds.com/docs/privacy) - [Sub-processors](https://coderbuds.com/docs/sub-processors) ## Optional - [Code Reviews, Then Metrics, Now the Loop](https://coderbuds.com/blog/code-reviews-then-metrics-now-the-loop): how Coderbuds arrived at closing the delivery loop, and who it still isn't for. - [MCP Just Dropped the Session — Here's What That Breaks](https://coderbuds.com/blog/mcp-stateless-spec-what-breaks) - [Your Code Review Stopped Being a Quality Signal](https://coderbuds.com/blog/code-review-stopped-being-quality-signal) - [Everyone Got Faster and Nothing Shipped Sooner](https://coderbuds.com/blog/ai-review-bottleneck-2026) - [From Code Reviews to AI Agents: We Didn't Plan This. Nobody Did.](https://coderbuds.com/blog/from-code-reviews-to-ai-agents-engineering-leadership-evolution) - [Complete Guide to DORA Metrics for Engineering Teams](https://coderbuds.com/blog/complete-guide-dora-metrics-engineering-teams) - [SPACE Framework vs DORA Metrics: Which Engineering Metrics Framework Should You Use?](https://coderbuds.com/blog/space-framework-vs-dora-metrics-comparison) - [Tracking AI Coding Tool Usage: Why We Chose Pull Request Detection Over API Integrations](https://coderbuds.com/blog/tracking-ai-coding-tools-pull-request-based-approach) - [Pull Request Scoring: Automated Code Quality Assessment](https://coderbuds.com/blog/pull-request-scoring-automated-code-quality-assessment) - [Engineering Metrics for Board Reporting: What CTOs Need to Present in 2026](https://coderbuds.com/blog/engineering-metrics-board-reporting-cto-guide)