ActionsPulse

ActionsPulse 🚀

✨ 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:

💡 How to generate these dashboards:

# 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

2. Configure MCP Server

Option A: Using env-file (Recommended)

Add to your ~/.mcp.env:

GITHUB_TOKEN=ghp_your_fine_grained_token_here

{  "servers": {    "actions-pulse": {      "command": "docker",      "args": [        "run", "-i", "--rm",        "--env-file", "/path/to/.mcp.env",        "-e", "GITHUB_ORG=your-org-name",        "ghcr.io/tsviz/actions-pulse:latest"      ],      "type": "stdio"    }  }}

Option B: Direct Environment Variables

{  "servers": {    "actions-pulse": {      "command": "docker",      "args": [        "run", "-i", "--rm",        "-e", "GITHUB_TOKEN=ghp_your_token",        "-e", "GITHUB_ORG=your-org-name",        "ghcr.io/tsviz/actions-pulse:latest"      ],      "type": "stdio"    }  }}

3. Environment Variables Reference

Repo Filter Precedence

When determining which repositories to query, ActionsPulse uses this precedence (highest to lowest):

Tip: For quick setup without a config repo, just set DEFAULT_REPO_FILTER in the MCP Registry installer. For richer metadata (team, tier, compliance tags), use inventory.yaml.

4. Configuration Files (Optional)

By default, ActionsPulse queries ALL repositories in your organization via the GitHub API — no configuration files are required. You can filter repos dynamically using tool parameters like repo_filter.

The optional configuration files let you define persistent metadata (teams, tiers, compliance tags) for filtering and reporting. There are two approaches:

Option A: Remote Config Repository (Recommended for Teams)

Create a devops-config repository in your organization with the following structure:

devops-config/├── devops-config.yaml          # Main configuration├── repositories/│   └── inventory.yaml          # List of repos to monitor├── policies/│   ├── workflow-policies.yaml  # CI/CD standards│   └── security-policies.yaml  # Security requirements└── dashboards/                 # Dashboard configs

The MCP server will automatically discover and load from {org}/devops-config repo.

Option B: Local Config Files (For Development/Testing)

Mount a local config directory into the Docker container:

{  "servers": {    "actions-pulse": {      "command": "docker",      "args": [        "run", "-i", "--rm",        "--env-file", "/path/to/.mcp.env",        "-e", "GITHUB_ORG=your-org-name",        "-e", "DEVOPS_CONFIG_PATH=/app/config",        "-v", "/path/to/your/config:/app/config:ro",        "ghcr.io/tsviz/actions-pulse:latest"      ],      "type": "stdio"    }  }}

Repository Inventory Example

apiVersion: actions-pulse/v1kind: RepositoryInventorymetadata:  name: my-inventory  version: "1.0.0"  description: "Repositories to monitor"
spec:  discovery:    enabled: false  # Only monitor explicit repos
  repositories:    - name: my-app      team: platform      tier: tier-1      compliance: [SOC2]      tags: [java, production]
    - name: my-api      team: backend      tier: tier-2      tags: [nodejs, staging]

Repository Tiers Quick Reference

See docs/ARCHITECTURE.md for complete tier definitions, compliance requirements, and alerting behavior.

5. Restart VS Code

After updating mcp.json, restart VS Code to pick up the new MCP server. You can verify the server is running by opening GitHub Copilot Chat and asking about your DevOps metrics.

