GitHub Actions Optimization with Pipetrics MCP

Overview

Pipetrics MCP makes measured GitHub Actions data available to Codex, Claude Code, OpenCode, or any other compatible MCP client. Use it for GitHub Actions optimization: find slow workflows, queue delays, failed spend, job bottlenecks, and regressions.

Pipetrics analyzes workflow telemetry without receiving your source code. Your coding agent can inspect workflow files in your local workspace, subject to its own permissions.

MCP endpoint: https://mcp.pipetrics.com/mcp

Prerequisites

Before connecting:

1. Install the Pipetrics GitHub App.
2. Grant the required read-only permissions.
3. Activate at least one repository in Pipetrics.
4. Wait for its first workflow data to be collected.

Authentication uses browser-based OAuth. No Pipetrics API key is required in client configuration.

Connect Codex

Add the remote MCP server, authenticate, and verify it:

codex mcp add pipetrics --url https://mcp.pipetrics.com/mcp
codex mcp login pipetrics
codex mcp list

You can also add it to ~/.codex/config.toml:

[mcp_servers.pipetrics]
url = "https://mcp.pipetrics.com/mcp"

Use /mcp inside Codex to check the connection. See the official Codex MCP documentation for client-specific options.

Connect Claude Code

Add Pipetrics at user scope so it is available across projects:

claude mcp add --transport http pipetrics \
  --scope user https://mcp.pipetrics.com/mcp
claude mcp login pipetrics
claude mcp list

For a project-scoped configuration, create .mcp.json:

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

Project-scoped servers require approval when Claude Code first loads them. If claude mcp login is unavailable in your installed version, run /mcp in an interactive session and authenticate there.

See the official Claude Code MCP documentation for scopes and server management.

Connect OpenCode

OpenCode provides an interactive setup command:

opencode mcp add

Select Remote, enter pipetrics as the name, and use https://mcp.pipetrics.com/mcp as the URL. Then authenticate and verify the server:

opencode mcp auth pipetrics
opencode mcp list

Alternatively, add the server to opencode.json or opencode.jsonc:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipetrics": {
      "type": "remote",
      "url": "https://mcp.pipetrics.com/mcp",
      "enabled": true
    }
  }
}

OpenCode detects OAuth automatically for remote MCP servers. See the official OpenCode MCP documentation for authentication and debugging commands.

GitHub Actions optimization prompts

Analyze where GitHub Actions time is spent in the current repository over the last 14 days. Separate queue delay from runtime, rank the slowest workflows, and explain the evidence before recommending changes.

Analyze .github/workflows/ci.yml at job and step level. Show duration, failure, retry, and outcome trends. Inspect the local workflow file before proposing the three highest-confidence optimizations.

Show which workflows and jobs account for the most measured GitHub Actions cost. Separate failed spend from successful pipeline spend and prioritize changes by estimated savings. Label assumptions and plan limits.

Find commits associated with the largest increases in workflow runtime. Show the before and after SHAs, workflow path, sample coverage, and modeled cost change. Inspect the local diff before suggesting a cause.

Give me the three most important current GitHub Actions findings for this repository. Rank them by runtime, failed spend, queue delay, or repeated regression. Include evidence and the next investigation step.

GitHub Actions optimization flow

Use this sequence for GitHub Actions optimization:

1. Request the top repository findings.
2. Select the workflow with the largest measured impact.
3. Drill into its jobs and steps.
4. Inspect the local workflow YAML.
5. Check commit evidence for recent regressions.
6. Make one focused change and compare later runs with the baseline.

This keeps recommendations tied to measured pipeline behavior instead of generic CI/CD advice.

Data access and plans

Pipetrics uses read-only GitHub permissions for Actions and repository metadata. MCP analysis returns telemetry such as durations, queue delays, failures, retries, workflow paths, commit SHAs, and cost estimates.

For GitHub Actions optimization, start with runtime and failure evidence. Add detailed cost analysis when the repository uses the Pro plan.

See Cost Profiler for visual GitHub Actions cost analysis.

Troubleshooting

Authentication is required

Run the login command for your client and complete OAuth in the browser:

codex mcp login pipetrics
claude mcp login pipetrics
opencode mcp auth pipetrics

The server does not connect

1. Confirm the URL is exactly https://mcp.pipetrics.com/mcp.
2. List configured MCP servers in the client.
3. Repeat browser authentication.

No repository data appears

Confirm that the GitHub App is installed, the repository is activated, and at least one workflow run has been collected. Review the integration guide for required permissions.

Security boundary

Pipetrics MCP does not need source-code access. It supplies measured CI/CD telemetry to the agent. Local file reads and edits are controlled separately by Codex, Claude Code, or OpenCode and remain subject to your approval settings.