Runzumi

com.runzumi.mcpPublished by mcp.runzumi.comOfficial publisherv0.1.3Updated Oct 26, 2026

Explore GitHub Actions job performance, compute costs and failures with Runzumi analytics.

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Runzumi is a remote MCP server that lets an assistant explore GitHub Actions job performance, compute costs and failures through Runzumi analytics.

What you can do
  • Explore GitHub Actions job performance data.
  • Review compute costs for CI jobs.
  • Investigate failures in workflow runs.
  • Query Runzumi's analytics from the assistant.
When to use it
Useful when a team wants an assistant to look into CI pipeline health on GitHub Actions — slow jobs, spending on compute, and recurring failures — without leaving the chat.
Requirements
A remote streamable HTTP endpoint at mcp.runzumi.com; no local package or runtime is needed. Authentication is OAuth and required, so a Runzumi account and a browser-based sign-in flow are expected. Network access to the endpoint is required.
Before you install
Access is granted through OAuth to a third-party analytics service, which will see the GitHub Actions data it analyzes. Review what repository and workflow data Runzumi ingests before connecting, and confirm the scope of the OAuth grant.

Installation

In SourceWeft

  1. Open Runzumi in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.runzumi.mcp%2Frunzumi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "runzumi": {
      "type": "http",
      "url": "https://mcp.runzumi.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.3LatestOct 18, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.