ActionsPulse 🚀

Real-time GitHub Actions observability through VS Code with GitHub Copilot

DORA Metrics • Cost Analysis • CI/CD Health • Security Compliance

_{☝️ This is an actual interactive HTML dashboard generated by ActionsPulse — see full tour below}

✨ What is ActionsPulse?

ActionsPulse is an Agentic MCP Server that brings DevOps observability directly into your IDE. Ask GitHub Copilot questions like:

💬 "Show me our DORA metrics for the last 30 days"
💬 "Which workflows are costing us the most?"
💬 "Generate a compliance report for SOC2"
💬 "What's our deployment frequency this month?"

And get interactive visual dashboards with actionable insights.

🎯 Features

🖼️ Dashboard Tour

ActionsPulse generates interactive HTML dashboards that you can open in any browser. Simply ask Copilot:

💬 "Generate DevOps reports for my organization"

Or use the generate_devops_reports tool directly. Here's a complete tour of what you get:

📊 Dashboard Overview — Executive summary with all key metrics at a glance

The main dashboard provides:

• 🎯 DevOps Maturity Score with visual gauge
• 📈 DORA Metrics summary (Deployment Frequency, Lead Time, Change Failure Rate, MTTR)
• ⚡ CI/CD Pipeline health overview
• 💰 Cost analysis highlights
• 🔒 Security & compliance status
• Quick navigation to detailed reports

📈 DORA Metrics — Industry-standard DevOps performance indicators

Track the four key DORA metrics:

• Deployment Frequency — How often you ship to production
• Lead Time for Changes — Time from commit to production
• Change Failure Rate — Percentage of deployments causing failures
• Mean Time to Restore — How quickly you recover from incidents

Each metric includes trend analysis and benchmarks against industry standards (Elite, High, Medium, Low performers).

⚡ CI/CD Pipeline Health — Workflow performance and reliability

Deep dive into your CI/CD pipelines:

• 🔄 Workflow success rates and trends
• ⏱️ Average run times with P95/P99 latencies
• 🚨 Failure analysis and common error patterns
• 📊 Per-repository and per-workflow breakdowns
• 🏃 Queue times and runner utilization

💰 Cost Optimization — Runner costs and savings opportunities

Understand and optimize your GitHub Actions spending:

• 💵 Total costs by runner type (GitHub-hosted vs self-hosted)
• 📊 Cost breakdown by repository, workflow, and OS
• 🎯 Actionable recommendations for cost savings
• 📈 Spending trends and projections
• ⚡ Efficiency metrics (cost per workflow, cost per minute)

🔒 Security & Compliance — Audit-ready compliance reports

Stay compliant and secure:

• ✅ Compliance framework coverage (SOC2, ISO27001, HIPAA, PCI-DSS)
• 🔍 Secret scanning status and alerts
• 🛡️ Code scanning findings
• 📋 Branch protection rule compliance
• 🔐 GHAS (GitHub Advanced Security) feature adoption

🎓 DevOps Maturity — Organizational capability assessment

Assess your DevOps maturity level:

• 📊 Overall maturity score with visual gauge
• 🎯 Category scores (CI/CD, Testing, Security, Monitoring, etc.)
• 📈 Improvement recommendations prioritized by impact
• 🏆 Benchmark against industry standards
• 📋 Actionable roadmap for advancement

💡 How to generate these dashboards:

Code

Copy

# Ask Copilot in natural language:
"Generate DevOps reports for the last 30 days"

# Or invoke the tool directly:
#generate_devops_reports --timeframe 30d

Reports are saved to timestamped folders as standalone HTML files — share them with your team or embed in internal wikis!

🚀 Quick Start

Install from MCP Registry

ActionsPulse is published to the official MCP Registry as io.github.tsviz/actions-pulse.

🌐 Web UI (Recommended) — Use the MCP Registry UI for 1-click installation into VS Code or Cursor:

1. Go to vemonet.github.io/mcp-registry
2. Search for "actions-pulse"
3. Click Install → Select your client (VS Code, Cursor)
4. Configure environment variables when prompted

Manual Docker Setup — Or follow the steps below to configure manually.

Prerequisites

• ✅ Docker installed
• ✅ GitHub Personal Access Token (fine-grained recommended)
• ✅ VS Code with GitHub Copilot

1. Create a Fine-Grained Personal Access Token

1. Go to GitHub Settings → Developer Settings → Personal Access Tokens → Fine-grained tokens

2. Click Generate new token

3. Configure basic settings:

   • Token name: actions-pulse-mcp
   • Expiration: 90 days (or per your security policy)
   • Resource owner: Select your organization
   • Repository access: All repositories

4. Set Repository permissions:

   Permission	Access	Required	Purpose
   Actions	Read	✅ Yes	Workflow runs, cache usage
   Administration	Read	✅ Yes	Billing data, repo settings
   Contents	Read	✅ Yes	Read config files from devops-config repo
   Custom properties	Read	✅ Yes	Read custom property values on repositories
   Deployments	Read	✅ Yes	Deployment frequency, environments (DORA)
   Discussions	Read	🔶 Optional	Community engagement metrics
   Environments	Read	✅ Yes	Environment protection rules
   Issues	Read	✅ Yes	Issue metrics, resolution times (DORA)
   Merge queues	Read	🔶 Optional	Merge queue adoption and wait times
   Metadata	Read	✅ Yes	Basic repo info (auto-granted)
   Pull requests	Read	✅ Yes	PR metrics, lead time, review times (DORA)

5. Set Organization permissions:

   Permission	Access	Required	Purpose
   Custom properties	Read	✅ Yes	Read property definitions/schemas at org level
   Custom properties for organizations	Read	✅ Yes	Read property values assigned to repositories

6. Set Organization permissions (continued):

   Permission	Access	Required	Purpose
   Members	Read	🔶 Optional	Team membership for productivity metrics
   Self-hosted runners	Read	🔶 Optional	Runner utilization metrics
   Administration	Read	✅ Yes	Org billing and settings

7. Optional permissions (for compliance features, requires GitHub Advanced Security):

   Permission	Access	Required	Purpose
   Secret scanning alerts	Read	❌ Optional	Compliance audit reports
   Code scanning alerts	Read	❌ Optional	Compliance audit reports

8. Click Generate token and save it securely