Server Details
Connect engineering metrics, DORA performance, and deploy risk scoring to any AI assistant. Score PRs for deployment risk using a 36-signal model, query team health, incidents, coverage, and more.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
20 toolsget_ai_adoption_summaryInspect
Get AI coding tool adoption metrics including GitHub Copilot acceptance rate, Cursor active users, AI-generated code percentage, and suggestions per developer. Use this to understand how the team is using AI coding assistants.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_ai_adoption_trendInspect
Get the trend of AI tool adoption over time showing weekly active users, acceptance rates, and code attribution percentages. Use this to track whether AI tool adoption is growing or declining.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Number of days to look back for trend data (default: 90) |
get_at_risk_prsInspect
Get pull requests at risk of becoming long-running or blocked. These are PRs that have been open for more than 3 days, have no reviews, or are very large. Use this to prompt engineering leads to take action on blocked work.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_coverage_summaryInspect
Get test coverage summary per repository showing overall coverage percentage, lines covered, and coverage trend. Use this to understand testing health and identify repositories with low coverage.
| Name | Required | Description | Default |
|---|---|---|---|
| repositoryId | No | Filter to a specific repository by ID. Omit to see all repositories. |
get_developerInspect
Get metrics for an individual developer including their PR throughput, review activity, average cycle time, and code contributions. Use this when asked about a specific engineer's activity or productivity.
| Name | Required | Description | Default |
|---|---|---|---|
| login | Yes | GitHub username / login of the developer (e.g. "jsmith") |
get_dora_summaryInspect
Get DORA metrics (deploy frequency, lead time for changes, change failure rate, MTTR) for the organization or a specific team. Use this to understand overall engineering delivery performance and reliability.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | End date as ISO string (e.g. 2024-01-31). Defaults to today. | |
| from | No | Start date as ISO string (e.g. 2024-01-01). Defaults to 30 days ago. | |
| teamId | No | Team ID to filter metrics for a specific team |
get_dora_trendInspect
Get DORA metric trend over time to see how deployment frequency, lead time, change failure rate, or MTTR has changed week over week. Useful for spotting regressions or improvements.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Number of days to look back (default: 90). Max recommended: 365. | |
| metric | Yes | Which DORA metric to trend: deploy_frequency, lead_time, change_failure_rate, or mttr | |
| teamId | No | Team ID to filter metrics for a specific team |
get_open_prsInspect
List currently open pull requests with their age in hours, size (additions + deletions), and reviewer assignments. Use this to identify stale or large PRs that may be blocking the team.
| Name | Required | Description | Default |
|---|---|---|---|
| highRiskOnly | No | If true, only return PRs that are large (>500 lines), old (>72h open), or have no reviewers | |
| repositoryId | No | Filter to a specific repository by ID |
get_org_healthInspect
Get a comprehensive organization health snapshot: DORA performance tier (Elite/High/Medium/Low), cycle time percentile vs industry benchmarks, test coverage percentage, number of active teams, and incident rate. Use this as the first tool to get a high-level picture of engineering health.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_pr_summaryInspect
Get pull request metrics including cycle time (time from first commit to merge), throughput (PRs merged per week), review health (time to first review, reviewer distribution), and PR size trends. Use this to assess code review efficiency.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Number of days to look back (default: 30) | |
| teamId | No | Team ID to filter to a specific team |
get_repositoryInspect
Get detailed metrics for a specific repository including deployment frequency, PR cycle time, contributor count, and code health indicators. Use this when asked about a specific codebase.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Repository name (e.g. "my-service") or full name with owner (e.g. "org/my-service") |
get_teamInspect
Get details and metrics for a specific team including DORA performance, cycle time, and member count. Use this when asked about a specific team's engineering health.
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | Yes | The team ID (use list_teams to find team IDs) |
get_well_being_summaryInspect
Get team well-being scores across pillars: focus time (uninterrupted deep work hours), meeting load (percentage of time in meetings), context switching (task interruptions per day), and burnout risk indicators. Use this to understand developer experience and identify teams under stress.
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | No | Team ID to filter well-being data. Omit for org-wide summary. |
list_recent_incidentsInspect
List recent production incidents from PagerDuty or OpsGenie with their severity, MTTR (mean time to recovery), and affected services. Use this to understand reliability posture or investigate a recent outage.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Number of days to look back for incidents (default: 30) | |
| limit | No | Maximum number of incidents to return (default: 20) |
list_repositoriesInspect
List all repositories connected to Koalr with their health scores, activity levels, and basic stats. Use this to get an overview of the codebase landscape or find repository IDs for filtering.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of repositories to return (default: 50, max: 200) |
list_team_membersInspect
List all members of a specific team with their GitHub logins and roles. Use this to understand team composition or find developer logins for the get_developer tool.
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | Yes | The team ID (use list_teams to find team IDs) |
list_teamsInspect
List all engineering teams in the organization with their member counts and slugs. Use this to discover team IDs needed for filtering other metrics tools.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_top_contributorsInspect
List the most active contributors ranked by commits and PRs merged over a time window. Use this to identify key contributors, bus-factor risks, or to recognize top performers.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Time window in days to measure activity (default: 30) | |
| limit | No | Number of contributors to return (default: 10, max: 50) |
score_pr_for_deploy_riskInspect
Score a specific pull request for deployment risk using Koalr's 36-signal model. Returns a 0-100 risk score with a detailed factor breakdown covering change entropy, DDL migration detection, author file expertise, PR size, CODEOWNERS violations, and more. Use this to answer "How risky is this PR?" or "Should we merge this before the release?".
| Name | Required | Description | Default |
|---|---|---|---|
| sha | Yes | Head commit SHA. | |
| body | No | PR description body (used to detect risky phrases). | |
| repo | Yes | Repository name. Example: "api-service". | |
| files | No | List of changed file paths. Used for DDL detection, CODEOWNERS analysis, and entropy calculation. More accurate results when provided. | |
| owner | Yes | GitHub repository owner (org or user). Example: "acme". | |
| title | Yes | PR title. | |
| prNumber | Yes | Pull request number. | |
| additions | Yes | Lines added. | |
| deletions | Yes | Lines deleted. | |
| hasReview | No | Whether the PR has at least one review (any type). | |
| authorLogin | No | GitHub login of the PR author. | |
| hasApproval | No | Whether the PR has at least one approving review. | |
| changedFiles | Yes | Number of files changed. |
searchInspect
Search across all Koalr entities: developers (by name or GitHub login), repositories (by name), pull requests (by title or branch), and teams (by name). Use this when you need to find an entity before using a more specific tool.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Limit results to a specific entity type. Omit to search all types. | |
| query | Yes | Search query text (e.g. "payments", "alice", "auth-service") |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!