Skip to main content
Glama
ajaychinthapalli

Jenkins to GitHub Actions MCP Server

by ajaychinthapalli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Jenkins to GitHub Actions MCP Server

No user-submitted related servers found.

    Related Servers

    • GitHub Actions MCP

      ArkTechNWA
      A
      license
      A
      quality
      Not graded
      maintenance
      Connects AI assistants to GitHub Actions workflows to monitor CI/CD pipelines, view run logs, diagnose failures, and optionally trigger or manage workflows with granular permission controls.
      10
      1
      -

    • github-actions-audit

      UnbearableDev
      F
      license
      Not graded
      quality
      D
      maintenance
      Audits GitHub Actions workflow files for supply-chain risks like script injection, leaked tokens, unpinned actions, and broad permissions.
      -

    • Jenkins MCP Server

      Anil-appari007
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Jenkins CI/CD systems through natural language, providing build management, job monitoring, log analysis, and debugging capabilities.
      MIT

    • github-actions-mcp

      lailo
      A
      license
      Not graded
      quality
      D
      maintenance
      Analyzes GitHub Actions workflows and performance, helping identify bottlenecks, failures, and optimization opportunities in CI/CD pipelines.
      18 npm
      MIT

    • actions-guard-mcp

      BerkantACUN
      A
      license
      A
      quality
      C
      maintenance
      Scans GitHub Actions workflow files for dangerous triggers, template injection, unpinned actions, excessive permissions, and secrets in shell commands before they are committed, exposing the checks as MCP tools for agents.
      2
      MIT
    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

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one converts Jenkinsfiles to GitHub Actions workflows, the other analyzes their structure. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow the same verb_noun pattern (convert_jenkinsfile, analyze_jenkinsfile), making the naming predictable and consistent.

    Tool Count3/5

    With only 2 tools, the server feels thin, but the narrow scope of Jenkins-to-GitHub-Actions conversion justifies a small toolset. It is borderline acceptable but not robust.

    Completeness4/5

    The core operations of analyzing and converting are covered, which addresses the server's primary purpose. Minor gaps exist, such as lack of validation or batch processing, but these are not critical.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources