Skip to main content
Glama
maxim-at-reveliolabs

pipelines-mcp

by maxim-at-reveliolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to pipelines-mcp

No user-submitted related servers found.

    Related Servers

    • runner-fleet-mcp

      jjoseph456
      A
      license
      B
      quality
      C
      maintenance
      Enables users to inspect ephemeral GitHub Actions runner fleet status, SLOs, incidents, capacity recommendations, and cost evidence through read-only MCP tools, without allowing infrastructure or cluster mutations.
      5
      MIT

    • Claude Ops Investigator

      Randhir123
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only Kubernetes incident investigation through MCP tools for listing pods, describing resources, fetching logs, and searching runbooks.
      1
      -

    • depot-mcp

      PostHog
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only inspection of Depot CI failures, job logs, GitHub Actions jobs on Depot runners, and container builds through the Depot API, so agents can diagnose issues without installing the Depot CLI.
      53 npm
      MIT

    • Autobase MCP

      PokeThePixel
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Autobase Console projects, clusters, environments, operations, PostgreSQL versions, and extensions through configurable MCP tools. Supports paginated listing and filtering, with limited redacted operation logs and no write or arbitrary execution tools.
      MIT

    • k8s-mcp-server

      gaelsg
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only interaction with a Kubernetes cluster, allowing listing of nodes, pods, deployments, and services, as well as fetching pod logs.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct resource/action pairing: jobs, pods, job configs, pod configs, and two log types. Pipeline worker logs and service logs are the only overlapping pair, but the names and descriptions cleanly separate them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using get_ or list_ prefixes. The resource nouns are uniform and predictable, with job/config/pod/log/service modifiers making the hierarchy easy to infer.

    Tool Count5/5

    Eight tools is a well-scoped size for a pipeline inspection server. Each tool covers a distinct need without redundancy or surface bloat.

    Completeness4/5

    The set provides solid read-only coverage of jobs, pods, configs, and logs, which matches an observability-focused purose. Minor gaps exist, such as no direct way to list services or aggregate request-level status, but agents can work around these using the existing list and get tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources