Jenkins to GitHub Actions MCP Server
Converts Jenkins declarative pipelines into GitHub Actions workflow YAML files, facilitating migration from Jenkins to GitHub Actions CI/CD.
README
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
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 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 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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。