ActionsPulse
Real-time GitHub Actions observability: DORA Metrics, Cost Analysis, CI/CD Health dashboards
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: monitor production incidents.Similar tools
Listed for the same task: monitor production incidentsReviews
No review yet. Used ActionsPulse? Be the first to help others choose.What it does
ActionsPulse is an MCP server, a connector that lets an AI assistant use it as a tool. It is installed locally as a package and runs on your machine.
From the publisher's description, Electra Index matched it to 2 capabilities: debugging and devops automation. That makes it a candidate for tasks such as monitor production incidents or automate CI/CD pipelines.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · not tested by Electra IndexInstall package
- DOCKER
ghcr.io/tsviz/actions-pulse:v2.3.0· runs locally (stdio)
Required: GITHUB_TOKEN, GITHUB_ORG (get them from the publisher)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"actionspulse": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_TOKEN",
"-e",
"GITHUB_ORG",
"ghcr.io/tsviz/actions-pulse:v2.3.0"
],
"env": {
"GITHUB_TOKEN": "<your GITHUB_TOKEN>",
"GITHUB_ORG": "<your GITHUB_ORG>"
}
}
}
}Replace the values in <angle brackets>.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Install package | ghcr.io/tsviz/actions-pulse:v2.3.0 | DECLARED | SRC-001 Official MCP Registry | 18h ago |
| Package registries | oci | DECLARED | SRC-001 Official MCP Registry | 18h ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 18h ago |
| Remote access (hosted) | no | DECLARED | SRC-001 Official MCP Registry | 18h ago |
| Repository | https://github.com/tsviz/github-mcp-server-devops | DECLARED | SRC-001 Official MCP Registry | 18h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 18h ago |
| Version | 2.3.0 | DECLARED | SRC-001 Official MCP Registry | 18h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 18h ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is ActionsPulse still online?
Free alerts · no account▲ 0Do you publish ActionsPulse? Get it seen by people choosing a tool
For publishers · optionalLaunch Spotlight: 60 days of clearly labelled Sponsored visibility on the use-case pages where ActionsPulse already appears, plus the weekly Pulse. No click in 60 days? The next 60 days are free.
Sponsored placements never change a score or a rank.
Questions about ActionsPulse
How do I connect ActionsPulse?
Install the Docker package ghcr.io/tsviz/actions-pulse:v2.3.0. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
Does ActionsPulse need an API key or token?
Yes. The registry entry lists required values: GITHUB_TOKEN, GITHUB_ORG. Get them from the publisher.
What can I use ActionsPulse for?
Based on its description, it is most relevant to: monitor production incidents, automate CI/CD pipelines, fix bugs in a codebase.