koalr-mcp 0.3.2 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/server.js +26 -1
  2. package/package.json +13 -3
package/dist/server.js CHANGED
@@ -10,10 +10,35 @@ import { registerIncidentTools } from './tools/incidents.js';
10
10
  import { registerAiAdoptionTools } from './tools/ai-adoption.js';
11
11
  import { registerOrganizationTools } from './tools/organization.js';
12
12
  import { registerDeployRiskTools } from './tools/deploy-risk.js';
13
+ const SYSTEM_PROMPT = `You are connected to Koalr, a deployment intelligence platform for engineering teams.
14
+
15
+ ## What this server does
16
+ Koalr tracks pull requests, DORA metrics, deploy risk, test coverage, incidents, and developer productivity across GitHub-connected repositories. All tools are read-only.
17
+
18
+ ## When to use which tool
19
+ - **Broad overview**: start with get_org_health
20
+ - **Merge safety**: use score_pr_for_deploy_risk — pass the PR number, file list, and size
21
+ - **Delivery performance**: get_dora_summary (or get_dora_trend for week-over-week changes)
22
+ - **Stale/blocked work**: get_at_risk_prs then get_open_prs for detail
23
+ - **Team or repo drill-down**: list_teams → get_team, or list_repositories → get_repository
24
+ - **Individual developer**: get_developer (requires GitHub login) or list_top_contributors
25
+ - **Incidents**: list_recent_incidents returns MTTR and impact
26
+ - **Coverage**: get_coverage_summary by repository
27
+ - **AI tool usage**: get_ai_adoption_summary or get_ai_adoption_trend
28
+
29
+ ## Key parameters
30
+ - Most tools accept optional \`from\`/\`to\` ISO date strings to set the time window (default: last 30 days)
31
+ - Use \`teamId\` to scope metrics to a specific team — call list_teams first to find IDs
32
+ - Use \`repositoryId\` to scope metrics to a single repo — call list_repositories first
33
+
34
+ ## Risk score interpretation
35
+ score_pr_for_deploy_risk returns 0–100. 0–39 = low, 40–69 = medium, 70–89 = high, 90–100 = critical. Scores above 70 warrant a review before merging.`;
13
36
  export function createServer(apiKey) {
14
37
  const server = new McpServer({
15
38
  name: 'koalr',
16
- version: '0.3.0',
39
+ version: '0.3.2',
40
+ }, {
41
+ instructions: SYSTEM_PROMPT,
17
42
  });
18
43
  // Register all tool groups (apiKey is threaded through for hosted HTTP mode)
19
44
  registerDoraTools(server, apiKey);
package/package.json CHANGED
@@ -1,15 +1,25 @@
1
1
  {
2
2
  "name": "koalr-mcp",
3
- "version": "0.3.2",
3
+ "version": "0.4.0",
4
4
  "description": "Koalr MCP server — connect engineering metrics to AI agents",
5
5
  "type": "module",
6
6
  "license": "MIT",
7
7
  "keywords": [
8
- "koalr",
9
8
  "mcp",
9
+ "koalr",
10
10
  "engineering-metrics",
11
11
  "dora",
12
- "deploy-risk"
12
+ "deploy-risk",
13
+ "devops",
14
+ "github",
15
+ "pull-requests",
16
+ "code-review",
17
+ "developer-productivity",
18
+ "deployment",
19
+ "metrics",
20
+ "ai-agent",
21
+ "claude",
22
+ "model-context-protocol"
13
23
  ],
14
24
  "homepage": "https://docs.koalr.com/docs/features/mcp-server",
15
25
  "repository": {