Runzumi × your assistant
Your CI.
A clearer conversation.
Explore Runzumi in Claude and Claude Code. Ask about GitHub Actions job performance, compute usage and failed runs, with evidence from the repositories you can access.
Read-only insights. Your existing access applies.
A question worth asking
From a question
to a useful next step.
Choose a scenario to explore a sample prompt and response. All data below is simulated; this is an illustration of the workflow, not a live assistant session or benchmark.
Try asking
“Show GitHub Actions job duration, queue time and success rate for my Runzumi repository this week.”
Separate running from waiting.
See recorded job duration, queue time and outcomes for a selected repository and time range. These metrics describe your Runzumi jobs, not every runner in the market.
Repository statistics · example week
- Job attempts
- 24
- Average duration
- 2m 18s
- Average queue
- 8s
23 of 24 job attempts succeeded (95.8%). Average execution time was 2m 18s; average queue time was 8s. These figures alone do not explain why a job waited.
Averages across 24 simulated job attempts. Queue time and execution time are reported separately.
Make the connection
Bring the right
account along.
You need a Runzumi account with access to the workspace and repository you want to investigate, plus a client that supports remote MCP and OAuth authorization.
Open your Runzumi dashboard- 01
Check your Runzumi access
Sign in to the Runzumi dashboard and check that your workspace and repository are visible. Account setup, GitHub installation and repository configuration happen there. Ask your workspace owner if access is missing.
- 02
Connect via remote MCP
Any Runzumi customer can connect through a compatible client. No special invitation is required. To add Runzumi as a custom connector in Claude, open Customize > Connectors, click “+ Add”, then “Add custom connector”. On Team and Enterprise plans, an Owner or Primary Owner adds it in Organization settings > Connectors, then members click “Connect”. Use this remote MCP server URL:
https://mcp.runzumi.com/mcpIn Claude Code, run this command, then type /mcp and follow the sign-in steps in your browser:claude mcp add --transport http runzumi https://mcp.runzumi.com/mcpThe Claude directory listing is still pending. Remote MCP access is available separately. - 03
Authorize the intended account
When your client prompts you to authorize, sign in to the Runzumi account with the access you need and review the permissions. Your assistant plan, region and workspace administrator’s settings may affect availability. Never paste passwords or access tokens into a chat.
- 04
Choose a workspace, then ask
Start a new chat and check that Runzumi is on under “+” > Connectors, ask “Open my Runzumi analytics” and select an authorized workspace and repository. Then try a prompt above. A compact panel is available in supported hosts; other hosts can return the same insights and a Runzumi link.
Interface labels and available features vary by host. Read Claude’s custom connector guide for current installation and workspace guidance.
Built for investigation.
The connection reads authorized Runzumi data. It saves only your display preferences, such as a default workspace and repository. It does not run, cancel or rerun jobs, edit workflows, install GitHub apps, change repository settings or manage billing. Manage those actions in your Runzumi dashboard.
Know what enters the conversation.
Analytics and run details can be returned to your assistant. Log excerpts enter the conversation only when explicitly requested, and reads are bounded. A partial result is not a complete audit of your logs.
Disconnect through your assistant’s connection settings to revoke the connection. This does not delete your Runzumi account or past conversations.
Read the connected assistant privacy disclosureKeep moving
Need help connecting?
Tell us which assistant you use, what you were trying to do and the safe error message. Please leave out credentials and full job logs.