project-risk-mcp latest

MCP server that aggregates data from Jira, Zoom, and GitHub to compute a weighted, multi-dimensional project risk score (0–100). Exposes 10 tools and 2 resources to give Claude Code instant visibility into project health.

"Give me a full risk assessment for PROJ-123"
→ 58/100 HIGH  |  Trend: DEGRADING
  Timeline 62 🔴  |  Team 55 🔴  |  Comms 38 🟡  |  Code 48 🟡
  Top threat: Burn rate lag 35% — completing 35/60 sprint points

Quick Install

Option 1: Install from npm (Recommended)

npm install -g project-risk-mcp

Then add to Claude Code:

claude mcp add --transport stdio --scope user \
  --env GITHUB_PERSONAL_ACCESS_TOKEN="ghp_..." \
  --env ZOOM_ACCESS_TOKEN="eyJ..." \
  --env JIRA_API_TOKEN="ATAT..." \
  project-risk-mcp \
  -- project-risk-mcp

Option 2: Run with npx (No Installation)

claude mcp add --transport stdio --scope user \
  --env GITHUB_PERSONAL_ACCESS_TOKEN="ghp_..." \
  --env ZOOM_ACCESS_TOKEN="eyJ..." \
  --env JIRA_API_TOKEN="ATAT..." \
  project-risk-mcp \
  -- npx project-risk-mcp

Option 3: Build from Source

git clone https://github.com/shaifulshabuj/project-risk-mcp.git
cd project-risk-mcp
npm install && npm run build

Then add to Claude Code:

claude mcp add --transport stdio --scope user \
  --env GITHUB_PERSONAL_ACCESS_TOKEN="ghp_..." \
  --env ZOOM_ACCESS_TOKEN="eyJ..." \
  --env JIRA_API_TOKEN="ATAT..." \
  project-risk-mcp \
  -- node /ABSOLUTE/PATH/TO/project-risk-mcp/build/index.js

4. Use in Claude Code

claude
# Then ask:
"What's the risk on project PROJ-123?"
"Generate an executive risk report for PROJ-123"
"Post risk report for PROJ-123 to #engineering-alerts"

The 4 Risk Dimensions

| Dimension | Weight | Key Signals | |-----------|--------|------------| | Timeline & Delivery | 35% | Burn rate lag, milestone drift, velocity drop, open blockers | | Team Velocity & Capacity | 28% | Sprint blockers, velocity trend, critical bugs, meeting attendance | | Communication & Cadence | 20% | Days since last meeting, action-item follow-through, doc backlog | | Code Quality & PR Health | 17% | CI failure rate, stale PRs, time-to-merge, reviewer concentration |

All 10 Tools

| Tool | What it returns | |------|----------------| | assess_project_risk | Full 4-dimension assessment, top threats, alerts, trend | | get_risk_score | Quick score (0–100) and risk level | | get_timeline_risk | Timeline dimension score and signals | | get_team_risk | Team dimension score and signals | | get_communication_risk | Communication dimension score and signals | | get_code_quality_risk | Code quality dimension score and signals | | get_risk_history | Up to 30 daily assessment snapshots | | generate_risk_report | Formatted report (summary/detailed/executive) | | get_risk_alerts | All HIGH and CRITICAL alerts | | notify_slack | Run assessment and post to a Slack channel |

2 Resources

| URI | Returns | |-----|---------| | risk://{project_id}/dashboard | Condensed snapshot (score, trend, alert counts) | | risk://{project_id}/scorecard | Weighted dimension breakdown (how score was computed) |

No Credentials? No Problem

All upstream integrations fall back to deterministic mock data if a credential is missing or the upstream is down. You can explore all tools and get realistic (simulated) responses without connecting to any real service.

Requirements

• Node.js ≥ 18.0.0
• Docker (for GitHub MCP; optional — falls back to mock without it)
• API tokens for the services you want real data from

Changelog

See CHANGELOG.md for version history and release notes.

Support

For issues, feature requests, or questions, please open an issue on GitHub.

License

This project is licensed under the MIT License.