Skip to main content
Glama
lockround

GitHub Actions MCP Server

by lockround

Related Servers

Alternatives to GitHub Actions MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables auditing GitHub Actions workflows for security problems directly from an MCP client, returning a risk score and findings with file:line evidence, attack narratives, and fixes. Also exposes the full rule catalog and a one-call demo that writes and scans a deliberately broken workflow.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables any MCP client to read GitHub repositories, branches, tags, pull requests, files and Actions workflow runs, and optionally create branches and pull requests, comment, assign, approve, trigger workflows, merge and delete. Read-only by default, with separate opt-in switches for write and destructive operations, working against github.com or GitHub Enterprise Server.
      11
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables managing GitHub repositories, files, and user information through MCP, with support for creating, updating, and deleting repository contents, as well as fetching user profiles.
      1
      -

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target clearly distinct resources (workflow definitions, workflow runs, repo parsing). However, trigger-workflow and trigger-repository-dispatch can both start workflows, and get-workflow vs get-workflow-run could be confused without reading descriptions carefully.

    Naming Consistency5/5

    All tool names follow a consistent lower-case hyphenated verb-object pattern, such as list-workflows, trigger-workflow, and cancel-workflow-run. There is no mixing of naming conventions or vague verbs.

    Tool Count5/5

    Seven tools is a well-scoped size for a GitHub Actions-focused server. Each tool serves a distinct operational purpose without unnecessary bloat or redundancy.

    Completeness4/5

    The server covers core workflow discovery, triggering, run status, and cancellation. Missing operations like listing all workflow runs, re-running workflows, or fetching logs create minor gaps, but the main lifecycle is reasonably represented.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues