ActionsPulse

Provides real-time DevOps observability for GitHub Actions with DORA metrics, CI/CD health, cost analysis, and security compliance via MCP.

typescript

GitHub Stars

typescript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "tsviz-github-mcp-server-devops": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--env-file",
        "/path/to/.mcp.env",
        "-e",
        "GITHUB_ORG=your-org-name",
        "ghcr.io/tsviz/actions-pulse:latest"
      ],
      "env": {
        "GITHUB_ORG": "your-org-name",
        "GITHUB_TOKEN": "ghp_your_token"
      }
    }
  }
}

ActionsPulse is an MCP Server that brings real-time GitHub Actions observability into your development workflow. You can query metrics, usage, and compliance data and see interactive dashboards right from your MCP client, helping you optimize CI/CD, delivery speed, and security posture.

How to use

You connect to ActionsPulse from your MCP client and run queries or use the built-in dashboards to explore DevOps metrics. Start by configuring your MCP server in your client, then issue tool calls to retrieve DORA metrics, CI/CD health, cost analysis, and security insights. Dashboards render as interactive HTML reports you can export or share with your team.

How to install

Prerequisites you need before installing ActionsPulse.

Docker must be installed on the host where you run the MCP server
Use a fine-grained token with appropriate repository permissions
Ensure Copilot is enabled if you plan to leverage Copilot for report generation

Choose one of the following installation methods.

Option A: Use the MCP Registry Web UI (recommended) to install ActionsPulse into your MCP client.

Option B: Configure a local MCP server using Docker with a ready-made command from the examples.

{
  "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"
    }
  }
}

Additional configuration examples

If you prefer inline environment variables, you can use the following configuration example.

{
  "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"
    }
  }
}

Environment variables

The following environment variables are used to configure ActionsPulse when running in MCP mode.

Restart and verify

After adding or updating your MCP configuration, restart your MCP client or VS Code extension to pick up the new server settings. Verify the server is running by invoking a DevOps metric query or opening the Copilot-based dashboard for your organization.

Tips for use

Use the MCP client to request specific metrics by repository or timeframe to tailor dashboards to your team’s needs.
Save dashboards as standalone HTML reports to share with stakeholders.

Available tools

get_actions_usage_metrics

Analyze GitHub Actions usage and billing data with timeframe and breakdown options.

get_dora_metrics

Retrieve DORA metrics such as deployment frequency and lead time for changes.

get_workflow_insights

Fetch workflow insights with bottleneck detection and dependencies analysis.

generate_cost_optimization_report

Generate actionable recommendations to reduce Actions spending.

get_team_productivity_metrics

Assess team productivity using Actions and commit activity data.

get_compliance_audit_report

Produce compliance and security audit reports across frameworks.

Built by

VeilStrat

AI signals for GTM teams