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 "Install 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 ServerConvert 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
This server cannot be installed
Maintenance
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ajaychinthapalli/jenkins-to-github-actions-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server