Supports Docker integration for building and testing environments, with specific commands for building Docker images and running tests in containerized environments.
Allows interaction with Jenkins CI/CD platform, enabling triggering of jobs, retrieving build statuses, and performing other Jenkins operations through the MCP interface.
A Jenkins MCP server. Model Context Protocol (MCP) lets AI tools (like chatbots) talk to and control your Jenkins setup, i. e. retrieve information and modify settings.
Note: This is a minimal experimental version of the MCP Jenkins server and is currently in early development.
This project provides a Model Context Protocol (MCP) server for interacting with Jenkins. It allows users to trigger Jenkins jobs, get build statuses, and perform other Jenkins-related operations through the MCP interface.
To install the package and make the console scripts available, run:
Once the package is installed using pip install ., the following console scripts become available in your shell environment:
mcp_jenkins_server: Runs the MCP server.mcp_jenkins_client: Runs an example client.mcp_jenkins_run_docker_build: Builds the Docker image for the server. This should be run before executing tests.mcp_jenkins_run_docker_tests: Runs tests using Docker (e.g., server/client/server tests). This script typically requires the Docker image to be built first using mcp_jenkins_run_docker_build.These scripts eliminate the need to manually manage Python paths or install requirements separately if the package has been installed.
To run the MCP server using the installed script:
To run the example client using the installed script:
For example, to list builds for a job named "backups" using a specific model, you can run:
This might produce output similar to:
A common workflow for development and testing is to first build the Docker image and then execute the tests:
This sequence ensures that tests are performed against the latest build in a consistent Dockerized environment.
The file open-webui/open_webui_interface.py provides an example of how to integrate this MCP Jenkins server with an OpenWebUI instance.
To use it:
open-webui/open_webui_interface.py file and paste it into the tool configuration in OpenWebUI.MCP_JENKINS_SERVER_URL: Set this environment variable in your OpenWebUI environment to the URL of your running MCP Jenkins server (e.g., http://localhost:5000). The script defaults to http://localhost:5000 if the variable is not set.MCP_API_KEY: If your MCP Jenkins server is configured to require an API key, ensure this environment variable is set in your OpenWebUI environment. The script will print a warning if it's not found but will still attempt to make requests.Once configured, the tools defined in open_webui_interface.py (e.g., list_jobs, trigger_build, get_build_status) should become available for use within your OpenWebUI chat interface.
This project is licensed under the MIT License.
This server cannot be installed
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
A Model Context Protocol (MCP) server that enables AI tools like chatbots to interact with and control Jenkins, allowing users to trigger jobs, check build statuses, and perform other Jenkins operations through natural language.