Agent Disco

runners.io

Let Claude read your runners.io CI jobs, logs, test results, cache and spend, and diagnose failed GitHub Actions builds without pasting a log.

View in the Claude registry
Integration details

Description

runners.io runs GitHub Actions jobs on managed runners. This connector lets Claude read your organisation's CI data as you, so you can ask why a build failed without pasting a log into the chat. What Claude can do: - Diagnose a failed job in one call: the verdict, the failing steps and tests, memory use, and the log around the last errors. - List recent jobs, filtered by repository, branch, runner label or status. - Read part of a job's log (the tail, a line range, or the lines around a phrase) and the failing tests from its test reports. - Show this month's metered minutes and spend per runner size. - Check Actions cache hit rates and entries, per repository. - List your repositories, the runner sizes and their prices, and search the runners.io docs. - Turn your workflow files into a patch that moves their jobs onto runners.io. It changes nothing: you apply the patch yourself. Built to be safe: - Sign-in uses OAuth. Each connection covers one organisation and sees only what your role sees in the dashboard. - 14 of the 16 tools only read. The two that change anything, cancelling a job and deleting a cache entry, are off by default: they need an owner or admin to approve write access, the organisation to switch them on, and a confirmation on every call. - Text that comes from repositories, such as logs, commit messages and branch names, is marked untrusted, so Claude treats it as data and never as instructions. Requires a runners.io account with GitHub connected. Setup guide: https://www.runners.io/docs/observability/mcp-server

Integration type
Connector
Verification status
Community connector
Platform
Claude
Category
Developer Tools

The broad Category that contains the Primary Subcategory.

Primary Subcategory
CI/CD & Internal Developer Platforms

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is listed.

Access
Account required
First tracked
2026-11-16
Tool count
16
Market
US
AgentDiscoClaude Discoverability Score

Claude Connector discovery is coming soon

Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.

No spam. Unsubscribe any time.

What discovery looks like

Claude showing a list of relevant Connectors in a conversation

Claude can surface verified Connectors when they match a user’s Prompt.

Primary Subcategory
18 scoredVerified connectors by score · Community connectors A–Z
Primary Subcategory
1Datadog69/100
2Grafana Cloud44/100
3mcp.betterstack.com41/100
4incident.io32/100
5CircleCI30/100
—BranchDeployPending VerificationGet notified
—ComponecatPending VerificationGet notified
—HotCodePushPending VerificationGet notified
—Push200Pending VerificationGet notified
—runners.ioPending VerificationGet notified
—Since.devPending VerificationGet notified
Tools

16 tools agents can invoke

Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.Read guide
FAQs

runners.io Claude Connector FAQ

How the directory, categories and Discoverability Score work.

Read the methodology
How do I improve runners.io's Claude Connector discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are runners.io alternatives on Claude?

As of 2026-11-17, runners.io competes with Datadog, Grafana Cloud, mcp.betterstack.com, incident.io, CircleCI, PagerDuty, Coralogix, Vercel and 15 more in Claude CI/CD & Internal Developer Platforms, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.