🛠️ Available Tools

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- timeframe: '24h' | '7d' | '30d'- breakdown: 'repository' | 'workflow' | 'runner_type'

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- timeframe: '7d' | '30d' | '90d'- repo_filter: Comma-separated list of repositories (optional)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- timeframe: '7d' | '30d' | '90d'- repo_filter: Comma-separated list of repositories (optional)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- repo_name: Specific repository (optional)- workflow_id: Specific workflow (optional)- timeframe: '1h' | '6h' | '24h' | '7d'

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- runner_type: 'self-hosted' | 'github-hosted' | 'all'- include_costs: Include cost analysis (default: true)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- repo_name: Specific repository (optional)- timeframe: '24h' | '7d' | '30d'

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- include_recommendations: Include actionable recommendations (default: true)- target_savings_percentage: Target savings (5-50, default: 20)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- repo_name: Repository name (required)- workflow_name: Workflow name or filename (required)- analyze_dependencies: Analyze job dependencies (default: true)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- team_slug: Team slug (optional)- include_individuals: Include individual metrics (default: false)- timeframe: '7d' | '30d' | '90d'

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- compliance_framework: 'SOC2' | 'ISO27001' | 'HIPAA' | 'PCI-DSS' | 'CUSTOM'- include_secrets_scan: Include secret scanning (default: true, requires GHAS)

📊 DORA Metrics & Developer Experience

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- timeframe: '7d' | '30d' | '90d'- repo_filter: Comma-separated list of repositories (optional)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- timeframe: '7d' | '30d' | '90d'- repo_filter: Comma-separated list of repositories (optional)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- timeframe: '7d' | '30d' | '90d'- repo_name: Specific repository (optional)- include_stale: Include stale PR analysis (optional)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- timeframe: '7d' | '30d' | '90d'- repo_name: Specific repository (optional)- label_filter: Filter by label (optional)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- timeframe: '7d' | '30d' | '90d'- environment: Filter by environment (optional)- repo_filter: Comma-separated list of repositories (optional)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- repo_filter: Comma-separated list of repositories (optional)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- repo_name: Specific repository (optional)- timeframe: '7d' | '30d' | '90d'

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- repo_name: Specific repository (optional)

🏷️ Custom Properties

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)

Parameters:- org_name: Organization name (optional if GITHUB_ORG is set)- property_name: Custom property name (e.g., team, tier, compliance)- property_value: Property value to filter by (optional)

🏢 Enterprise Features (Optional)

GITHUB_ENTERPRISE_SLUG=your-enterprise-slug

🔧 Development

npm installnpm run builddocker build -t actions-pulse:local .

export GITHUB_TOKEN=ghp_your_tokenexport GITHUB_ORG=your-orgnpm start

🤖 Automating DevOps Reports with GitHub Actions

You can automate DevOps report generation using GitHub Copilot CLI with ActionsPulse MCP server in a GitHub Actions workflow. This enables scheduled weekly reports, on-demand analysis, and automatic issue creation with insights.

How It Works

1. Install Copilot CLI in the workflow runner
2. Configure ActionsPulse MCP with your GitHub token
3. Run Copilot with a prompt to generate reports using MCP tools
4. Create issues with the generated report

Example Workflow

See .github/workflows/weekly-devops-report.yml for a complete working example.

- name: Setup MCP config  env:    GITHUB_TOKEN: ${{ secrets.GH_PAT_DEVOPS }}  run: |    mkdir -p ~/.copilot    printf '%s\n' '{      "mcpServers": {        "actions-pulse": {          "command": "docker",          "args": ["run", "-i", "--rm", "-e", "GITHUB_TOKEN='"$GITHUB_TOKEN"'", "-e", "GITHUB_ORG=your-org", "ghcr.io/tsviz/actions-pulse:latest"],          "tools": ["*"]        }      }    }' > ~/.copilot/mcp-config.json
- name: Generate DevOps Report  env:    GITHUB_TOKEN: ${{ secrets.GH_PAT_DEVOPS }}    GH_TOKEN: ${{ secrets.GH_PAT_DEVOPS }}  run: |    copilot --yolo \      --disable-builtin-mcps \      --additional-mcp-config @$HOME/.copilot/mcp-config.json \      --prompt "Use the actions-pulse MCP tools to generate a DevOps report..."

Key Copilot CLI Flags

Tips

• Use $HOME instead of ~ in the config path — tilde is not expanded in @file arguments
• Embed the token in args — the env block in MCP config doesn't pass variables to Docker
• Include "tools": ["*"] in your MCP config — this field is required

📚 Documentation

Example Configurations

Ready-to-use configuration examples are available in the examples/ directory:

�📄 License

MIT