# ActionsPulse [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/tsviz/github-mcp-server-devops  
**GitHub Stars:** 3  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/actionspulse

## Description
Real-time GitHub Actions observability: DORA Metrics, Cost Analysis, CI/CD Health dashboards.

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://github.com/tsviz/github-mcp-server-devops), copied verbatim. Run them in order; they are not an mcpServers config.

1. Install:

```sh
npm install
```

2. Run:

```sh
npm run build
```

3. Install:

```sh
docker build -t actions-pulse:local .
```

4. Start the server:

```sh
npm start
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/actionspulse/readme_