Log inSubmit server
ActionsPulse logo

ActionsPulse

GitHub Actions observability through MCP, with DORA metrics, CI/CD health, cost analysis, and compliance reports.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install ActionsPulse

Run the project’s own setup commands, in order.

Setup steps from the project

ActionsPulse installs with its own commands rather than a config we can generate, so these are copied as-is. Run them in order in a terminal. Source: github.com

  1. 1. Install
    npm install
  2. 2. Run
    npm run build
  3. 3. Install
    docker build -t actions-pulse:local .
  4. 4. Start the server
    npm start

Overview

ActionsPulse MCP server connects GitHub Actions data to GitHub Copilot through an MCP-based IDE workflow. It analyzes DORA metrics, workflow health, runner usage, costs, security compliance, cache activity, and DevOps maturity. The server can generate timestamped interactive HTML dashboards for browser viewing and sharing. Reach for it when you need organization-level GitHub Actions reporting rather than individual workflow inspection.

Use cases

  • Measure DORA performance across repositories
  • Identify slow or unreliable GitHub Actions workflows
  • Analyze runner spending and savings opportunities
  • Generate compliance reports for security frameworks
  • Assess DevOps maturity and improvement priorities

Key features

  • DORA metrics with trends and benchmarks
  • CI/CD workflow health analysis
  • Runner cost and utilization reporting
  • Security and compliance dashboards
  • DevOps maturity assessment
  • Interactive HTML report generation

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

9/9 checks healthy over the last 56d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
Last commit9mo agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How ActionsPulse works

What ActionsPulse does

The ActionsPulse MCP server brings GitHub Actions observability into an IDE through GitHub Copilot. It reads organization and repository data to produce operational reports covering delivery performance, pipeline reliability, spending, security controls, and DevOps maturity.

Its reporting scope includes the four DORA measures: deployment frequency, lead time for changes, change failure rate, and mean time to restore. It also analyzes workflow success rates, run durations, failure patterns, queue times, runner utilization, and results by repository or workflow.

Cost reporting covers GitHub-hosted and self-hosted runners, with breakdowns by repository, workflow, and operating system. Security and compliance reports can include SOC2, ISO27001, HIPAA, and PCI-DSS coverage, along with secret scanning, code scanning, branch protection, and GitHub Advanced Security adoption.

How it works

ActionsPulse MCP server exposes DevOps reporting through MCP so an IDE assistant can respond to natural-language requests. In the documented workflow, a user asks GitHub Copilot for a report, such as a 30-day DevOps summary, or invokes the generate_devops_reports tool directly with a timeframe.

The server generates standalone interactive HTML files and stores them in timestamped folders. These files can be opened in a browser, shared with a team, or embedded in an internal wiki. The generated dashboard includes an overall view and detailed sections for DORA metrics, CI/CD health, cost optimization, security and compliance, and maturity assessment.

Setup and configuration

The documented setup uses Docker, a GitHub personal access token, and VS Code with GitHub Copilot. The project is published in the MCP Registry as io.github.tsviz/actions-pulse. Its installation flow also lists VS Code and Cursor as selectable clients through the MCP Registry UI.

The recommended token is fine-grained and should be scoped to the organization and required repositories. Required read permissions include Actions, Administration, Contents, Custom properties, Deployments, Environments, Issues, Metadata, Pull requests, and related repository data. Discussions and Merge queues are listed as optional permissions. Token expiration and repository access should follow the organization’s security policy.

The repository also provides a Docker-based manual setup path.

Tools and capabilities

The ActionsPulse MCP server supports reporting and analysis for:

  • DORA metrics and trend comparisons
  • Workflow success rates, durations, failures, queues, and runner usage
  • Runner costs, spending trends, projections, and efficiency
  • Repository, workflow, and operating-system cost breakdowns
  • Security and compliance status, including GHAS-related signals
  • Cache usage analytics
  • Team productivity metrics
  • DevOps maturity scoring and improvement recommendations
  • Interactive HTML dashboard generation through generate_devops_reports

Limitations and notes

The reports depend on the GitHub permissions granted to the token. Optional permissions affect access to discussions and merge-queue data. Organization and enterprise feature availability differs in the documented feature matrix, including cross-organization cost analysis and runner coverage.

It does not document other MCP clients, transport modes, individual API endpoints, or the exact environment-variable names. Generated reports are HTML files rather than a hosted dashboard service.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about ActionsPulse

ActionsPulse is an MCP server that connects GitHub Actions and GitHub repository and organization data to GitHub Copilot through an IDE. It provides DORA metrics, CI/CD health, cost analysis, compliance reporting, runner utilization, cache analytics, and interactive HTML dashboard generation via tools including generate_devops_reports.

Install it from the MCP Registry UI or configure the supplied Docker setup manually. The documented prerequisites are Docker, a fine-grained GitHub personal access token, and VS Code with GitHub Copilot. The registry installation flow supports selecting VS Code or Cursor and configuring environment variables.

ActionsPulse needs read access to Actions, Administration, Contents, Custom properties, Deployments, Environments, Issues, Metadata, and Pull requests. Discussions and Merge queues are optional. The token should be scoped to the target organization and repositories according to the documented setup.

Yes, Cursor is listed as an installation option in the MCP Registry UI.

Ask GitHub Copilot for a DevOps report or invoke the `generate_devops_reports` tool directly with a timeframe such as `30d`. The server saves standalone interactive HTML reports in timestamped folders for browser viewing, sharing, or embedding in an internal wiki.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewActionsPulse AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/actionspulse?style=directory)](https://allmcps.com/mcp/actionspulse)
HTML Embed
<a href="https://allmcps.com/mcp/actionspulse"><img src="https://allmcps.com/api/badge/actionspulse?style=directory" alt="ActionsPulse on AllMCPs" /></a>