Skip to main content
Glama
Jenkins to GitHub Actions MCP Server

Jenkins to GitHub Actions MCP Server

Jenkins to GitHub Actions MCP Server

An MCP (Model Context Protocol) Server that converts Jenkinsfiles to GitHub Actions workflows. This tool helps you migrate your CI/CD pipelines from Jenkins to GitHub Actions by automatically converting declarative Jenkins pipelines into equivalent GitHub Actions workflow YAML files.

Quick Start

# Install dependencies
npm install

# Build the project
npm run build

# Run tests
npm test

# Start the MCP server
npm start

# Try the examples
node examples/test-converter.js
node examples/test-mcp-tools.js

Related MCP server: GitHub Actions MCP

Features

  • 🔄 Convert Jenkins declarative pipelines to GitHub Actions workflows

  • 📊 Analyze Jenkinsfile structure and extract pipeline information

  • 🔍 Support for common Jenkins pipeline constructs:

    • Stages and steps

    • Environment variables

    • Shell commands (sh)

    • Echo commands

    • SCM checkout

  • ⚡ MCP protocol integration for seamless AI assistant interaction

  • 🛠️ Both JSON and YAML output formats

Installation

npm install
npm run build

Usage

As an MCP Server

The server can be integrated with MCP-compatible clients (like Claude Desktop):

npm start

Configuration for Claude Desktop

Add to your Claude Desktop configuration:

{
  "mcpServers": {
    "jenkins-to-github-actions": {
      "command": "node",
      "args": ["/path/to/jenkins-to-github-actions-mcp-server/dist/index.js"]
    }
  }
}

Available Tools

1. convert_jenkinsfile

Convert a Jenkinsfile to GitHub Actions workflow.

Parameters:

  • jenkinsfile (string, required): The content of the Jenkinsfile to convert

  • format (string, optional): Output format - "yaml" or "json" (default: "yaml")

Example:

{
  "jenkinsfile": "pipeline { agent any stages { stage('Build') { steps { sh 'npm install' } } } }",
  "format": "yaml"
}

2. analyze_jenkinsfile

Analyze a Jenkinsfile and provide information about its structure.

Parameters:

  • jenkinsfile (string, required): The content of the Jenkinsfile to analyze

Example:

{
  "jenkinsfile": "pipeline { agent any stages { stage('Build') { steps { sh 'npm install' } } } }"
}

Example Conversion

Input (Jenkinsfile):

pipeline {
  agent any
  
  environment {
    NODE_ENV = 'production'
    VERSION = '1.0.0'
  }
  
  stages {
    stage('Build') {
      steps {
        sh 'npm install'
        sh 'npm run build'
      }
    }
    
    stage('Test') {
      steps {
        sh 'npm test'
      }
    }
    
    stage('Deploy') {
      steps {
        echo 'Deploying application'
        sh 'npm run deploy'
      }
    }
  }
}

Output (GitHub Actions):

name: CI
on:
  push:
    branches:
      - main
      - master
  pull_request:
    branches:
      - main
      - master
jobs:
  build:
    runs-on: ubuntu-latest
    env:
      NODE_ENV: production
      VERSION: 1.0.0
    steps:
      - name: Checkout code
        uses: actions/checkout@v4
      - name: Build
        run: npm install
      - name: Build
        run: npm run build
      - name: Test
        run: npm test
      - name: Deploy
        run: echo "Deploying application"
      - name: Deploy
        run: npm run deploy

Development

Build

npm run build

Watch Mode

npm run watch

Run Tests

npm test

Test Examples

Try the interactive examples to see the converter in action:

# Test the converter with the sample Jenkinsfile
node examples/test-converter.js

# Run the interactive MCP tools test suite
node examples/test-mcp-tools.js

Lint

npm run lint

Supported Jenkins Pipeline Features

  • ✅ Declarative pipeline syntax

  • ✅ Agent configuration

  • ✅ Environment variables

  • ✅ Multiple stages

  • ✅ Shell commands (sh)

  • ✅ Echo commands

  • ✅ SCM checkout

  • ⚠️ Scripted pipelines (limited support)

  • ❌ Complex Groovy scripting

  • ❌ Jenkins-specific plugins

Limitations

  • This tool focuses on declarative Jenkins pipelines

  • Complex Groovy scripting and Jenkins-specific plugins may not be fully supported

  • Some Jenkins-specific features may require manual adjustment in the output

  • The converter makes best-effort conversions and may include warnings for constructs that don't have direct GitHub Actions equivalents

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT

Available Tools

2 tools
analyze_jenkinsfileA

Analyze a Jenkinsfile and provide information about its structure, including stages, steps, environment variables, and agent configuration.

Inputs: jenkinsfile (required).

convert_jenkinsfileA

Convert a Jenkinsfile (declarative pipeline syntax) to a GitHub Actions workflow YAML. Takes a Jenkinsfile content as input and returns the equivalent GitHub Actions workflow.

Inputs: jenkinsfile (required), format.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers

    • 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
    • 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
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Analyzes GitHub Actions workflows and performance, helping identify bottlenecks, failures, and optimization opportunities in CI/CD pipelines.
      -