概要
What is Jenkins Mcp?
Jenkins Mcp is a Model Context Protocol (MCP) server that provides Jenkins integration tools. It allows AI assistants to interact with a Jenkins server – retrieving job information, build details, console output, views, and triggering builds – using Jenkins API authentication.
How to use Jenkins Mcp?
Install dependencies with pip install -r requirements.txt, then configure credentials in a .env file (JENKINS_URL, JENKINS_USER, JENKINS_TOKEN) or via environment variables in the MCP client configuration. Add the server to your MCP client (e.g., Claude Desktop) by editing claude_desktop_config.json with the command and environment variables. Once connected, any MCP‑compatible assistant can call the exposed tools by name.
Key features of Jenkins Mcp
- Retrieve Jenkins server information
- List and inspect Jenkins jobs
- Get recent builds and build summaries
- View build details and console output
- List and manage Jenkins views
- Trigger job builds with optional parameters
Use cases of Jenkins Mcp
- An AI assistant queries the status of recent builds for a CI/CD pipeline.
- A developer triggers a parameterized Jenkins job directly from a chat interface.
- Automating inspection of Jenkins server configuration and job health.
- Debugging failed builds by fetching console output without opening the Jenkins UI.
- Managing Jenkins views and jobs through natural language commands.
FAQ from Jenkins Mcp
What are the runtime requirements?
Python 3.10 or higher and access to a Jenkins server with API access enabled.
How does authentication work?
The server uses a Jenkins API token for authentication. Credentials are set via a .env file (JENKINS_USER, JENKINS_TOKEN) or environment variables in the MCP client configuration.
How do I install and add the server?
Clone the repository, run pip install -r requirements.txt, then add the server to your MCP client by providing the uv command, project directory, and environment variables in the client’s config JSON.
Does it support triggering builds with parameters?
Yes. The trigger_job_build tool accepts an optional parameters dictionary to pass to the Jenkins job.
Where is the server’s data stored?
No data is stored locally beyond the configuration files (.env). All operations are performed live against the configured Jenkins server.
