Jenkins to GitHub Actions MCP Server
Generates GitHub Actions workflow YAML files from Jenkinsfiles, enabling automated pipeline conversion for GitHub Actions.
Converts Jenkins declarative pipelines to GitHub Actions workflows, analyzing Jenkinsfile structure to migrate CI/CD pipelines.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Jenkins to GitHub Actions MCP Server Convert this Jenkinsfile to GitHub Actions workflow YAML file"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.jsRelated 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 buildUsage
As an MCP Server
The server can be integrated with MCP-compatible clients (like Claude Desktop):
npm startConfiguration 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 convertformat(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 deployDevelopment
Build
npm run buildWatch Mode
npm run watchRun Tests
npm testTest 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.jsLint
npm run lintSupported 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 toolsanalyze_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
Scored across 2 tools
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.
Both tools follow the same verb_noun pattern (convert_jenkinsfile, analyze_jenkinsfile), making the naming predictable and consistent.
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.
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
Audit GitHub Actions workflows for script injection, unpinned actions and missing permissions.
Check GitHub Actions workflows live: retired actions, bad inputs, injection. Pin actions to SHAs.
Finds the GitHub Actions workflow eating your CI bill and suggests fix diffs, verified against runs.
GitHub Actions workflow security audit - 21 checks: pinning, permissions, secrets, injection.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jenkins CI/CD systems through natural language, providing build management, job monitoring, log analysis, and debugging capabilities.MIT
- AlicenseAqualityNot gradedmaintenanceConnects 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.101-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jenkins CI/CD systems for build management, job monitoring, console log analysis, and debugging through natural language commands.2MIT
- FlicenseNot gradedqualityDmaintenanceAnalyzes GitHub Actions workflows and performance, helping identify bottlenecks, failures, and optimization opportunities in CI/CD pipelines.-