Skip to main content
Glama
522,293 tools. Updated 2026-09-06 12:44

"Alby" matching MCP tools:

  • Read the tail of a build log to identify termination errors, then page upward using the before_line parameter for context. Diagnose build failures by inspecting the end of the log.
    GPL 3.0
  • Find the root cause of a build failure by searching the log for error signatures or a regex, returning matches with context. Use when tail only shows the symptom.
    GPL 3.0
  • Extract a targeted line range from a build log to investigate failures, expand search results, or review earlier output; logs are auto-downloaded.
    GPL 3.0
  • Generate a release plan for ALBS builds by specifying build ID, platform, and product, computing package-to-repository assignments without releasing.
    GPL 3.0
  • Retrieve available sign keys from ALBS to obtain key ID, name, GPG fingerprint, and platform IDs needed for signing builds.
    GPL 3.0

Matching MCP Servers

Matching MCP Connectors

  • MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.

  • AI listing workflow for Etsy sellers: listings, images, mockups, KDP copy & ad copy. 14 tools.

  • Create a build on AlmaLinux Build System for selected platforms and packages, with options for branches, tags, or SRPM URLs.
    GPL 3.0
  • Search and filter ALBS builds by project or running status, returning page details with task counts, failures, release state, and package NVRs.
    GPL 3.0
  • Retrieve all ALBS products with IDs, names, flags, and platforms to select a target for release plan creation.
    GPL 3.0
  • View a release plan by ID to get its status, product, platform, source packages, and target repositories.
    GPL 3.0
  • List available platform flavors with names and IDs to verify correct flavor names before creating builds.
    GPL 3.0
  • Publish a release using its ID. Currently blocked; server only creates release plans.
    GPL 3.0
  • Delete a build from the AlmaLinux Build System. This operation is currently disabled as a safety measure to prevent accidental removal.
    GPL 3.0
  • Save a build log file to your local filesystem by specifying the build ID and filename. After downloading, tail it to inspect the contents.
    GPL 3.0
  • Retrieve comprehensive build details including task statuses, architectures, package names, sign tasks, and linked builds to reproduce builds accurately.
    GPL 3.0
  • Check sign task status for a build to determine if signing completed or failed, returning each task's ID, status, and key ID.
    GPL 3.0
  • Sign a build on ALBS using a specified sign key ID. Requires JWT token for authentication.
    GPL 3.0
  • Retrieve failed tasks for a build ID, including available log file names like mock_build and mock_stderr to diagnose build issues.
    GPL 3.0
  • Retrieve all available platforms and their supported architectures from ALBS to determine build targets for package compilation.
    GPL 3.0